| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #840
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 2 - Low, e.g. a documentation error or undocumented side-effect |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Config Files |
|---|
| Summary: | fltk-config mod to recognize when invoked from a source dir |
|---|
| Version: | 1.1.6 |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1-current (SVN: v4341) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | greg.ercolano
13:02 May 01, 2005 |
| I find myself with many revs of fltk, and install/rebuild
fltk quickly, never doing the 'make install'. Chances are
high I just run 'configure ; make' w/out any flags, creating
an "fltk-config" that doesn't work; by default it looks
in /usr/local/lib and /usr/local/include for FLTK files,
where they were never actually installed.
Would be cool for those of us with multiple versions
if fltk-config could realize it was being run from the
source dir, and if so, looked in the source dir for
include and lib files, instead of configure's defaults.
I think this one line change to fltk-config will do that:
--- fltk-config: snip
[..]
### BEGIN fltk-config
prefix=/usr/local
selfdir=`dirname $0`; if test -e $selfdir/FL/Fl_Window.H; then prefix=$selfdir; fi <-- ADD THIS LINE
exec_prefix=${prefix}
[..]
--- snip
(I hope that doesn't word-wrap)
This way 'fltk-config' can be invoked out of the source dir
so that it builds with /that/ version of FLTK, eg. via a Makefile:
FLTKCONFIG=/usr/local/src/fltk-1.1.6/fltk-config
myprog: myprog.cxx
$(FLTKCONFIG) --compile $< | |
| |
| #2 | mike
10:28 May 12, 2005 |
| Fixed in Subversion repository.
The changes I made were a little more comprehensive; please let me know if you run into any problems... | |
[ Return to Bugs & Features ]
|
| |
