Re: [Boost-build] How to compile sub directories with relative paths (like make)

Subject: Re: [Boost-build] How to compile sub directories with relative paths (like make)
From: Nogradi, Chris (Chris.Nogradi_at_[hidden])
Date: 2011-12-29 17:36:19

It looks like $(PATH_BUILD) is the culprit.  How do you set that variable and is it a relative or absolute path?

Chris

-----Original Message-----
From: boost-build-bounces_at_[hidden] [mailto:boost-build-bounces_at_[hidden]] On Behalf Of "Häfemeier, Frank"
Sent: Tuesday, December 27, 2011 7:31 AM
To: boost-build_at_[hidden]
Subject: Re: [Boost-build] How to compile sub directories with relative paths (like make)

Hi Rene,

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++
>> project/sub4/source2.cxx'?
>
> 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:

project /root
  : build-dir
      $(PATH_BUILD)
  : requirements
      # always turn debug symbols on (also for release build variant)
      <debug-symbols>on
      <runtime-debugging>on
      # turn off optimization (also for release build variant)
      <optimization>off
      # custom warnings level
      <warnings>xyz
      <warnings-as-errors>on
                # enable 32-bit build on native 64-bit platforms
      <address-model>32
      <cflags>-Wa,--32
      # some settings from original Sniff-based build process
      <cxxflags>-pipe
      <cxxflags>-fsjlj-exceptions
      # preprocessor constants from original Sniff-based build process
      <define>OS_SYSV
      <define>OS_LINUX
      <define>OS_LINUX_1_0
      <define>__GLIBC__=2
      <define>_contigous_storage
      # include path for STL implementation
      <include>/usr/local/include/stlport
      # dependency on this Jamroot file
      <dependency>$(PATH_ROOT)/Jamroot
  : default-build
  : usage-requirements
;

Bye
        Frank

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.

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies.

Thank you for your cooperation.