On 25 Mar 2009, at 21:51, Albrecht Schlosser wrote: > MacArthur, Ian (SELEX GALILEO, UK) wrote: >> All, >> >> A brief investigation suggests that the --compile option is returning >> the wrong options for linking the image libs. I think this is because >> --ldstaticflags is returning the wrong options. >> >> Here's some examples. Firstly, the fltk-1.1 output; >> >> $ fltk-config --use-images --ldflags >> -L/usr/local/lib -mwindows -mno-cygwin -lfltk_images -lpng -lz -ljpeg >> -lfltk -lole32 -luuid -lcomctl32 -lwsock32 >> >> (comment: --ldflags looks good) >> > A quick check here with fltk 1.1 and _cygwin_ looks okay: >
Hmm, I just tried this mac, and got results analogous to what I get under mingw, so I don't think it is mingw specific. immpc4:~ ian$ fltk-config --use-images --ldstaticflags /usr/local/lib/libfltk_images.a -lpng /usr/local/lib/libfltk.a - lpthread -framework Carbon -framework ApplicationServices Note there is no -ljpeg or -lz in there... The differences between your setup and mine would seem to be that (a) I have fltk installed (i.e. with make install) on both test machines, and (b) I am using system versions of the image libs rather than the fltk built-ins. However, on both my test machines, fltk-1.3 seems to work fine, using the system image libs, but I do not have fltk-1.3 installed, so perhaps that is the difference? immpc4:~ ian$ fltk-1.3/fltk-config --use-images --ldstaticflags /Volumes/Disk2/CVS_images/fltk-1.3/lib/libfltk_images.a -lpng -lz - ljpeg /Volumes/Disk2/CVS_images/fltk-1.3/lib/libfltk.a -lpthread - framework Carbon -framework ApplicationServices Anybody else seeing problems with this? I guess it is possible that something in my setup, even over different host OS, is causing this problem, as I do try and make all the differing machines as "similar" as possible... -- Ian _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
