But that pushes the burden of dependency checking onto the developer, which essentially negates most of the value of having a build system. I want to know immediately if I make some change that has ripple effects on other libraries, e.g. I might have updated a header file, so that other libs need to be rebuilt to interface properly. In this case that /fast target would build something that was useless. There is nothing fundamental about the dependency checking that should take so long (I know this because I have an existing build system that does it much faster). It takes so long because cmake does this dependency checking by invoking make many MANY times.<div>
<br></div><div>Kevin<br><br><div class="gmail_quote">2010/7/26 Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">If you want to build just one target, e.g. "foo", there are targets "foo/fast"</div>
which skip the dependency skipping of dependent targets, i.e. it doesn't<br>
check the dependencies of libraries against which foo links.<br>
<br>
So, most of the time is spent in dependency checking.<br>
<br>
Alex<br>
</blockquote></div><br></div>