> Fabien Costantini wrote: ou may be right here. I'm using cygwin for (Windows) development for a long time > now, and it works very well, once you know the tricks. Okay, but it should work without (too many) tricks, see below. > If you would configure in automatic mode, ./configure would find > the system (cygwin) dlls, and your build would be broken, because it would > depend > on the cygwin image libraries (dlls) and cygwin1.dll. Here comes > --enable-local* ... Thanks for the details, I know that many people use the enable-localxxx to avoid conflicts. I also always use them local because I like to have the same source code to deal with on any platform. Now, while concentrating only on images libs (have no other pretension right now) and try to make it work better : Even if the libs are found, we should also test if the headers found, then only in that case, in auto mode, we would make the lib mode on, otherwise it should be off and so local lib should be choosen.
Also, I wonder how auto mode would work without the [action-if-not-given] parameter as specified in the autoconf manual ? Any autoconf pro could enlighten us ? _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
