Re: [Boost-build] Unable to run sandbox tests in own directory

Subject: Re: [Boost-build] Unable to run sandbox tests in own directory
From: Edward Diener (eldiener_at_[hidden])
Date: 2010-11-29 19:23:36

On 11/29/2010 6:52 PM, Daniel James wrote:
> On 29 November 2010 23:17, Edward Diener<eldiener_at_[hidden]>  wrote:
>>
>> If I go to the 'example' test directory and try the above 'bjam' line things
>> get even worse, with the output:
>
> Sorry, that should be fixed now, it was missing a 'using testing' line.

Thanks ! Yours is now working but mine is still failing. I have no idea 
why that is. Is there some bjam command-line parameter that shows me 
which jamfiles/lines are being processed when I try to run my test 
jamfile ? Other than that shot I have no idea how I can find out why the 
boost header file is not being found, since it is clearly there. 
Somehow, despite the <include>$(boost-root) in the top-level Jamfile.v2, 
the same that is in the top-level directory of 'example' it is not 
finding my Boost distribution when I specify 
--boost=C:/Programming/VersionControl/boost on the command line because 
the compilation which includes my header file which has an

#include <boost/config.hpp>

tells me that 'boost/config.h' can not be found.