MacArthur, Ian (SELEX GALILEO, UK) wrote: > >>> 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 > > >> Yes, and maybe even if using the built-in libs (?). Shouldn't it use >> something like -lfltk-png in the first case? > > > Ouch, yes. Good point. > That worked in my test harness, of course, since it picked up the system > libs.
But only because they are there. Otherwise it would have picked the local libs. > I never noticed... It should be picking up the local libs. > > I configured as: > > > $ ./configure --enable-threads --enable-local-jpeg --enable-local-png > --enable-local-zlib > > And it does seem to have built the local libs - just not used them... > Urgh! I guess there are too many options and cases ;-) I remembered after posting that the libs are renamed during the _install_ process, and fltk-config does some magic tricks to detect if it is called from the source tree (test and its own build case) or from the installed dir. Thus it should work in the "installed" case. But there are things to be checked anyway, and probably the best we can do is really to use libxxx.a explicitly in the static linker case. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
