Hi,<br><br><div class="gmail_quote">On Fri, Jun 22, 2012 at 6:10 PM, Leif Walsh <span dir="ltr"><<a href="mailto:leif.walsh@gmail.com" target="_blank">leif.walsh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Suppose I have two projects, A and B. A builds a shared lib that links with a static lib in B.<br>
<br>
Sometimes, I want to build and test B by itself. Other times I want to build A, which requires building B.<br>
<br>
For now, I manually (or with a script) build B, then set an environment variable to say where the built static lib is, and then build A (which uses the environment variable). This is...not superb.<br>
<br>
If I wrote A's CMakeLists.txt to have add_subdirectory(B), it would error when it hit B's project(B). </blockquote><div><br></div><div>What makes you think that having 2 project() invocations in the same cmake source tree causes a problem for cmake? Or maybe this was a problem in some older versions of cmake, my 2.8.8 here groks a sample with 2 project() calls in a setup as you describe just fine.</div>
<div><br></div><div>Andreas</div></div>