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 inside.<div>
<br></div><div>CMake is generating resource files that must be placed in these directories and are later included in the targets to be compiled, so I need to know this directory so that no matter what generator I'm using, the resource file will always be copied to the proper location.<br>
<br><div class="gmail_quote">On Thu, Jun 21, 2012 at 11:07 AM, J Decker <span dir="ltr"><<a href="mailto:d3ck0r@gmail.com" target="_blank">d3ck0r@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Jun 21, 2012 at 8:58 AM, Robert Dailey <<a href="mailto:rcdailey.lists@gmail.com">rcdailey.lists@gmail.com</a>> wrote:<br>
> So how do I get the absolute path to this directory in a portable (between<br>
> generators) way?<br>
><br>
><br>
<br>
</div>Well, what is it you want from there? I generate INSTALL commands to<br>
put the outputs where I want them and let them worry about where the<br>
files are?<br>
<div class="HOEnZb"><div class="h5"><br>
> On Thu, Jun 21, 2012 at 9:03 AM, J Decker <<a href="mailto:d3ck0r@gmail.com">d3ck0r@gmail.com</a>> wrote:<br>
>><br>
>> On Wed, Jun 20, 2012 at 12:08 PM, Robert Dailey<br>
>> <<a href="mailto:rcdailey.lists@gmail.com">rcdailey.lists@gmail.com</a>> wrote:<br>
>> > ${CMAKE_CURRENT_BINARY_DIR} returns a directory that contains generated<br>
>> > files, such as vcproj files when generating for visual studio. However,<br>
>> > actual compiled binaries are placed:<br>
>> ><br>
>> > ${CMAKE_CURRENT_BINARY_DIR}/${target_name}.dir/Debug (for debug<br>
>> > configuration)<br>
>> ><br>
>> > Is there a variable or target property that will give me the following<br>
>> > path<br>
>> > for any target:<br>
>> ><br>
>> > ${CMAKE_CURRENT_BINARY_DIR}/${target_name}.dir<br>
>> ><br>
>> > (I don't care about debug/release being part of the path, I just want<br>
>> > the<br>
>> > "target.dir" part to be included in the path. Right now I'm hard-coding<br>
>> > the<br>
>> > ".dir" directory and appending it to my path, but I don't know if this<br>
>> > naming scheme is guaranteed by CMake or if it will change in the future.<br>
>> ><br>
>> it differs from generator to generator<br>
>><br>
>> > --<br>
>> ><br>
>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> ><br>
>> > Visit other Kitware open-source projects at<br>
>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> ><br>
>> > Please keep messages on-topic and check the CMake FAQ at:<br>
>> > <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
>> ><br>
>> > Follow this link to subscribe/unsubscribe:<br>
>> > <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
><br>
><br>
</div></div></blockquote></div><br></div>