| | [ Return to Bugs & Features | Roadmap 2.0 | SVN ⇄ GIT ]
STR #868
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Config Files |
|---|
| Summary: | enhance fltk-config to report on compiler chosen and install path |
|---|
| Version: | 2.0-feature |
|---|
| Created By: | ianmacarthur |
|---|
| Assigned To: | dejan |
|---|
| Fix Version: | 2.0-current (SVN: v4521) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | ianmacarthur
10:58 May 17, 2005 |
| It would be handy if fltk-config could have a few extra options added, to help with cross platform makefiles.
fltk-config --cxx-name # reports the c++ compiler used to build the lib, e.g. g++, bcc, cc, etc. depending on platform
fltk-config --cc-name # as above for c compiler
fltk-config --fltk-root # reports the install path of the fltk files, if multiple versions of the lib are installed in non-standard places for dev or testing. | |
| |
| #2 | ianmacarthur
13:34 May 17, 2005 |
| I've cobbled together a patch to do this (against a working fltk-config, not against fltk-config.in, sorry..)
Works as described above, but I decided at the last minute to make --fltk-root be --fltk-path instead.
Note that I have also included my patch for STR #869 in this code.
--
Ian | |
| |
| #3 | ianmacarthur
03:54 May 18, 2005 |
| Actually, now it occurs to me that my patch can return the wrong thing for --fltk-path, if you invoke fltk-config in a "local" directory (rather than an installed directory).
I'll try and post something better later today... | |
| |
| #4 | ianmacarthur
10:58 May 18, 2005 |
| OK, I have posted a patch for fltk-config.in that *should* do the right thing now. I've changed the names as Mike suggested, and added some tests to make sure that --prefix returns the "right thing" if invoked from a non-installed location - even if via a symlink.
There's a slightly untidy looking dance going on with that, to do with resolving symlinks - I had to dodge that a bit for platforms (mingw) where symlinks don't really exist - and neither do "readlink" or "which"... urgh. But I need that so...
Anyway, seems to work for me - others could test?
Also, please ignore the fltk-config.in I posted, that was finger trouble trying to post the patch!
--
Ian | |
| |
| #5 | dejan
06:15 Aug 17, 2005 |
| Fixed in Subversion repository.
This has been fixed long ago. | |
[ Return to Bugs & Features ]
|
| |
