> Since doing a ./configure --disable-cygwin DOES build to > completion (with the same configure line) my guess is it's a > check for WIN32 without an offset to see if CYGWIN is defined > or not. Over the last few years that usually seems to be the > culprit. I'll try to suggest a correction during the week if > no one gets to it.
Thanks - I welcome the feedback (and if you come up with a fix, I'd welcome that too...!) All my win32 builds have been with msys/mingw, so it's entirely possible I've missed something on the cygwin front. I don't have that toolchain at all now. Does a "regular" 1.1.8 snapshot build OK for you with cygwin? I thought I had mostly kept my configure script the same but perhaps I messed up. Also, on another front, do you actually need the cygwin support? We used to use cygwin here a lot, even though our win32 targets did not need or use the cygwin layer, until a few years back we had real performance issues on our NT boxes - turned out to be specific to the cygwin build of our code and recompiling with mingw fixed it... That has made we wary of the cygwin stuff ever since, although I dare say they have fixed it in the meantime! Cheers, -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
