On Fri, Feb 29, 2008 at 5:53 AM, Anteru <<a href="mailto:Anteru@shelter13.net">Anteru@shelter13.net</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Problems:<br>
* I want to name my debug libraries with a trailing 'd'. I use<br>
SET_TARGET_PROPERTIES(MyTarget PROPERTIES DEBUG_POSTFIX "d") to do this.<br>
However, MyTarget is a unit-test runner and I want to execute it using<br>
ADD_COMMAND as described here<br>
<a href="http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_then_use_the_executable_to_generate_a_file.3F" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ#How_do_I_generate_an_executable.2C_then_use_the_executable_to_generate_a_file.3F</a><br>
albeit without the output:<br>
<br>
GET_TARGET_PROPERTY(PRJ_UT_TARGET MyTarget OUTPUT_NAME)<br>
ADD_CUSTOM_COMMAND(<br>
TARGET MyTarget<br>
POST_BUILD<br>
COMMAND "${PRJ_UT_TARGET}" VERBATIM<br>
)<br>
<br>
This works fine for release, but not for debug, as it always returns the<br>
name without the prefix. How is this supposed to work?</blockquote><div><br>How about GET_TARGET_PROPERTY(var MyTarget DEBUG_LOCATION) followed by a second ADD_CUSTOM_COMMAND() for the debug binary?<br><br>Not exactly the cleanest solution but I think it should work. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Is it possible to have x86 & x64 configurations inside a single VC<br>
solution? During configure, I have to choose either x64 or x86. This is<br>
nothing serious, I'm just wondering.</blockquote><div><br>Not that I'm aware of.<br> </div></div><br>-- <br>Philip Lowman