Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2005-05-31 15:25:25

Vladimir Prus <ghost_at_[hidden]> writes:

> 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 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?

Yes. We need a way of deciding to generate the manifest action, but
only in the case where we're building a DLL (or a PYD).

> If yes, adding the necessary information to the property set passed
> to rule should be easy.

Okay, please go for it then!

Dave Abrahams
Boost Consulting

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