|
Boost-Build : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-05-30 01:11:19
On Friday 27 May 2005 21:12, David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> >> Volodya, why is this target being labelled as type RUN_PYD?! In v1,
> >> that target type is reserved for the result of running a test on a
> >> Python extension module. And v2 seems to be written with the same
> >> intention. Python modules should have type PYD, no?
...
> > And 'make-test' indeed defines main target with the 'run-pyd' type. So
> > the above output is certainly intended. You're probably looking at a way
> > to check the type of the actual target we're creating.
>
> Yes.
>
> > Unfortunately, it's not possible from the msvc.link rule.
> >
> > It's easy to add this information, by hacking action.actualize (line 679
> > in my copy). However, there's one question -- what if an action produces
> > two targets? Which type should be add?
>
> Both, obviously.
Ok, I'm +-0.
> > Those of the first produced target (recall that order of the targets
> > is always the same as specified when declaring a generator).
>
> Is that a question or an assertion?
That was a question. I think I've missing the conclusion of that 'vc8.0
manifect' issue -- is it still needed to do something? If yes, adding the
necessary information to the property set passed to msvc.link rule should be
easy.
- Volodya
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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