Hello John (and the others who answered), * On Mon, Nov 29, 2004 at 09:55:32AM -0600 McNamee, John wrote:
> If you're not building device drivers, consider using a tool other > than build.exe. There are plenty of make utilities for Windows, > including a port of GNU make. Yes, I know. This project contains a driver, as well as user mode programs. Although the drivers differ significantly between Linux and Windows (obviously), I like to have one build environment for both types. Because of this, I find build.exe to be the tool of choice. > (1) Use a different name for the Linux makefile. makefile.linux, for > example. If the Linux developers alias "build" to "make -f > makefile.linux", then both Windows and Linux will use the same command > to build the code. How much more equal can they be? :-) A good point, which was suggested by another one, too. I did not yet think about such a solution. I will suggest that one internally. > (2) The Microsoft build.exe tool can compile code from the parent > directory of the sources file. It can? Ok, I did not yet test for the parent directory, but it cannot compile code from another directory. A solution I used before was to #include the .c file, but IMHO, this is very error-prone. I will test this one, too. Thank you all for your suggestions, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
