Hi, > By "Windows compatibility" I meant what I was talking about in my > post, i.e. it working properly when called from cmd.exe "Running the Makefile from cmd.exe" is a way more useful term than "Windows compatibility". My comments regarding GnuWin32 were targeted towards cmd.exe... > (of course > make from MinGW/whatever is required as well). This would mean > replacing mkdir/rmdir/rm/etc with Windows equivalents when Windows is > detected. It's up to you if you want to pursue that or not. I personally don't see any point in doing so. Where ever you get your make from should be a great place to get mkdir/rmdir/rm from. Check out this: http://www.gnu.org/software/make/manual/make.html#Utilities-in-Makefiles To get anywhere near reproducable results with 'make' one needs to envision make and the enumerated utilities as a single entitiy to be provided/installed/used together. Build tools trying to improve/replace 'make' typically have the functionality of those utilities built in. But with 'make' they happen to be separate - neverless they are part of a 'make' environment. Trying to have 'make' work with some other utilities that happen to come with Windows is like trying to have ld65 work with another compiler instead of cc65. >> I haven't however tested the Makefile with GunWin32 so far, maybe >> someone else... > I'll try it out and let you know. That would be great - thanks in advance :-) Regards, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat May 28 22:46:51 2011
This archive was generated by hypermail 2.1.8 : 2011-05-28 22:46:54 CEST