Albrecht, Here's what I get (Msys/mingw, but ought to be broadly the same as cygwin...)
For a build set to use the fltk built-in image libs, I get: /d/IanMacarthur/svn/fltk-1.1-local $ fltk-config --use-images --ldstaticflags -mwindows -mno-cygwin ./lib/libfltk_images.a ./lib/libfltk_png.a ./lib/libfltk_z.a ./lib/libfltk_jpeg.a ./lib/libfltk.a -lole32 -luuid -lcomctl32 -lwsock32 Which I think looks correct. However, changing to my build-tree that uses the system image libs I get: /d/IanMacarthur/svn/fltk-1.1-local $ cd ../fltk-1.1 /d/IanMacarthur/svn/fltk-1.1 $ fltk-config --use-images --ldstaticflags -mwindows -L/usr/local/lib -mno-cygwin ./lib/libfltk_images.a -lpng -lz -ljpeg ./lib/libfltk.a -lole32 -luuid -lcomctl32 -lwsock32 Which I think is wrong; I have requested static linking, but the shared png (et al) are selected instead at build time. We either need to give a "full" name for the archive in the /some/path/to/libpng.a (etc.) format, or consider adding the "-static" flag or one of its synonyms (-Bstatic etc.) to the command line to try and force the linker to ignore the shared DLL's. This last idea seems simplest for our needs, but I worry about how portable it might be (although it does seem to work OK for my setup here, FWIW.) However, what I am not clear on is whether, having set "-static" before -lpng etc., we then need to reset to "-shared" before we link the win32 standard libs. It seems that we don not, in my test, but perhaps I was just "lucky"...? -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
