<div><div class="gmail_quote">On Wed, May 20, 2009 at 9:38 PM, Philip Lowman <span dir="ltr"><<a href="mailto:philip@yhbt.com">philip@yhbt.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 Wed, May 20, 2009 at 9:40 PM, Robert Dailey <span dir="ltr"><<a href="mailto:rcdailey@gmail.com" target="_blank">rcdailey@gmail.com</a>></span> wrote:<br>> I'm still looking to figure out how a single project can be configured to generate multiple executables. Can anyone clarify?<br>
<br></div>A Visual Studio project file is limited to one target (executable, library, etc.) as far as I know. If this is what you're asking.<br><br>At work what we do is clump our unit tests for each class (in a library) into a single unit test executable. In this way we minimize the number of executables linked and the number of tests that run and show up in Visual Studio.<br>
<br>We use gtest but the same principals apply with cxxtest, cppunit, etc.</blockquote><div><br></div><div>This idea would work perfectly if I did not have compile time unit tests. For example, some unit tests pass if they fail to compile, or pass if they compile successfully. It's the former case that makes this idea impossible to use. </div>
</div></div>