Newsgroups:	comp.os.msdos.djgpp
From:	gerlach AT netcom DOT com (Matthew H. Gerlach)
Subject:	Re: Using non-GNU compiler with GNU Make
Message-ID:	<gerlachEA88Hp.J3F@netcom.com>
Organization:	Netcom Online Communications Services (408-241-9760 login: guest)
References:	<199705142200 DOT SAA02817 AT delorie DOT com>
Date:	Thu, 15 May 1997 14:34:37 GMT
Lines:	33
Sender:	gerlach AT netcom23 DOT netcom DOT com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <199705142200 DOT SAA02817 AT delorie DOT com> MTEEL DOT DTECHS AT dtechs DOT com (Mark Teel) writes:
>I am porting pSOS to a GEC Butterfly
>micro using the ARM cross development
>tools (armasm, armcc, etc.).  My
>question is: I want to use GNU make as
>we have standardized on it (and it
>rocks the world), but I am having
>trouble invoking the ARM tools from
>Makefiles - it seems that the output
>from the tools to stderr are not
>displayed in my Win95 DOS window.
>This is killing my development
>momentum...
>Any suggestions, thoughts?
>Thanks.
>


Yes GNU make rocks the world, and since I have started using it my
development life has been better.

I use the TI dsp compiler with the djgpp GNU make just fine on my 
win95 machine.  I even run perl scripts from make with no problem.
From my experience STDOUT and STDERR "do the right thing".

One thing you might consider, is make using command.com as the shell
to execute programs?  I found that using bash as the shell promotes
UNIX/win95 portabiltity of makefiles.  This might help STDOUT vs. 
STDERR problems.

Matthew

- Raw text -