| | [ Return to Bugs & Features | SVN ⇄ GIT ]
STR #3339
| 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: | fltk-config: would be nice if one could add extra libs to --compile |
|---|
| Version: | 1.4-feature |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | AlbrechtS |
|---|
| Fix Version: | 1.4.0 |
|---|
| Fix Commit: | ee3f9dd06d1325b3f71e655a819b441e1b820468 |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
Trouble Report Comments:
| |
| #1 | greg.ercolano
18:17 Oct 06, 2016 |
| It's nice to compile simple programs with --compile.
But sometimes even simple programs need some extra linker flags,
like -l<somelib>.
Would be good if the user could specify linker flags that --compile
could use:
1) a new fltk-config flag like --add-ldflags, example:
fltk-config --compile foo.cxx --add-ldflags -lsqlite3
2) Let environment variables influence fltk-config the same way
they can influence configure, e.g.
( export LDFLAGS=-lsqlite ; fltk-config --compile foo.cxx ) | |
| |
| #2 | greg.ercolano
18:57 Oct 06, 2016 |
| Attaching a v1 patch that just adds the new flag:
-add-ldflags="-lxxx -lyyy"
Includes online docs mod.
Pretty simple mod.
I decided against letting LDFLAGS influence fltk-config,
as that might create unexpected effects for new users or
build pipelines. | |
| |
| #3 | AlbrechtS
15:21 Nov 25, 2023 |
| Fixed in Git repository.
This has been implemented with even more features.
Closing this STR now. | |
[ Return to Bugs & Features ]
|
| |
