DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L1799
Version: 1.1-current


Greg said:


% fltk2-config --ldflags
-L/usr/local/lib -lfltk2 -lX11 -lXi -lXinerama -lXft -lpthread -lm 
-lXext -lsupc++
(..not sure what's wrong with this one.)

I think the problem with this one (and the ldstaticflags option too), at
least in gga's eyes, is that this returns more than just the linker
*flags*, it also returns the linker *libs*, so possibly ought to be called
--ldlibs or etc.

Perhaps ldflags should return just the linker flags and be used in
conjunction with the existing --libs option?

Although - for my money - it is OK as is...

Greg also wrote:

% fltk2-config --ldstaticflags
-L/usr/local/lib /usr/local/lib/libfltk2.a -lX11 -lXi -lXinerama -lXft 
-lpthread -lm -lXext -lsupc++
..should probably be -lfltk2.a instead of /usr/local/lib/libfltk2.a


No - I think maybe you need to give the full path here? There's something
about the way the gcc linker favours dynamic linking over static linking,
and if both libs exist and you *want* to force static linking, you need to
give the full path explicitly. Or something. I used to know this stuff, but
now...

Anyway - if someone knows better, please post!
-- 
Ian


Link: http://www.fltk.org/str.php?L1799
Version: 1.1-current

_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to