$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2005-08-03 11:27:58
To my big surprise, I just discovered that defines are somehow not
propagated to dependencies, when using bbv1.
Example:
> cd boost-HEAD/libs/test/test
> bjam -a -n -sTOOLS=gcc -sBUILD="<define>FOOBAR"
[snip]
gcc-C++-action
../../../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc/debug/compiler_log_formatter.o
set -e
"g++" -c -Wall -ftemplate-depth-255 -DBOOST_TEST_NO_AUTO_LINK=1 -g
-O0 -fno-inline -I"../../../bin/boost/libs/test/build" -I "/v
ol2/boost/boost-HEAD" -o
"../../../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc/debug/compiler_log_formatter.o"
"/vol2/boo
st/boost-HEAD/libs/test/build/../src/compiler_log_formatter.cpp"
[snip]
gcc-C++-action
../../../bin/boost/libs/test/test/class_properties_test.test/gcc/debug/class_properties_test.o
set -e
"g++" -c -Wall -ftemplate-depth-255 -DBOOST_TEST_NO_AUTO_LINK=1
-DFOOBAR -g -O0 -fno-inline -I"../../../bin/boost/libs/test/test"
-I "/vol2/boost/boost-HEAD" -o
"../../../bin/boost/libs/test/test/class_properties_test.test/gcc/debug/class_properties_test.o"
"class_p
roperties_test.cpp"
[snip]
Note that in the first C++ action (when the test library is built), FOOBAR
is not defined, but it is in the second (when the tests are built). Is this
behaviour intended? Or is it somehow caused by the Jamfiles of boost.test?
TIA, Markus