Christian,
The bug I was talking about (project prefix) is in a Rule artifact.
I do something like (separated in multiple files but the same hierarchy)
Project{
property string myProp:"val"
Project{
Product{
Rule{
inputs:['myinputs']
Artifact {
fileName:project.myProp
}
}
}
This seems to work on my side but should not according to your answer to
Tim.
Regards
Olivier
> On 05/22/2014 04:00 PM, Tim Hutt wrote:
>> Relatedly, how can I access properties from a Rule's prepare script?
>> E.g. this does not work - it thinks foo is not defined.
>>
>> Rule {
>>
>>
>> property string foo: "baz"
>>
>>
>> prepare: {
>>
>> var /a = foo;/
>>
>> /
>> /
> Yeah, Rules (much like Artifacts) are not first-class items in that they
> don't really support adding custom properties in a meaningful way (i.e.
> you can't access them later from prepare scripts). Maybe that is worth
> changing. Jörg, what's your opinion on this?
>
>
> Christian
> _______________________________________________
> QBS mailing list
> QBS@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qbs
_______________________________________________
QBS mailing list
QBS@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qbs
