Re: [Boost-cmake] Testing dependencies

On Thu, Jun 11, 2009 at 5:50 AM, Brad King wrote: > Instead we should have one add_custom_target() to do all the tests > for a single library (e.g. function).  Within the target there would > be file-level rules created by add_custom_command().  This will > translate to one .vcproj file per library

Re: [Boost-cmake] Testing dependencies

Beman Dawes wrote: On Mon, Jun 8, 2009 at 9:17 AM, Brad King wrote: However, the major step before that is to package all tests for each library into test-driver executables. This is useful whether using bjam or CMake because it drastically reduces the total link time and disk space used for bu

Re: [Boost-cmake] Testing dependencies

Vladimir Prus wrote: This is what Troy's custom-target-per-test approach last year tried to do, but it was not scalable. In what way, and why and can *that* be fixed? Troy's solution used one add_custom_target() for each test. This translates into one .vcproj file per test on Visual Studio

Re: [Boost-cmake] Testing dependencies

Brad King wrote: > David Abrahams wrote: >> I just realized we need a feature (surprise!) >> >> When I'm working on a Boost library, I need to be able to fire off all >> the tests of libraries that depend on the one I'm changing, to make sure >> I'm not breaking anything in the library collection

Re: [Boost-cmake] Testing dependencies

On Mon, Jun 8, 2009 at 9:17 AM, Brad King wrote: > David Abrahams wrote: >> >> I just realized we need a feature (surprise!) >> >> When I'm working on a Boost library, I need to be able to fire off all >> the tests of libraries that depend on the one I'm changing, to make sure >> I'm not breaking a

Re: [Boost-cmake] Testing dependencies

David Abrahams wrote: I just realized we need a feature (surprise!) When I'm working on a Boost library, I need to be able to fire off all the tests of libraries that depend on the one I'm changing, to make sure I'm not breaking anything in the library collection before I check in. We discusse

[Boost-cmake] Testing dependencies

I just realized we need a feature (surprise!) When I'm working on a Boost library, I need to be able to fire off all the tests of libraries that depend on the one I'm changing, to make sure I'm not breaking anything in the library collection before I check in. Thoughts? -- Dave Abrahams BoostP