On Thu, Apr 9, 2009 at 12:59 PM, Paul Oppenheim (Poppy Linden) < [email protected]> wrote:
> Robert Dailey wrote: > >> Do you have unit tests that require failure to compile in order to be >> successful? If you do, placing these particular unit tests in a project with >> other tests that must compile to succeed will interrupt the process, >> depending on the order of compilation. >> > > 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. Ah, I see now. It was not immediately obvious to me what your code was doing. I didn't notice it was making each CPP file basically compile itself (Which is still just an assumption). Where is the implementation for "set_source_files_properties"?
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
