[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

Re: [Boost-cmake] Merging problems with CMakeLists.txt and related files

TortoiseSVN is showing you a diff in metadata properties on the two files, not in the file content itself. Right click on a file in Windows Explorer and choose "TortoiseSVN > Properties" (near the bottom of the submenu) to see what properties a given file has in svn. (Or do an "svn proplist filena

Re: [Boost-cmake] CMake for development testing

David Abrahams wrote: 67/ 79 Testing Python-resultPassed 68/ 79 Testing Python-string_literal ***Failed 69/ 79 Testing Python-borrowed ***Failed 70/ 79 Testing Python-object_managerPassed 71/ 79 Testing Python-copy_ctor_mutates_rhs Pa

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

Re: [Boost-cmake] CMakeLists.txt missing copyright and licence

Jeremiah Willcock wrote: The CMake-based build system should not be removed, even temporarily, in my opinion. Nick Edmonds and I depend on it because it is the only way to run the tests for Boost.MPI and the parallel parts of Boost.Graph. In particular, it is essential to be able to run the

[Boost-cmake] Problem with Linking CXX shared module

Hi All, I'm using "NMake Makefiles" and my attempt to run nmake failed with the following errors: Scanning dependencies of target hello [100%] Building CXX object CMakeFiles/hello.dir/hello.cpp.obj hello.cpp Linking CXX shared module hello.dll LINK : fatal error LNK1104: cannot open fil

Re: [Boost-cmake] CMakeLists.txt missing copyright and licence

Jeremiah Willcock wrote: > On Fri, 29 May 2009, troy d. straszheim wrote: > >> Beman Dawes wrote: >>> This is causing lots of inspect failures. See >>> http://boost.cowic.de/rc/inspect-trunk.html >>> >>> I'd like to see these cleared ASAP so I can pester developers about their >>> real inspect p

[Boost-cmake] CMake thoughts

Hi, The preliminary CMake file in the distr. (1.38.0) is IMHO way, WAY too complex. It makes no sense to have each sublib as a separate project, and in all different flavors at that (debug/rel/mt/st). It seems as it is designed just to create the boost libraries, which in my view in a non-sens

Re: [Boost-cmake] CMake for development testing

Excerpts from David Abrahams's message of Fri Jun 05 23:09:44 +0200 2009: > However, the way CMake reports failures really doesn't fit in with my > development workflow. I'm doing > > make Python-test > > and what I get back looks something like this: > > ... > > 67/ 79 Testing Pyt

Re: [Boost-cmake] CMakeLists.txt missing copyright and licence

On Sun, 31 May 2009, Vladimir Prus wrote: Jeremiah Willcock wrote: On Fri, 29 May 2009, troy d. straszheim wrote: Beman Dawes wrote: This is causing lots of inspect failures. See http://boost.cowic.de/rc/inspect-trunk.html I'd like to see these cleared ASAP so I can pester developers about

Re: [Boost-cmake] CMake thoughts

Thoughts are inline.. On Jun 2, 2009, at 3:40 AM, Robert Bielik wrote: Hi, The preliminary CMake file in the distr. (1.38.0) is IMHO way, WAY too complex. It makes no sense to have each sublib as a separate project, and in all different flavors at that (debug/rel/mt/st). It seems as it

Re: [Boost-cmake] CMake thoughts

Michael Jackson wrote: What _really_ needs to be done, for BOTH the bjam and the cmake based builds is to produce a "UseBoost.cmake" file akin to the UseQt4, UseVTK, UseITK, UseParaView that are either included with CMake or produced by the build system then installed into the installation loca

Re: [Boost-cmake] CMake thoughts

On Jun 8, 2009, at 10:00 AM, Brad King wrote: Michael Jackson wrote: What _really_ needs to be done, for BOTH the bjam and the cmake based builds is to produce a "UseBoost.cmake" file akin to the UseQt4, UseVTK, UseITK, UseParaView that are either included with CMake or produced by the bu

Re: [Boost-cmake] CMake for development testing

Brad King wrote: David Abrahams wrote: 67/ 79 Testing Python-resultPassed 68/ 79 Testing Python-string_literal ***Failed 69/ 79 Testing Python-borrowed ***Failed 70/ 79 Testing Python-object_managerPassed 71/ 79 Testing Python-copy_ctor_

Re: [Boost-cmake] CMake thoughts

FYI, the "Use-file" approach in CMake land has been superceded by CMake package files: http://www.cmake.org/Wiki/CMake_2.6_Notes#Packages If Boost were to provide BoostConfig.cmake and BoostConfigVersion.cmake files in its installation, then 'FindBoost.cmake' will be very simple. All problems w

[Boost-cmake] revision 50756 failed to merge some file properties [was: Merging problems with CMakeLists.txt and related files]

David Cole writes: > > > TortoiseSVN is showing you a diff in metadata properties on the > two files, not in the file content itself. Right click on a file > in Windows Explorer and choose "TortoiseSVN > Properties" (near > the bottom of the submenu) to  see what properties a given file > has i