Re: [jamboost] Stage targets for V2

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-11-14 03:20:03

Rene Rivera wrote:

>>>In V1 I have this set for all my targets:
>>>
>>> <gcc><linkflags>"-Wl,-rpath -Wl,."
>>> <gcc><linkflags>"-Wl,-rpath -Wl,$(GCC_STDLIB_DIRECTORY)"
>>
>>Good. I think if we both need this feature, we can create a new feature for
>>it, something like <hardcode-dll-paths>?
> 
> 
> How about just the shorter <dll-path>; singular "path" seeing as one can
> only specify one at a time.

Where the value of ";" means "hardcode"? OK with me.

>>but this specified which variant of "mylib" to select, while what we
>>want is different processing for different sources. Maybe we can
>>extend this mechanism. If <use-symlinks> is incidential property
>>(the one which is assumed to not affect build products) then
>>
>> stage dist : mylib/<optimization>off/<use-symlink>yes ;
>>
>>would select the same variant of "mylib" as
>>
>> stage dist : mylib/<optimization>off ;
>>
>>However, we can make <use-symlink> somehow travel with the generated
>>target, so that stage rule can take care of it. It's not trivial.
> 
> 
> Looks obtuse... confusing.

That's why I didn't rush to implement this :-) Somethink like
this is needed, but not sure how.

> What we need is a way of synthesising targets inline. 

We do! I've just filed an issue on it
http://zigzag.cs.msu.su:7814/scarab/issues/id/BB2