"Christian Henning"
Alright I'm getting the same output. I haven't know that I need to set some environmental variables. So, back to my question how do I build the guid id lib? This is what I tried:
shell> set BOOST_ROOT=C:\boost shell> set BOOST_BUILD_PATH=C:\boost\tools\build\v2 shell> bjam --version Boost.Build V2 (Milestone 10) Boost.Jam 03.1.13
This is good; it's obviously using BBv2.
shell> bjam -sTOOLS=vc-7_1 --libdir=c:\boost\lib --with-guid stage
OK, -sTOOLS=... is a BBv1-style option. You need toolset=msvc
C:/boost/tools/build/v1\testing.jam:12: in load ^^
Whoops; it seems to have picked up a v1 jamfile. I suggest cd C:\boost\tools\build del /f/s/q v1 and then try the whole thing again.
rule difference unknown in module testing.
The rest looks OK, in principle.
C:\boost\tools\build\v2/kernel\modules.jam:259: in import C:/boost/tools/build/v2/build\project.jam:723: in project._using C:/boost/tools/build/v2/build\project.jam:748: in using project-root.jam:6: in modules.load C:/boost/tools/build/v2/build\project.jam:306: in load-jamfile C:/boost/tools/build/v2/build\project.jam:68: in load C:/boost/tools/build/v2/build\project.jam:164: in project.find C:/boost/tools/build/v2\build-system.jam:136: in load C:\boost\tools\build\v2/kernel\modules.jam:259: in import C:\boost\tools\build\v2/kernel/bootstrap.jam:153: in boost-build C:\boost\boost-build.jam:16: in module scope
That obviously hasn't worked. Any ideas? Do you think I should get the latest source code tree, maybe?
Thanks for you help, Christian
-- Dave Abrahams Boost Consulting www.boost-consulting.com