> On 23.09.2009, at 00:48, Greg Ercolano wrote:
>> 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.
Matthias Melcher wrote:
> Hmm. ZVisual C users (about 40% of our user base, IIRC) will not use
> "configure".
Unless I'm missing something, the problem of accidentally
getting stale include files mixed into builds
is only an issue on machines that /are/ case sensitive,
right? (linux, irix..)
On machines that aren't case sensitive (microsoft + osx)
that's not an issue that needs to be detected.
So anyone using Visual Studio wouldn't encounter the problem
of stale include files getting mixed into builds..
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
