On Fri, Jun 10, 2011 at 11:02 AM, Jason Gochanour jrgoc...@lanl.gov wrote:
I think you may be right. CMAKE_INSTALL_CONFIG_NAME doesn't contain a
value
when I run a fresh build of the PACKAGE project in Visual Studio.
If it isn't possible to tell CPack what build configuration the user
chooses
I think you may be right. CMAKE_INSTALL_CONFIG_NAME doesn't contain a
value when I run a fresh build of the PACKAGE project in Visual Studio.
If it isn't possible to tell CPack what build configuration the user
chooses in the IDE is there any way to have it just package the required
DLLs
Hello,
I've managed to get an NSIS project up and running in VIsual Studio with
CPack, but I can't figure out how to determine which configuration type
is being built. Is it possible to write up a CMakeLists that will run
through different conditionals based off of the Build Configuration
I've managed to get an NSIS project up and running in VIsual Studio with
CPack, but I can't figure out how to determine which configuration type is
being built. Is it possible to write up a CMakeLists that will run through
different conditionals based off of the Build Configuration Type
I've managed to get an NSIS project up and running in VIsual Studio with
CPack, but I can't figure out how to determine which configuration type is
being built. Is it possible to write up a CMakeLists that will run through
different conditionals based off of the Build Configuration Type
if(SUPPORTS_PARALLEL_BUILD_TYPE)
CMAKE_INSTALL_CONFIG_NAME is set to the current configuration name
(DEbug, release, minsizerel) as chosen in the visual studio
environment so to choose which you build - you choose which you
build.
It doesn't package multiple configurations at once into a
