[QBS] Properties and base.concat (was: Quick reference for porting pro files?)

[Tom Sutcliffe]

Hi Jörg,

Thanks for the updates. I'm still not totally clear on the rules for how properties get overridden - is the following about right as a recommendation?

* Specifying cpp.defines as a raw list is almost always the wrong thing to do - ie this is bad: cpp.defines: ["MY_DEFINE"]
* Almost always you should be using base.concat - ie: cpp.defines: base.concat(["MY_DEFINE"])
* Inside a group, you should probably use outer.concat(["GROUP_SPECIFIC_DEFINE"])

Are there any other properties that we need to be wary of assigning directly to because of stuff done behind the scenes? Eg cpp.includePath? Is cpp.defines going to become enough of a gotcha that it'd be better to define UNICODE etc some other way (similar to what you said in your other mail I guess?). Is there any legitimate situation where you might want to exploit this behaviour to undefine a platform-defined macro?

Cheers,

Tomsci

On Mar 05, 2012, at 09:44 AM, Joerg Bornemann <joerg.bornemann at nokia.com> wrote:

> On 04/03/2012 23:09, ext Tom Sutcliffe wrote:
> 
> > Thanks. I've included this in the guide I've started here:
> >
> > http://qt-project.org/wiki/Qbs_Quick_Reference
> 
> Great initiative! I will have a look at it and add some things (and 
> answer the questions in it).
> 
> 
> BR,
> 
> Jörg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qbs/attachments/20120305/9f068693/attachment.html>