MacArthur, Ian (SELEX GALILEO, UK) wrote:
> Still an issue with it not forcing the image libs to "static" if I use
> the system image libs, but that's probably not a show stopper...
> [..]
> if I configure to use the system libs I get:
>
> /d/IanMacarthur/svn/fltk-1.1
> $ ../fltk-1.1/fltk-config --use-images --ldstaticflags
> -mwindows -L/usr/local/lib -mno-cygwin ../fltk-1.1/lib/libfltk_images.a
> -lpng -lz -ljpeg ../fltk-1.1/lib/libfltk.a -lole32 -luuid -lcomctl32
> -lwsock32
>
> Which of course means that the build picks up the shared libs for png, z
> and jpeg.
Whenever I want to link static libs, I specify the absolute
path to the .a files, and stay away from -L/-l flags. ie:
g++ [..] /usr/lib/libpng.a /usr/lib/libz.a [..] -o foo
This always seemed to make it clear to both me and the linker
what the intention is, and so dynamic libs won't "leak" into
the binary by accident.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
