Subject: Re: [Boost-build] How to compile sub directories with relative paths (like make)
From: Häfemeier, Frank (frank.haefemeier_at_[hidden])
Date: 2011-12-27 08:30:42
On 12/21/2011 10:26 AM, "Rene Rivera" wrote:
> On 12/20/2011 10:26 AM, "H?femeier, Frank" wrote:
>> Is there a way to prevent the compiler calls using the absolute path
>> and instead using the relative path for example 'gcc.compile.c++
>> project/sub1/source1.cxx' or 'gcc.compile.c++
> I'm not sure how you are getting it to use absolute paths since you
> didn't post a use case. But BB normally uses relative paths for everything.
I am myself not sure how we get absolute paths. I see in the log output a compiler call which has absolute paths. With the example in my original posts a call with absolute path is 'gcc.compile.c++ /home/user/project/sub1/source1.cxx'. I would prefer the call without '/home/user', means 'gcc.compile.c++ project/sub1/source1.cxx'.
In Jamroot we use the following project definition:
# always turn debug symbols on (also for release build variant)
# turn off optimization (also for release build variant)
# custom warnings level
# enable 32-bit build on native 64-bit platforms
# some settings from original Sniff-based build process
# preprocessor constants from original Sniff-based build process
# include path for STL implementation
# dependency on this Jamroot file
Think green - keep it on the screen.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
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