|
Boost-Build : |
Subject: Re: [Boost-build] Projects requirements and alternative selection
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-04-16 12:01:39
On Thursday 16 April 2009 17:08:26 Hartmut Kaiser wrote:
> > Vladimir Prus wrote:
> > > On Wednesday 15 April 2009 16:38:28 Johan Nilsson wrote:
> > >> Hi,
> > >>
> > >> I'm experiencing some "problems" with target selection. A simplified
> > >> example:
> > >>
> >
> > [snip]
> >
> >
> > >> Is this as expected - I had a gut feeling that the requirements set
> > >> by "project" should be added to the "build" request for the bar lib
> > >> in the above scenario?
> > >>
> > >> I've tried the above using Boost.Build from trunk as well as from
> > >> 1.34.1. Toolset is msvc (set in user-config.jam).
> > >
> > > You are hitting:
> > >
> > > http://zigzag.lvk.cs.msu.su/boost.build/ticket/16
> > >
> > > I'd recommend that instead of alternatives, you use one target with
> > > indirect conditional requirements that computes <file> property as
> > > necessary.
> >
> > Is that the recommended long-term approach as well? Seems a bit awkward
> > to
> > me.
> >
> > Would it be possible for you to describe a bit more in detail what
> > happens/should happen in the actual implementation and also list a
> > couple of
> > possible approaches to fix this? I could take a look at it.
>
> Please excuse my ignorance, but exactly how am I supposed to fix (work
> around) my problem?
Sorry, what problem? I don't think I see any email from you in this
thread -- neither in my mailer or not gmane.org.
- Volodya
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