I'm still looking to figure out how a single project can be configured to generate multiple executables. Can anyone clarify?<br><br><div class="gmail_quote">On Thu, Apr 9, 2009 at 1:30 PM, Robert Dailey <span dir="ltr"><<a href="mailto:rcdailey@gmail.com">rcdailey@gmail.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="gmail_quote"><div class="im">On Thu, Apr 9, 2009 at 12:59 PM, Paul Oppenheim (Poppy Linden) <span dir="ltr"><<a href="mailto:poppy@lindenlab.com" target="_blank">poppy@lindenlab.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't have that particular case, but I could support it. With my scenario each test is its own binary. This is normally messy, but because tests are built in sub-projects it's not noticeable in the main build. Each group of tests looks like one test in the main build, but are completely separate in the sub-build.</blockquote>
<div><br></div></div><div>I don't see how you are forcing each CPP to result in an executable. Could you explain? Also, if one source file fails to compile, will the rest of the source files continue to compile or not? </div>
</div>
</blockquote></div><br>