Debug build error

• Dec 18, 2012 - 01:18

Hi,

I am trying to build a debug version on Windows platform. And I follow the build instructions of http://musescore.org/en/developers-handbook/compile-instructions-window…

1 Release version build is normal.

2 Debug version build has problems. And the build errors are as follows.

Can anyone give me some advice on what to do?

Really thanks a lot in advance!

Victor Wang

/***********************************************************************************************
D:\MuseScore>mingw32-make -f Makefile.mingw debug
if not exist build.debug\nul mkdir build.debug
if not exist win32install\nul mkdir win32install
cd build.debug & cmake -G "MinGW Makefiles" -DCMAKE_TOOLCHAIN_FILE=../build/ming
w32.mingw.cmake -DCMAKE_INSTALL_PREFIX=../win32install -DCMAKE_BUILD_TYPE=DEBUG
-DCMAKE_MAKE_PROGRAM=C:\MinGW\bin\mingw32-make.exe ..
-- The C compiler identification is GNU 4.4.0
-- The CXX compiler identification is GNU 4.4.0
-- Check for working C compiler: C:/MinGW/bin/gcc.exe
-- Check for working C compiler: C:/MinGW/bin/gcc.exe -- broken
CMake Error at C:/Program Files/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCComp
iler.cmake:61 (message):
The C compiler "C:/MinGW/bin/gcc.exe" is not able to compile a simple test
program.

It fails with the following output:

Change Dir: D:/MuseScore/build.debug/CMakeFiles/CMakeTmp

Run Build Command:C:\MinGW\bin\mingw32-make.exe
"cmTryCompileExec2839505294/fast"

mingw32-make[1]: Entering directory
`D:/MuseScore/build.debug/CMakeFiles/CMakeTmp'

C:/MinGW/bin/mingw32-make -f
CMakeFiles\cmTryCompileExec2839505294.dir\build.make
CMakeFiles/cmTryCompileExec2839505294.dir/build

mingw32-make[2]: Entering directory
`D:/MuseScore/build.debug/CMakeFiles/CMakeTmp'

"C:\Program Files\CMake 2.8\bin\cmake.exe" -E cmake_progress_report
D:\MuseScore\build.debug\CMakeFiles\CMakeTmp\CMakeFiles 1

Building C object
CMakeFiles/cmTryCompileExec2839505294.dir/testCCompiler.c.obj

C:\MinGW\bin\gcc.exe -o
CMakeFiles\cmTryCompileExec2839505294.dir\testCCompiler.c.obj -c
D:\MuseScore\build.debug\CMakeFiles\CMakeTmp\testCCompiler.c

Linking C executable cmTryCompileExec2839505294.exe

"C:\Program Files\CMake 2.8\bin\cmake.exe" -E cmake_link_script
CMakeFiles\cmTryCompileExec2839505294.dir\link.txt --verbose=1

"C:\Program Files\CMake 2.8\bin\cmake.exe" -E remove -f
CMakeFiles\cmTryCompileExec2839505294.dir/objects.a

C:\MingGW\bin\ar.exe cr CMakeFiles\cmTryCompileExec2839505294.dir/objects.a
@CMakeFiles\cmTryCompileExec2839505294.dir\objects1.rsp

Error running link command: The system cannot find the path specified

mingw32-make[2]: *** [cmTryCompileExec2839505294.exe] Error 2

mingw32-make[2]: Leaving directory
`D:/MuseScore/build.debug/CMakeFiles/CMakeTmp'

mingw32-make[1]: *** [cmTryCompileExec2839505294/fast] Error 2

mingw32-make[1]: Leaving directory
`D:/MuseScore/build.debug/CMakeFiles/CMakeTmp'

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:21 (project)

-- Configuring incomplete, errors occurred!
mingw32-make: *** [debug] Error 1
/*********************************************************************************************


Comments

The first error is
CMake Error at C:/Program Files/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCComp
iler.cmake:61 (message):
The C compiler "C:/MinGW/bin/gcc.exe" is not able to compile a simple test
program.

It's a problem with your system, or with the CMake installation maybe.

In reply to by [DELETED] 5

Really thanks a lot!

Now I can finish the debug build. I just follow the instruction of "http://musescore.org/en/developers-handbook/compile-instructions-window…".

And now I am doing for the final step, that is:
To compile the debug build and start debugging go to Debug → Start debugging → Start debugging or simply click the debug icon. You have access to Qt help, completion, and debugging features

But when I want to debug the source code, a message of "the gdb process terminated" appears.

Anyone met with the same problem and give me some help?

Really thanks a lot in advance!

Do you still have an unanswered question? Please log in first to post your question.