<div dir="ltr">Hello,<div><br></div><div>I am indeed trying to figure out whether I have a case "<span style="font-family:arial,sans-serif;font-size:13px">where a non-default target is</span></div><font face="arial, sans-serif">not being made default despite a dependency on it", but just could not put it that clearly. I attach a zipfile to demonstrate my problem. And, to add to my confusion I succeeded in making the respective target default and have it not added nonetheless...</font><div>
<span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">I used VS2013 and the appropriate generator.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><font face="arial, sans-serif">After generation the example contains three solutions:</font></div><div><font face="arial, sans-serif"> foo\foo.sln</font></div><div><font face="arial, sans-serif"> foo\alib\alib.sln</font></div>
<div><font face="arial, sans-serif"> foo\aapp\aapp.sln</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">The troublemaker is the custom target 'run_agen'.</font></div>
<div><font face="arial, sans-serif">Open all three solutions and check the configuration manager:</font></div><div><font face="arial, sans-serif"> foo.sln : run_agen is marked for building</font></div><div><font face="arial, sans-serif"> alib.sln : run_agen is marked for building</font></div>
<div><font face="arial, sans-serif"> aapp.sln: run_agen is *not* marked for building</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">I feel that run_agen should be marked for building in aapp.sln.</font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Thanks,</font></div><div><font face="arial, sans-serif">Dirk</font></div><div><font face="arial, sans-serif"><br></font></div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 11, 2014 at 8:16 PM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com" target="_blank">brad.king@kitware.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="">On 06/11/2014 11:57 AM, Dirk Steenpass wrote:<br>
> I could not make myself any clearer I re-post a question by<br>
> William Deurwaarder on Apr 11, 2014.<br>
</div>[snip]<br>
<div class="">> root/A -> in this CMakeLists.txt a custom-target is defined<br>
> root/B -> in this CMakeLists.txt a static-library is defined which depends on A<br>
</div><div class="">> root/C -> in this CMakeLists.txt the executable is defined which depends on B<br>
</div><div class="">> root -> in this CMakeLists.txt all three sub-directories are added.<br>
<br>
</div>Please provide a tarball or zipfile with a minimal source tree<br>
demonstrating the problem.<br>
<div class=""><br>
> what is the reason to exclude A from the default-build<br>
<br>
</div>If add_custom_target is called without the ALL option then it<br>
will not normally be part of the default build. It could be<br>
some utility operation that should not normally run but can<br>
be manually triggered. As explained in William's original<br>
message, and here:<br>
<br>
<a href="http://www.cmake.org/Bug/view.php?id=14929#c35918" target="_blank">http://www.cmake.org/Bug/view.php?id=14929#c35918</a><br>
<br>
it is necessary to bring such targets into the default build if<br>
they are depended upon by other targets that are in the<br>
default build. (It would be much simpler if VS were to honor<br>
dependencies as one might expect instead of skipping things.)<br>
<br>
IIUC you are reporting a case where a non-default target is<br>
not being made default despite a dependency on it. A specific<br>
example tarball will help clarify that.<br>
<br>
Thanks,<br>
-Brad<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Dirk Steenpass</div>
</div>