Strange problem with MinGW make command (with muParser)?

Question

I have the strangest problem when trying to create and install muParser on my windows computer. As suggested in the installation guide, I just burn the CD to the build folder and run

make -f makefile.mingw 

This should be a good and correct standard procedure. However, I cannot understand the output from the command:

 if not exist obj\gcc_static_rel mkdir obj\gcc_static_rel Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Chase\Desktop\muparser_v2_0_0\muparser_v2_0_0\build> 

Now ... at this moment I'm really confused. Since according to the name of the command window, I still INSIDE the make command. So, I type "exit" at the "prompt"

 g++ -c -o obj\gcc_static_rel\muParser_lib_muParser.o -DNDEBUG -O2 -D_WIN32 - I..\include -MTobj\gcc_static_rel\muParser_lib_muParser.o - MFobj\gcc_static_rel\muParser_lib_muParser.od -MD -MP ../src/muParser.cpp Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Chase\Desktop\muparser_v2_0_0\muparser_v2_0_0\build> 

The "step" command appears through the following function. I continue to type exit at the "prompt", and the command seems to continue to step until it is executed. However, after full completion, I do not see any results, and it seems that nothing has been done.

In addition, this has nothing to do with the command line. I even wrote a python script in cd to a directory and call make, and the output still displays a window-style command line - complete with Microsoft's copyright line, etc., and was waiting for input. I typed exit the same way until the process returned to python.

Now I can go crazy, but I'm really confused. The request on the forums did not help, the only answer is that "window assembly should work."

Does anyone know what is happening ???

Answer 1

I downloaded the muParser package and tried to create it. I have the same strange behavior as yours. Then I realized that I only installed MSYS-make, not MinGW-make (the first is for use in the MSYS shell, the second is for use in the Windows shell).
Unfortunately, installing and using mingw32-make gave another error, but googling led me to this page , where it was suggested to rename sh.exe in the MSYS directory. After that, run the mingw32-make -f makefile.mingw library that was successfully built (static version).

Another method that you and shellter use to run ./configure; make ./configure; make in the MSYS shell also cannot create an example for me. In this case, it creates the DLL version of the library instead of the static version; perhaps that is why the example cannot be built.

Answer 2

(You might want to add a tag for "make" or "gmake", which should increase the number of eyes looking at your problem).

Looking at makefile.mingw, I am surprised to see statements like "-if not exist ..", that is, the syntax of the .bat syntax.

I ran ./configure ; make ./configure ; make , and he walked past the error messages you mention, but I see a bunch of error messages like undefined reference to mu::ParserError: so I probably don't have enough libraries to make it work completely. I will have to leave it, and hope this helps you. Note that I did not use make -f makefile.mingw . After using configure , make just picked up the newly created Makefile and it worked (except for problems with the library ;-)

(When you talk about forums, did you mean mingw forums? If not, try looking around here . The search functionality is pretty good.)

Hope this helps.