Boost logo

Boost-Build :

From: aulwelling_at_[hidden]
Date: 2007-03-13 12:27:17


> Message: 6
> Date: Tue, 13 Mar 2007 09:49:19 +0300
> From: Vladimir Prus <ghost_at_[hidden]>
> Subject: Re: [Boost-build] [bbv2] Path to generated files
> To: boost-build_at_[hidden]
> Message-ID: <200703130949.20009.ghost_at_[hidden]>
> Content-Type: text/plain; charset="iso-8859-15"
>
> On Monday 12 March 2007 19:10, aulwelling_at_[hidden] wrote:
> > I haven't had much luck with descriptive questions so I'll
> keep this one
> > short.
>
> Which "descriptive questions" you have in mind? If there's some
> unanswered email, then pinging it it usually effective.
 
I will ping them separately then. One of them provides a lot more
detail on what I'm trying to do.

> > I have a custom rule that calls the lib rule. From my custom rule I
> > need to know path where all generated files will go for the current
> > target (.o, .so, etc.). How do I get this path?
>
> I don't know how you've defined the rule, but you generally cannot
> find that out, because bjam might be invoked with 10 different
> sets of properties.

Here is a pared down example of my rule:

rule mylib ( Libname : sources * )
{
  lib $(Libname)
    : $(sources)
      version.cc
    :
    ;

  make version.cc : $(sources) : generateCode ;
}

$(Libname), version.cc, version.o, etc all go into the same directory,
which is what I need.

> Inside a custom generator, once some virtual target are created,
> calling 'path' method on them will work.
>
> - Volodya

What is a virtual target and how do I make one? Do I want to? What
kind of a target is version.cc in my above example? I've read the
snippet about virtual targets here:
http://boost.org/boost-build2/doc/html/bbv2/builtins/raw.html and I
don't understand how they are used. I've searched the list as well and
pretty much found only error messages. Any help would be greatly
appreciated.

Thanks,
Ashley


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