<div dir="ltr">Dan,<div><br></div><div>How did you end up handling the precompiled dependencies? Did you use a dependency management system, such as ivy, or roll your own system?</div></div><div class="gmail_extra"><br clear="all">
<div>Thomas Taranowski | 425-442-9209 | skype: thomas.taranowski | <a href="http://baringforge.com" target="_blank">baringforge.com</a><br><br></div>
<br><br><div class="gmail_quote">On Mon, Aug 26, 2013 at 12:21 PM, Dan Kegel <span dir="ltr"><<a href="mailto:dank@kegel.com" target="_blank">dank@kegel.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="im">On Mon, Aug 26, 2013 at 12:16 PM, Thomas Taranowski <<a href="mailto:tom@baringforge.com">tom@baringforge.com</a>> wrote:<br>
> Now, I'm trying to implement a multi-stage build which does the following:<br>
> 1) builds some external third-party dependencies.<br>
> 2) auto-generate some code<br>
> 3) build the source<br>
> 4) package the result<br>
><br>
> To do this, I'd like to implement some top level build targets in cmake, so<br>
> I can run make auto_generate, make third_party, etc.<br>
><br>
> I can see a couple different potential ways to do this, but I've not been<br>
> able to google up documentation that discusses the best method for<br>
> implementing this. How are folks generally approaching this top level build<br>
> target issue?<br>
<br>
</div>I tried to do it all in cmake for a while, but then I gave up and use a<br>
shell script or something to drive the inner builds. The problem was,<br>
some developers wanted to not build everything; they wanted<br>
precompiled versions of the other packages. And it was just too painful<br>
for some devs to build one way, and others to build another way.<br>
<span class="HOEnZb"><font color="#888888">- Dan<br>
</font></span></blockquote></div><br></div>