On Thu, Jun 21, 2012 at 11:33 AM, Yuri Timenkov wrote:
> Is it strict requirement? Can't you just add your .rc files as source
> file to your target or just add target name as part of file name? This
> way they can be put everywhere, including current binary dir. I use
> this for adding version in
Is it strict requirement? Can't you just add your .rc files as source
file to your target or just add target name as part of file name? This
way they can be put everywhere, including current binary dir. I use
this for adding version information to binaries.
Otherwise you may try to use post-build
I really want to do that, but unless I can add source files to a target
after its been created, I'm in a catch 22:
I need the location of that directory to place a resource file there, which
will be included in the target. HOWEVER-
I can't get the location without creating the target, and I can't
This is becoming a challenge :-)
I'm generating .RC files using configure_file() in my CMake script. Since I
can have multiple targets defined in the same directory, and the resource
file generated for each target has the same name, I need them to be placed
in the .dir directory inside of CMAKE_CU
Then you should use LOCATION target property
(http://www.cmake.org/cmake/help/v2.8.8/cmake.html#prop_tgt:LOCATION)
or use generator expressions, because exact place where resulting
binary located depends on many things (used generator, other
variables, like CMAKE_RUNTIME_OUTPUT_DIR, etc).
On Thu,
On Thu, Jun 21, 2012 at 9:26 AM, Robert Dailey wrote:
> You're totally confused. I'm not looking to work around a problem, I just
> want information from CMake that I know it has. Somewhere it knows exactly
> where binaries will be placed (those binaries that get compiled) because it
> has to gene
You're totally confused. I'm not looking to work around a problem, I just
want information from CMake that I know it has. Somewhere it knows exactly
where binaries will be placed (those binaries that get compiled) because it
has to generate the scripts and visual studio projects with those paths
in
On Thu, Jun 21, 2012 at 8:58 AM, Robert Dailey wrote:
> So how do I get the absolute path to this directory in a portable (between
> generators) way?
>
>
Well, what is it you want from there? I generate INSTALL commands to
put the outputs where I want them and let them worry about where the
file
So how do I get the absolute path to this directory in a portable (between
generators) way?
On Thu, Jun 21, 2012 at 9:03 AM, J Decker wrote:
> On Wed, Jun 20, 2012 at 12:08 PM, Robert Dailey
> wrote:
> > ${CMAKE_CURRENT_BINARY_DIR} returns a directory that contains generated
> > files, such as
${CMAKE_CURRENT_BINARY_DIR} returns a directory that contains generated
files, such as vcproj files when generating for visual studio. However,
actual compiled binaries are placed:
${CMAKE_CURRENT_BINARY_DIR}/${target_name}.dir/Debug (for debug
configuration)
Is there a variable or target propert
10 matches
Mail list logo
