On 21.08.2011, at 22:20, Ian MacArthur wrote: > Matt, > > Yes, OK, I know the Xcode project is the preferred build option on OSX, but I > always just use the Makefiles anyway.
Oh no. Makefiles are supposed to work too, but there will be changes... . > Except that now it chokes on OSX... Ooops... > Compiling fl_images_core.cxx... > /usr/bin/ar cr ../lib/libfltk_images.a ... > make[1]: *** No rule to make target `../lib/libfltk_png.a', needed by `all'. > Stop. > make: *** [all] Error 1 > Hmm, that's odd - it ought to be using the system image libs, so it has not > bothered to build the fltk_png at all, hence the choke: OK, I made a design decision here that will haunt me for a while. I figured it would be useful to compile jpeg, png, and zlib from scratch always. This will reduce special cases at compile time and simplify the autoconf/configure process. It will ensure that these libraries exist, even if FLTK was configured on a machine that has built-in jpeg libraries, but a resulting app was distributed to a machine without that library (say you build Fluid on machine a and statically link fltk and fltk_images, but not fltk_jpg etc. . On a machine that has no libjpeg, the app will not launch at all). The overhead is close to zero (jpeg.png/zlib compile in less then ten seconds on my machine), and the developer can of course still decide to dynamically link with libjpeg instead of fltk3jpeg. This is only relevant for the test/example/fluid apps. But obviously my setup is not yet good enough ;-) I will start a quite huge reorganization of the directory structure today. - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
