Ingo Albrecht wrote:
Note that vcbuild (the command line driver for VS builds) has command
line arguments for specifying strings to prefix log messages at various log
levels with. This should make log scraping of the compilation much more
reliable, although it still disgusts me. This does not work for CTest
though
because it tests using cmake scripts.
Running vcbuild is certainly no alternative for trying the build in the
IDE,
but it should be sufficient for continuous integration.
Further, I have to note that command-line VS builds should be
supported for one simple reason: nmake does not support parallel
builds and probably never will. This makes VS the easiest way of
running a parallel build on Windows (locally or distributed with
additional tools). GNU make from MSYS is out of the question
because MSYS seems far from production-grade.
Should IDE builds be considered support-worthy, it would of
course be necessary to test manually before releases.
I hope that some of this helps
Interesting, thanks for this. Would the 'cwrap' approach (where the
compiler is called via a wrapper) work under vcbuild? (Forgive me, I
don't do windows). The only reason I paid attention to NMAKE is that it
was somewhat familiar to me.
-t
_______________________________________________
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-cmake
