2009/5/21 Eric Auer <e.a...@jpberlin.de>: > Not really - I think it would be tricky to put the config > variables in something that all used MAKE versions can deal > with directly, as opposed to having both a BAT and a MAK?
There used to be (a long time ago) both a config.bat and a config.mak (for DOS!), where config.bat defined the make to use and config.mak the rest. However it is easier to use just one file. Problems: a) On Linux you can assume that "make" works, on DOS you can't, only batch files are sure to work. b) The logic as done in default.bat and config.bat is impossible to do in "portable make"; esp. Turbo C 2.01 Make is very basic, and can only do !if tests on numbers. c) A recursive "make" or "GNU make" calling "OW wmake" as now done in the cross-build can make DOS run out of memory (depending on compiler/command.com/make). That's why build.bat is used for DOS. > Okay but "echo>> file file1.obj file2.obj" here? that works too. Bart ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
