Could a warning be emitted on value overwrites though? Christian raises a very valid point of these errors being kinda difficult to trace. Obviously there will need to be a way to say to qbs that this write is valid to silence the warning though.
On Mon, Dec 18, 2017 at 1:21 PM, Christian Kandeler < [email protected]> wrote: > On Sun, 17 Dec 2017 08:53:42 +1300 > Christian Gagneraud <[email protected]> wrote: > > > Could someone explain the rules as to when to use base.concat or not, eg > is > > it necessary here just because of the group? Or should this be always > used? > > (Project, Product, Module, ...) > > You use "base" if and only if there is a base item that sets the > respective property and you want to merge the values. This happens often in > products, but if you find yourself deriving from a Module or Group item, > then the same logic also applies. > When setting module properties in a (non-derived) Group, you'll typically > use "outer" instead, which refers to the value in the surrounding product. > That should do the right thing even if the product does not set the module > property directly. > See also https://doc.qt.io/qbs/module-item.html#special-property-values > > > Christian > _______________________________________________ > Qbs mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qbs >
_______________________________________________ Qbs mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qbs
