On Thursday 23 September 2010, Andrea Galeazzi wrote:
> Hi everybody,
> I've got a project with two configuration (Debug and Release) and two
> target: win32 and ARM.
> In your opinion what's the best way to manage a such kind of project?
> As an example, in my CmakeList I have the following piece
See here for information on build/source directories:
http://www.paraview.org/Wiki/CMake_FAQ#Out-of-source_build_trees
For your example compiler flag (is that gcc only?) and all other info you've
provided so far, you'd probably want to do something like this:
if(CMAKE_CONFIGURATION_TYPES)
se
But where could I put the custom options for the compiler, for example
in arm-debug I'd like to have
CMAKE_CXX_FLAGS -no-rtti
what do you mean with build directory, the source directory?
Citando Ryan Pavlik :
Keep these lines, if they are necessary for your system:
if(CMAKE_CONFIGURATION_TYPE
Keep these lines, if they are necessary for your system:
if(CMAKE_CONFIGURATION_TYPES)
set(CMAKE_CONFIGURATION_TYPES Debug Release)
set(CMAKE_CONFIGURATION_TYPES "${CMAKE_CONFIGURATION_TYPES}" CACHE
STRING "Reset the configurations to what we need" FORCE)
endif()
Remove the other lines
Hi everybody,
I've got a project with two configuration (Debug and Release) and two
target: win32 and ARM.
In your opinion what's the best way to manage a such kind of project?
As an example, in my CmakeList I have the following piece of code that
works fine only for visual studio.
if(CMAKE_
