MacArthur, Ian (SELEX GALILEO, UK) wrote: >> Ian, would you please test both fixes in your environment again? I >> checked it with cygwin with and w/o local libs, and it seems to work >> okay. I also got the *PNG_ALPHA_* macro defined correctly, >> but I didn't >> do any runtime checks. > > Looks OK so far. The PNG checks seem to be good, and the ldstatic flags > stuff is better.
Fine. > 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... Yes, I new that before and documented it on the STR page. But this ought to be the same with FLTK 1.3 now. > i.e., if I have configured to use the fltk built-in image libs, I get: > > /d/IanMacarthur/svn/fltk-1.1-local > $ ../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 > > > Whereas 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. Yes, and maybe even if using the built-in libs (?). Shouldn't it use something like -lfltk-png in the first case? > Still, I am happy with what we have for now. Okay, it's an improvement, but I'm curious now, and maybe I'll take another look later today. I think that there are different variables like STATICIMAGES or so, but maybe they are not used when generating the output (fltk-config) file. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
