widelands-dev team mailing list archive

[Kiscsirke <csirkeee@xxxxxxxxx>]

Okay, now cmake has no problems running, and I can build, but make
doesn't have a "codecheck" target, instead a separate make target for
codechecking each file. I guess that's not the expected behaviour?

-- 
CMake Windows codecheck error
https://bugs.launchpad.net/bugs/535616
You received this bug notification because you are a member of Widelands
Developers, which is subscribed to widelands.

Status in Widelands: Confirmed

Bug description:
This happens for me If I try to run cmake on Windows with codecheck, so for example with the default Debug build (though not with Release build). It is a regression from revision 4968. The error messages are like hundreds of these:

"CMake Error: Cannot open file for write: D:/prog/widelands/bzr/widelands/build_cmake/src/CMakeFiles/D:_prog_widelands_bzr_widelands_src_ai_ai_help_structs_cc_codecheck_stamp_.dir/build.make.tmp
CMake Error: : System Error: Invalid argument
CMake Error: Could not create D:/prog/widelands/bzr/widelands/build_cmake/src/CMakeFiles/D:_prog_widelands_bzr_widelands_src_ai_ai_help_structs_cc_codecheck_stamp_.dir/cmake_clean.cmake"

With some googling and stuff, I found the problem to be with line 37 (currently) in the src/CMakeLists.txt, this one:

"add_custom_target(${stamp} DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/codecheck-stamps/${stamp})"

The same problem and a solution can be found here:
http://www.mail-archive.com/cmake@xxxxxxxxx/msg03178.html , although I don't understand fully, but for someone more into CMake it might make sense.