Keep these lines, if they are necessary for your system:<br>if(CMAKE_CONFIGURATION_TYPES)<br> set(CMAKE_CONFIGURATION_TYPES Debug Release)<br>
set(CMAKE_CONFIGURATION_TYPES "${CMAKE_CONFIGURATION_TYPES}"
CACHE STRING "Reset the configurations to what we need" FORCE)<br>endif()<br><br>Remove the other lines. In general, for something like this, you'd have multiple binary/build directories for a single source tree. With a multi-config generator like Visual Studio, you just would need one build directory for each platform (win32 and arm). For a single-config generator like NMake or Unix Makefiles, you'd have one build directory for each platform-mode pair (win32-release, win32-debug, etc).<br>
<br>Hope this helps!<br><br>Ryan<br><br><div class="gmail_quote">On Thu, Sep 23, 2010 at 9:58 AM, Andrea Galeazzi <span dir="ltr"><<a href="mailto:galeazzi@korg.it">galeazzi@korg.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi everybody,<br>
I've got a project with two configuration (Debug and Release) and two target: win32 and ARM.<br>
In your opinion what's the best way to manage a such kind of project?<br>
As an example, in my CmakeList I have the following piece of code that works fine only for visual studio.<br>
if(CMAKE_CONFIGURATION_TYPES)<br>
set(CMAKE_CONFIGURATION_TYPES Debug Release)<br>
set(CMAKE_CONFIGURATION_TYPES "${CMAKE_CONFIGURATION_TYPES}" CACHE STRING "Reset the configurations to what we need" FORCE)<br>
set(CMAKE_CXX_FLAGS_DEBUG "/D _DEBUG")<br>
set(CMAKE_CXX_FLAGS_RELEASE "/D _NDEBUG")<br>
endif()<br>
<br>
What I need is to move this code in another file so I can also specify similar options for gcc etc......<br>
On the other hand in CMakeList.txt should contain just only the sources,include path and the other statements not involving the specific target or configuration.<br>
Cheers<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ryan Pavlik<br>HCI Graduate Student<br>Virtual Reality Applications Center<br>Iowa State University<br><br><a href="mailto:rpavlik@iastate.edu">rpavlik@iastate.edu</a><br>
<a href="http://academic.cleardefinition.com">http://academic.cleardefinition.com</a><br>Internal VRAC/HCI Site: <a href="http://tinyurl.com/rpavlik">http://tinyurl.com/rpavlik</a><br>