On Thursday 29 November 2007 16:51, Tim Stahlhut wrote:
> >>Build command used was
> >>mingw32-make -f windows\makefiles\makefile.gcc USE_GUI=0
> >> BUILD=debug
> > CPPFLAGS="->DDISTRIBUTION_MESSAGE_2=\"TimS\""
> > "bad command or file name"
> > since there is no file "mingw32-make.exe",
> > I am thinking there should be a "make.exe" in
> > f:\msys\mingw\mingw32\bin and path set to same?
If you plan to use MSYS, then no, there should *not* be; it should be
called mingw32-make.exe, if you've installed it according to our
standard, although it is acceptable to shorten it to gmake.exe if you
prefer shorter command names.
When you install MSYS, *it* provides its own make.exe, in its own /bin
directory. MinGW must *not* be installed into the same directory as
MSYS, (unless you are trialling the technology preview of MSYS-1.0.11);
however, it is acceptable to install MinGW into a /mingw subdirectory of
the MSYS tree, which is what the OP appeared to have, so that would not
have been his problem.
> > (there is no make.exe" in that dir)
Nor should there be; MinGW's bin directory should come *before* the
MSYS /bin directory, in the $PATH set for the MSYS shell, but you want
to be able to run the MSYS make.exe in that environment; thus you
*must* use a different name for MinGW's make.
> Yes, mingw32-make.exe is part of MinGW...
but it is packaged separately, and is an optional install; perhaps the
OP neglected to install it.
> and should be in the bin folder.
MinGW's bin directory, yes; *not* in the MSYS /bin directory.
> It is normaly in C:\MinGW\bin folder;
That is certainly the default, and we *strongly* recommend keeping it
that way, unless you *really* know what you are doing; (and those who
think it might be a good idea to tuck it into `Program Files' do *not*
have the necessary expertise).
> I think you need to install MinGW correctly without the MSys
The OP's installation looked fine to me, except that it was missing