On Mon, Dec 22, 2008 at 11:27 PM, Robert Dailey <span dir="ltr"><<a href="mailto:rcdailey@gmail.com">rcdailey@gmail.com</a>></span> 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;">
<div class="Ih2E3d">On Mon, Dec 22, 2008 at 9:23 PM, Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a>></span> 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;">
<div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Investigate CMAKE_CFG_INTDIR.<br>
<br>
<br>
I believe for Visual Studio output, this will be $(OutDir), right? If this is the case, this is a visual studio environment variable that will have no meaning when used in CMake scripts.<br>
<br>
</blockquote>
<br></div>
It is . when not in VS, and $(OutDir) when it is. So, you can say /foo/bar/bin/${CMAKE_CFG_INTDIR}/runit.<br>
<br>
It will be /foo/bar/bin/./runit with makefiles.<br>
It will be /foo/bar/bin/$(OutDir)/runit with VS projects.</blockquote></div><br></div>Keep in mind this is for include directories, which will not work with visual studio environment variables. I need to statically tell CMake which include directories go along with what configuration. I don't believe this can be done at the moment, at least with visual studio generation.</blockquote>
<div><br>Just curious, why would you ever want to have two different include directories, one for debug and one for release? It doesn't seem like a very good idea to me, but then again perhaps there is a good use case for this. How many header files are affected? I assume you are aware of and have rejected using the NDEBUG definition for your problem (via a 3rd wrapper file for every affected header file)<br>
</div></div><br>-- <br>Philip Lowman<br>