Configuring mingw project in v22.0.2.1

[bremenpl]

Same thing:

Code: [Select]

k:\test>make -f test.mak
C:/MinGW/bin/g++.exe -c   -O0 -g3 -ggdb -p -pg -o "Debug/test.o"  test.c
C:/MinGW/bin/g++.exe  -O0 -g3 -ggdb -p -pg -o "Debug/test.exe" Debug/test.o
g++.exe: fatal error: no input files
compilation terminated.
make: *** [Debug/test.exe] Error 1

k:\test>

[Dan]

Is Debug/test.o there?

[bremenpl]

Yes. Running the commands manually works, using the makefile does not.

[Dan]

I misunderstood, I thought the linker command didn't work at all.

[bremenpl]

Yeah, the linker command works, the compile one does not.

[bremenpl]

In general I have noticed that in eclipse I do not need any variables in path at all. Everything is configured as local path (attachment).
For instance in the MINGW_HOME there are all necessary pathes for compiling and MSYS_HOME provides the minimum posix enviroment.
In Slickedit, is there any way to provide make, rm, ls etc. programs path?

[Dan]

No, for make you can adjust it by changing it in the build command.  Running rm or ls from the the editor actually run an internal command.

[bremenpl]

I see.
So, do you have any other ideas what could be wrong in here? I do appreciate your help so far though.

[Dan]

I'm kind of at a loss myself.  I can't reproduce it.

Just for the heck of it, I'm curious what happens if you put MinGW's bin directory in your path.  You'd have to add it, then launch a console, and then launch SlickEdit from there (I guess running SlickEdit from an icon would work too).  You can be sure it worked by running the command "set" on the SlickEdit command line.

I'll ask some colleagues later today.  It's only 645am here on the East coast of the US, so it will be an hour or so before I expect to see anybody else online.

[bremenpl]

I had to add mingw to my path already. Otherwise it did not see all of the *.dll files within mingw directory and crashed. So yes, mingw bin directory is in path already. Thats why I was asking about those pathes. Thanks.

[Dennis]

Just to make sure you are getting the right "make", try:

Code: [Select]

C:/MinGW/bin/make -f test.mak
If you are picking up a Cygwin or other make tool, it may not understand the C:/MingW style path, either because it expects /cygdrive/... or that it doesn't like forward slashes.

[bremenpl]

Its the right make. I have now even entered it manually in the makefile:

Code: [Select]

MAKE=C:/MinGW/bin/mingw32-make.exe
The thing is I can execute it from command line and it works. It just doesnt when run in the slickedit script.

[Dennis]

What's entered in the makefile is only used if the makefile has to call 'make' recursively, for example to compile a dependent project.

You are running just 'make', but what you just sent was mingw32-make.exe, so are you certain that when you run 'make' that it is running C:/mingw/bin/make ?

What happens if you run C:\MingW/bin/mingw32-make.exe -f test.mak ?

On my Windows machine, I had to insure that /c/mingw/msys/1.0.bin/ was in my PATH in order for make to work correctly with the mingw gcc compiler.  The easiest way to do that is to launch the msys shell window rather than the more bare-bones mingw32 terminal.

[bremenpl]

Yes, I have also included the msys path. When I manually run make:

Code: [Select]

k:\test>C:\MingW/bin/mingw32-make.exe -f test.mak
C:/MinGW/bin/gcc.exe -O0 -g3 -ggdb -p -pg -o "Debug/test.exe" Debug/test.o
gcc.exe: fatal error: no input files
compilation terminated.
test.mak:61: recipe for target 'Debug/test.exe' failed
mingw32-make.exe: *** [Debug/test.exe] Error 1

k:\test>

[Dennis]

Really looks like something is amiss about your mingw installation and mingw make.  What do you get if you run C:\mingw32\bin\mingw32-make.exe --version ?

Why don't you go ahead and write your own Makefile for building your program and see if you can get that off the ground.  Then you can return to debugging whatever is going wrong with the makefile that we are generating for you.