On 23.09.2009, at 00:48, Greg Ercolano wrote: > Matthias Melcher wrote: >> Actually, for 1.3.0, we could remove the symbolic links and instead >> create files that include a #warning statment, then later an #error >> statement, kind of slowly deprecating the "feature". > > Right.. for the compilers that support this. > > I also thought 'configure' would be a good place to put > warnings (ie. have the 'configure' script sniff around > in /usr/include for links, and if found, warn about them) > > Since everyone has to run configure, whether they do > a 'make install' or not, that might be a good place to > put detection logic, so that during the fltk build process, > one is warned about the old style links.
Hmm. ZVisual C users (about 40% of our user base, IIRC) will not use "configure". I am not sure what to do, because WIN32 is casinsenitive anyways, so they will never see an issue until their source code is compiled on OS X or Unix. I guess that that problem can never be solved anyways... . Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
