Re: [Boost-build] Best way to include platform specific sources?

From: Daniel Einspanjer (deinspanjer_at_[hidden])
Date: 2006-02-10 11:48:11

I noticed one other oddity that I think might be a bug.  Please see the 
bottom of this e-mail...

"Daniel Einspanjer" <deinspanjer_at_[hidden]> wrote in message news:...
> rule select_platform_specific_sources ( properties * )
> {
>    if <os>NT in $(properties)
>    {
>        return <build>no ;
>    }
>      ...
> }
> obj platform_specific_sources
>    : # sources
>    : # requirements
>        <conditional>@select_platform_specific_sources
>    ;
> lib util
>    : # sources
>        #... normal sources here
>        platform_specific_sources
>    : # requirements
>    ;
> [C:\src\testproj\engine\cpp\util\common]bjam util
> Skipping build of 
> ../../../../engine/cpp/util/common/platform_specific_sources -- <build>no 
> in properties.
> ...patience...
> ...found 468 targets...
> ...updating 91 targets...
> MkDir1 ..\..\..\..\product\build

MkDir1 
..\..\..\..\product\build\engine\cpp\util\common\internal\msvc\debug\build-no
MkDir1 
..\..\..\..\product\build\engine\cpp\util\common\internal\msvc\debug\build-no\runtime-debugging-off

I just noticed that on NT, my util lib gets built into a build-dir 
containing build-no.  At the most, I would expect to see the 
platform_specific_sources rsp files in a build-no directory, certainly not 
the files that actually did get built.

Daniel