Boost logo

Boost-Build :

From: John Reid (j.reid_at_[hidden])
Date: 2007-01-31 07:41:04

Ok I seem to have fixed this. So here's the answer:

In my exe target that depends on the lib bio target, I put the following
This causes the build/output directory to be in the #include search path.

I would like to put this in the usage requirements of the lib bio target
but this causes an infinite recursion :(

I worked this out by looking at:
which describes how to build a COM server with boost build.

BTW I am using BBv2.

I'm not sure this will help you though Noel. Perhaps you can look in BB
source code for how <implicit-dependency> works.


John Reid wrote:
> I have a custom generator that places C headers in the output directory.
> Other sources that are built in the same main target as the sources for
> the custom generator find these when they are #include'd. I have trouble
> getting source files in other main targets to include them though.
> What I'm trying to say is that I think I need similar functionality as
> Noel does and I can't find it in the docs...
> Any help appreciated.
> Thanks,
> John.
> K. Noel Belcourt wrote:
>>I'm compiling Fortran 90 with bjam and want to set a compile flag for
>>the Sun F90 compiler to tell it where to search for the Fortran 90
>>modules. Sun's F90 compiler has this flag, -moddir=path, that will
>>let me do this. Is there a bjam variable that I can access that has
>>the target's output directory for the currently building target? If
>>I could get the output directory from bjam, I could pass it to the
>>compiler like this.
>>project contact
>> : requirements
>> <toolset>sun:<fflags>-moddir=$(target-output-directory)
>> ;
>>This would be really handy. Any ideas if or how this can be done?
>>-- Noel Belcourt
>>Unsubscribe & other changes:
> _______________________________________________
> Unsubscribe & other changes:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at