From: Vladimir Prus (ghost_at_[hidden])
Date: 2007-04-30 15:19:33
> Phillip -
> Thanks for the feedback. If I remove the <include> from the Jamfile, the
> compile won't work, no matter where I am.
> Would I use the bhome entry you mentioned in the jamroot or the Jamfile?
> Aaron R>
> On 4/30/07, Phillip Seaver <phil_at_[hidden]> wrote:
>> DrAnonymous wrote, on 4/30/2007 11:52 AM:
>> > jamfile
>> > exe atrans : atrans.cpp : <include>$bhome ;
>> > When I am in subdir and do a bjam, I get an executable under the bin
>> > directory. If I try to do a bjam under the top directory, the include
>> > files aren't found. Why aren't the includes working from the Jamroot?
>> > The bhome env variable is defined as an absolute path.
>> I'm almost positive environment variables don't get added as jam
>> variables. You would need to do something like:
>> import modules ;
>> bhome = [ modules.peek : bhome ] ;
>> My guess would be that it's running the compile from whatever directory
>> you're in and picking up the includes from the working directory.
Whenever you want to use 'bhome'. There's no difference whatsoever between
Jamroot and Jamfile except that Jamroot inherit properties from user-config.jam,
while Jamfile -- from Jamfile/Jamroot in a parent directory.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk