Stephen Brandon wrote: > > I think the warnings are good and I would not want to remove > them from Windows compilation, where, to be honest, it's > easier to make the mistakes because it can be harder to > ensure that GNUstep.sh has been run before doing > compilations etc. It's not as standardised as unix. >
I get the bogus warning when compiling on Windows and it really is annoying/confusing. So it would be nice to fix it. I guess at the risk of expanding the code infinitely, we could do: ifeq ($(findstring mingw, $(GNUSTEP_TARGET_OS)), mingw) ...windows specific check else ...unix specific check endif (also including cygwin) -- Adam Fedor, Digital Optics | Fudd's law of opposition: Push [EMAIL PROTECTED] http://www.doc.com | something hard enough, and it [EMAIL PROTECTED] http://www.gnustep.org | will fall over. _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
