Lpc2000

Jens Hildebrandt wrote:

> Pablo Bleyer Kocik wrote:
>
> > At 22:45 2004-07-20, you wrote:
> >
> >
> >>Thanks for that.
> >>Would the same 'make' be OK with other GNU packages (MSP430 and
> >>Hitachi) ? I always had a problem with a coexistance of GNU tools for
> >>different micros.
> >>Jan
> >
> >
> >   'GNU make' is 'GNU make', if they are the same version they should 
> behave
> > the same. However, if you are using make for a Cygwin environment, you
> > should be aware of the directory path translations Cygwin does with the
> > filesystem (eg /cygdrive/{drive}, /usr/..., mounts, etc.)
> >
> >   Regards.
> >
> >
> > --
> > PabloBleyerKocik /"Why don't we rewrite it all in assembly
> >   pbleyer2004    / language for processor Mega666?"
> >    @... / - The linux-kernel mailing list FAQ
> >
> >
> Also, make sure that there are no other Development tools with an own 
> 'make' in
> the PATH variable before GNU-make. I ran into that problem when 
> Eclipse instead
> of GNU-make found the make utility that came with Borland C++ Builder. 
> That one
> didn't work with my makefile and produced an error. If you can't 
> change the
> order of entries in the PATH variable (e.g. because then the other 
> tools will
> not be able to find their 'make') you could create a symbolic link like
> "gnu-make" and tell Eclipse to use that name to call 'make'.

Could always do the dodgy old trick of putting a make.bat in the project 
directory
pointing to the make and other utils you want to use.

Sometimes its the only way to get around things, especially
if you have a few different versions of gcc and cygwin installed
and multiple make versions.
eg
"normal cygwin"
mingw + msys
gnuarm
winavr
microchip C30 (gcc  based)
Macraigor Cygwin
keil
gcc for blackfin  etc

Alex