Vladimir -
What would be the proper way to make this compile from the top directory? I believe I can add bhome as a default include path to all subprojects, but I don't know the syntax.
I'm still confused as to why I can't build from the top dir, when bhome is properly included in the sub-project's Jamfile?
Thanks,
Aaron R>
DrAnonymous wrote:
> 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?
>
> Thanks,
> Aaron R>
>
>
>
> On 4/30/07, Phillip Seaver <phil@apago.com> 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.
- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build