Re: [Boost-build] really dumb boost build question

Subject: Re: [Boost-build] really dumb boost build question
From: Robert Ramey (ramey_at_[hidden])
Date: 2016-01-26 15:39:47

--- Original Message ----- 
  From: Vladimir Prus 
  Newsgroups: gmane.comp.lib.boost.build
  To: Boost.Build developer's and user's list 
  Sent: Tuesday, January 26, 2016 8:50 AM
  Subject: Re: really dumb boost build question

  Robert,

  Did you do 'b2 headers'?

Here's a more complete discription.

My system is an XP with msvc 9.0 installed.  I use cygwin for my shell.  It has installed the command line git as well.  I followed the instruction for cloning the whole of Boost on this machine and selecting serialization library for development.  I use bootstrap.sh to build the local version of b2.

As a test, I invoke

$b2 toolset=gcc variant=debug link=shared test_native_array_xml_warchive >b2.log &  

and things seem to go as expected.  That is, all libraries required for the test build, the test builds, runs and fails - I expect this to happen.

But when I change to the following command line to:

$b2 toolset=msvc variant=debug link=shared test_native_array_xml_warchive >b2.log &

I get a b2.log file which contains in part

...patience...
...patience...
...found 2465 targets...
...updating 69 targets...
compile-c-c++ ../../../bin.v2/libs/config/test/all/no_std_wstreambuf_pass.test/msvc-9.0/debug/threading-m
ulti/no_std_wstreambuf_pass.obj
no_std_wstreambuf_pass.cpp
C:\modular-boost\libs\config\test\no_std_wstreambuf_pass.cpp(21) : fatal error C1083: Cannot open include
 file: 'boost/config.hpp': No such file or directory

    cmd.exe /S /C call "C:\Program Files\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" x86 ">nul" "&&" cl
 /Zm800 -nologo @"C:\modular-boost\bin.v2\libs\config\test\all\no_std_wstreambuf_pass.test\msvc-9.0\debug
\threading-multi\no_std_wstreambuf_pass.obj.rsp"

...failed compile-c-c++ ../../../bin.v2/libs/config/test/all/no_std_wstreambuf_pass.test/msvc-9.0/debug/t
hreading-multi/no_std_wstreambuf_pass.obj...

every attempt to compile fails in the same way. So it's not finding the boost headers.  In searching for the cause/fix for this I do the following:

$# display current directory

$pwd
/cygdrive/c/modular-boost/libs/serialization/test

$# check value of BOOST_ROOT 

$echo $BOOST_ROOT

$# verify that file actually exits

$ls ../../../boost/config.hpp
../../../boost/config.hpp

$# verify contents of file

$cat ../../../boost/config.hpp
//  Boost config.hpp configuration header file  ------------------------------//

//  (C) Copyright John Maddock 2002.
//  Use, modification and distribution are subject to the
//  Boost Software License, Version 1.0. (See accompanying file
//  LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
...

Just to be sure I try

$pwd
/cygdrive/c/modular-boost/libs/serialization/test
$export BOOST_ROOT="cygdrive/c/modular-boost"
$echo $BOOST_ROOT
cygdrive/c/modular-boost

$b2 toolset=msvc variant=debug link=shared test_native_array_xml_warchive >b2.log &

with the same results.

What is the best way to get past this?

Robert Ramey