[QBS] Properties and base.concat

[Tom Sutcliffe]

>> Are there any other properties that we need to be wary of assigning directly to because of stuff done behind the scenes

What about cpp.includePaths? I fell over this in \qbs\share\qbs\imports\qbs\base\QmlApp.qbs:

Product {
    type: ["application", "installed_content"]
    Depends { name: "qt.declarative" }
    Depends { name: "cpp" }
    property string appViewerPath: localPath + "/qmlapplicationviewer"
    cpp.includePaths: [appViewerPath]

    Group {
        files: [
            appViewerPath + "/qmlapplicationviewer.h",
            appViewerPath + "/qmlapplicationviewer.cpp"
        ]
    }

Should this be changed too, so that a user assigning to cpp.includePaths inside a QmlApp doesn't stomp over this defnition by mistake?

Cheers,

Tom

On 07 Mar, 2012,at 01:05 PM, Joerg Bornemann <joerg.bornemann at nokia.com> wrote:

> On 06/03/2012 12:58, ext Joerg Bornemann wrote:
> 
> > I propose to have cpp.defines initially empty and have another property
> > for initial defines.
> 
> commit f3feb2464f92e98098d62df33b2a08fa6975c8b3
> Author: Joerg Bornemann <joerg.bornemann at nokia.com>
> Date: Wed Mar 7 13:39:35 2012 +0100
> 
> cpp module: separate platform defines and user defines
> 
> The cpp module got a new property platformDefines.
> That's e.g. used on Windows to define UNICODE.
> 
> The standard way to set user defines is now
> cpp.defines: ['NARF', 'ZORT']
> again.
> 
> 
> Wiki page updated.
> 
> 
> 
> BR,
> 
> Jörg
> _______________________________________________
> QBS mailing list
> QBS at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qbs

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