Thanks for the pointers - though I'm not a cygwin fan... Albrecht uses cygwin I think, so he may have more useful comments!
> The cygwin folk have made the rather odd choice to move their Historically, they made a lot of choices I considered odd, really messed me up. I now use mingw/Msys instead and things have been a lot less bumpy... > With these changes, and --enable-cygwin on the command line > for configure I have been able to build and use FLTK 1.1.10 > quite happily on the current cygwin platform. Ah, OK. I *never* use the enable-cygwin option, I always use the native options. We have a mixture of commercial and free tools here, all of which depend on different (and apparently incompatible) versions of the cygwin DLL's, and it is a hideous mess. So I build my own code to *never* depend on the cygwin DLL's and then it Just Works... I concede it does make portability between *nix and win32 a little bit more tricky, I think it is less painful than actually fighting with the cygwin DLL's. *So far* I haven't found any *nix'ism that the cygwin DLL provided that I couldn't do satisfactorily with native win32 calls anyway, so far.... Going OT, and just out of curiosity, is there something that cygwin provides that you really need? Cheers, -- Ian SELEX Galileo Ltd 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
