vcproj2cmake-users Mailing List for vcproj2cmake
Visual Studio .vc[x]proj to CMakeLists.txt (make, Ninja ...) enabler
Status: Alpha
Brought to you by:
andim2
You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|
From: Kurien M. <kur...@gm...> - 2012-03-28 16:32:58
|
Hello, I have a vcproj with 4 configurations - Debug|Win32 - Debug|x64 - Release|Win32 - Release|x64 The CMakeLists.txt generated by vcproj2cmake.rb does not seem to differentiate between the 2 debug configurations Win32 and x64. eg it contains 2 blocks with if(CMAKE_CONFIGURATION_TYPES OR CMAKE_BUILD_TYPE STREQUAL "Debug") > This results in two identical targets and the following error: CMake Error at CMakeLists.txt:233 (add_library): > add_library cannot create target "os" because another target with the > same > name already exists. The existing target is a shared library created in > source directory > "/home/kmathew/svn/os/build/cmake". > See documentation for policy CMP0002 for more details. > How can this be resolved? Thanks Kurien |
From: Kurien M. <kur...@gm...> - 2012-03-28 15:23:02
|
Hello, I have a couple of question on how to use the script: 1) The output of the vcproj2cmake.rb script reads: Wrote CMakeLists.txt Finished. You should make sure to have all important v2c settings includes such as vcproj2cmake_defs.cmake somewhere in your CMAKE_MODULE_PATH and the CMakeLists.txt generated has set(CMAKE_MODULE_PATH "././cmake/Modules" ${CMAKE_MODULE_PATH}) How can one ensure that v2c settings are in the CMAKE_MODULE_PATH? Is there a preferred way to do this? Can the rb script be configured to generate a CMakeLists.txt with a custom value for CMAKE_MODULE_PATH eg "./build/cmake/v2c/cmake/Modules"instead of "././cmake/Modules". 2) The CMakeLists.txt has the comments # TEMPORARY Build file, AUTO-GENERATED by http://vcproj2cmake.sf.net # DO NOT CHECK INTO VERSION CONTROL OR APPLY "PERMANENT" MODIFICATIONS!! Why is it advised not to put the file into version control? Without CMakeLists.txt files in version control wouldn't it be necessary to run the script on each module after checkout of the source? Or would the Live Update Capability simplify this? Thanks Kurien |