Sorry I think we are not on the same page.<div><br></div><div>My custom target is: "Foo"</div><div>My C++ executable target is: "Bar"</div><div><br></div><div>I don't want Bar depend on Foo, because I do not want Foo's commands to execute when I build Bar. However, because Bar does not depend on Foo, Foo.vcproj will not be part of Bar.sln. I need a way to make sure that Foo.vcproj opens with Bar.sln without creating that dependency.</div>
<div><br></div><div>I hope this makes a little more sense.<br><br><div class="gmail_quote">On Wed, Apr 4, 2012 at 2:01 PM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Your original message said you didn't want to make it a dependency.<br>
So, why then use "add_dependencies" ...?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On Wed, Apr 4, 2012 at 3:00 PM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
> Well, add_dependencies means that the custom target will be built<br>
> *before* the target that needs it. So it becomes part of "ALL" if the<br>
> other target is part of "ALL".<br>
><br>
> I thought nothing depended on it, that's why I offered the leave out<br>
> "ALL" advice. If something depends on it, then it's going to be<br>
> executed before the thing that depends on it...<br>
><br>
><br>
><br>
> On Wed, Apr 4, 2012 at 2:35 PM, Robert Dailey <<a href="mailto:rcdailey.lists@gmail.com">rcdailey.lists@gmail.com</a>> wrote:<br>
>> I add the custom targets as a dependency with add_dependencies(), and I<br>
>> create the targets with add_custom_target(), I don't specify "ALL".<br>
>><br>
>> In my test with Visual Studio 2008, building the parent project results in<br>
>> these custom targets being built as well. According to your instruction,<br>
>> this should not happen, correct?<br>
>><br>
>> On Wed, Apr 4, 2012 at 12:10 PM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
>>><br>
>>> Sure, just use add_custom_target without the "ALL" argument. If you<br>
>>> don't use "ALL", then the project is completely disconnected from<br>
>>> ALL_BUILD and everything else, and will only be triggered when you<br>
>>> explicitly build that target/project.<br>
>>><br>
>>><br>
>>> HTH,<br>
>>> David<br>
>>><br>
>>><br>
>>> On Wed, Apr 4, 2012 at 12:53 PM, Robert Dailey <<a href="mailto:rcdailey.lists@gmail.com">rcdailey.lists@gmail.com</a>><br>
>>> wrote:<br>
>>> > Hi,<br>
>>> ><br>
>>> > I have a custom target that just runs some commands that have nothing to<br>
>>> > do<br>
>>> > with building source. For convenience, when generating visual studio<br>
>>> > projects, I'd like for that target to be included in the SLN generated<br>
>>> > by<br>
>>> > project() but I don't want to make it a dependency, since that would<br>
>>> > force<br>
>>> > it to build when I build any other project in the solution (I think).<br>
>>> ><br>
>>> > Is there a way to make a vcproj be included in a sln without it building<br>
>>> > as<br>
>>> > part of the dependency chain?<br>
>>> ><br>
>>> > Thanks in advance.<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>