.cmake file by
install(FILES foo.txt DESTINATION . CONFIGURATIONS Debug )
Do I figured it was the best way to do it
Scott
-Original Message-
From: Scott Aron Bloom
Sent: Saturday, May 14, 2016 10:41 AM
To: 'J Decker'; Roman Wüger
Cc: cmake@cmake.org
Subject: RE: [CMake] Debug vs Release
Subject: Re: [CMake] Debug vs Release "install" area
there is also BUILD_TYPE (not CMAKE_BUILD_TYPE, which is the initial
condition) that often gets translated into. BUILD_TYPE seems to get set to the
current building configuration.
http://cmake.limitpoint.com/installing-multiple-build-type
I meant to also add; when I first was porting my projects to cmake, I
thought this was a thing I wanted to do also... turns out, it's just a
lot easier to make 2 build trees and build one release and one debug
and have the same output image exactly for both... then install one or
the other for use
On 2016-05-12 20:07- Scott Aron Bloom wrote:
Looking for some advice.
In order to make our Visual Studio debugging environment, as self-contained
(and easy to use for the developers) as possible, we use developers must run an
install. We also use the resulting release based Install for
there is also BUILD_TYPE (not CMAKE_BUILD_TYPE, which is the initial
condition) that often gets translated into. BUILD_TYPE seems to get
set to the current building configuration.
http://cmake.limitpoint.com/installing-multiple-build-types-in-cmake-generated-visual-studio-projects-2/
You could use conditional generator expressions e.g $ with a
combination of add_custom_command stuff like "${CMAKE_COMMAND} -P
yourscript.cmake " to handle the rest.
Best Regards
Roman
> Am 12.05.2016 um 22:07 schrieb Scott Aron Bloom :
>
> Looking for some advice.
>
> In
Looking for some advice.
In order to make our Visual Studio debugging environment, as self-contained
(and easy to use for the developers) as possible, we use developers must run an
install. We also use the resulting release based Install for our packaging
into our installer.
We change the