Re: [Boost-cmake] Parallel Builds on Windows
David Abrahams schrieb: on Thu Feb 05 2009, Michael Jackson wrote: There are those in the CMake community that successfully combine "unix makefiles" with the Visual Studio Compilers to perform parallel builds. http://www.cmake.org/pipermail/cmake/2008-June/022178.html is one of the relevant threads. Here is another thread that has some important information about exactly what versions of gmake and others to use. http://www.cmake.org/pipermail/cmake/2008-April/021336.html If that's the only path to parallel builds with CMake on windows, it seems like a very significant weakness. For a UNIX hacker like myself, it certainly seemed this way initially. I did change my mind though, after a while. My reasoning is that VC just turns out to be the predominant build tool on Windows today and has ended decades of fighting with UNIXoid make tools on a platform that requires its own way. Microsoft made it quite possible to use VC for builds exclusively by improving support for command-line builds over the years. Among open source libraries supporting windows, there are, in my mind, two categories. One is using vcbuild. The other one uses mingw and autoconf/make. Just guess which of the two made a more polished and integrated impression on me... Greets Ingo ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] Parallel Builds on Windows
Bill Hoffman schrieb: Beman Dawes wrote: On Sun, Feb 8, 2009 at 6:58 AM, David Abrahams wrote: But the real problem here is that anyone wanting to contribute a testing server will have a tough time making good use of his hardware, because --- unless I'm mistaken --- you can't automate the VS-based builds. ...or am I missing something? Isn't that what msbuild does? It is totally automated. You can run devenv /build on the command line or use msbuild, they do not pop up a gui. ctest uses devenv /build. All of this is already automated by ctest. The question is about log scrapping, which needs to be done. However, vs does create html logs during the build, and you should be able to use them with not too much effort. This is no longer true. Since VS2005, there is another tool called vcbuild that does not only emit messages on its stdout but can also dump them into a good old text file. As I already noted earlier, it can also prefix lines with specific severity levels with strings provided on the command line. It even has an advantage over make in that it can separate messages from parallel jobs correctly. This tool is also available in the free Express Edition. ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] Parallel Builds on Windows
On Mon, Feb 9, 2009 at 5:13 AM, Ingo Albrecht wrote: > ... Since VS2005, there is another tool called vcbuild > that does not only emit messages on its stdout but can also dump them > into a good old text file. As I already noted earlier, it can also prefix > lines with specific severity levels with strings provided on the command > line. > > It even has an advantage over make in that it can separate messages > from parallel jobs correctly. > > This tool is also available in the free Express Edition. Thanks! I'd missed vcbuild. It looks very interesting. --Beman ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
Re: [Boost-cmake] Parallel Builds on Windows
Ingo Albrecht wrote: It is totally automated. You can run devenv /build on the command line or use msbuild, they do not pop up a gui. ctest uses devenv /build. All of this is already automated by ctest. The question is about log scrapping, which needs to be done. However, vs does create html logs during the build, and you should be able to use them with not too much effort. This is no longer true. Since VS2005, there is another tool called vcbuild that does not only emit messages on its stdout but can also dump them into a good old text file. As I already noted earlier, it can also prefix lines with specific severity levels with strings provided on the command line. It even has an advantage over make in that it can separate messages from parallel jobs correctly. This tool is also available in the free Express Edition. I will look into using vcbuild, and parsing the output. I guess since we had devenv /build working, I did not figure vcbuild would have anything extra to add, sounds like it might. -Bill ___ Boost-cmake mailing list Boost-cmake@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
