Spiro Trikaliotis wrote:
Well, it depends upon the tool you're using. We are building drivers,
and they need the build.exe tool, which is part of the DDK. That one can
only compile files in the current directory. As John has pointed out, it
might even be able to compile files in the parent directo
Hello,
* On Mon, Nov 29, 2004 at 07:49:06AM -0500 Todd Denniston wrote:
> I thought it was possible with MS to have them not collocated, but you
> have to spend time figuring out how to convince the MS tool of that as
> it is not the DEFAULT mode of operation.
Well, it depends upon the tool you
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 proje
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.
If you are building drivers, there are two things I can suggest...
(1) Use a different name for the Linux makefile. makefile.linux, fo
At 06:30 AM 11/29/2004, Spiro Trikaliotis wrote:
No. 1 has been rejected, as the Linux guys thing: "GNUMakefile" is a
name which is reserved for makefiles which use GNU-specific extensions.
Choose a different name.
___
Frederic W. Brehm, S
Spiro Trikaliotis <[EMAIL PROTECTED]> writes:
> Hello,
>
> I have a question regarding two projects, which do the same for Windows
> and/or Linux, and share many files of the common code base.
>
> Unfortunately, the build systems or not compatible: GNU Make with gcc on
> the one hand, Microsoft's
Spiro Trikaliotis wrote:
>
> Hello,
>
> I have a question regarding two projects, which do the same for Windows
> and/or Linux, and share many files of the common code base.
>
> Unfortunately, the build systems or not compatible: GNU Make with gcc on
> the one hand, Microsoft's BUILD-Tool on the
