: cmake@cmake.org
Subject: Re: [CMake] Copy target from different configurations
alexandre.feb...@thomsonreuters.com wrote:
> Hi,
>
> yes, this is definitely what I would like, there is no other way to
get
> rid of these Debug/Release directories.
>
> I even would like to have
alexandre.feb...@thomsonreuters.com wrote:
Hi,
yes, this is definitely what I would like, there is no other way to get
rid of these Debug/Release directories.
I even would like to have the corresponding variables:
- CMAKE_LIBRARY_OUTPUT_DIRECTORY_
- CMAKE_ARCHIVE_OUTPUT_DIRECTORY_
- CMAKE
target from different configurations
We could create a RUNTIME_OUTPUT_DIRECTORY_ property
to allow per-configuration output directory customizaiton.
Is that what you want?
-Brad
This email was sent to you by Thomson Reuters, the global news and information
company.
Any views expressed in this
Jacob Repp wrote:
I found that the VS7 local generator doesn't honor the
*_OUTPUT_DIRECTORY properties so here's a modification that I added to
our local version:
I think your patch just updates the "intermediate files" output
location, which includes all the object files.
CMake 2.6.4 does hon
est of the team.
Thanks for helping.
Daniel Tavares
Programmer | Slipgate Ironworks
http://www.slipg8.com
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
Of Jacob Repp
Sent: Friday, May 29, 2009 11:24 AM
To: cmake@cmake.org
Subject: Re: [CMa
Unfortunately at least in version 2.6.4 the local visual studio 7
generator doesn't honor the cmake output path settings so some of the
suggestions for that version at least will not work.
If you're using the newer visual studio generator (you don't specify)
you can take advantage of the VS macros
On Thu, May 28, 2009 at 04:02:35PM -0700, Daniel Tavares wrote:
> I'm trying to add a post build event using add_custom_command that will
> copy the target executable to a different directory, but I can't get the
> correct location of the executable created at build time, because it
> changes depen
How can I get the location of the target being built? Granted, this file
name changes depending on the configuration that you're building.
I'm trying to add a post build event using add_custom_command that will
copy the target executable to a different directory, but I can't get the
correct loc
