Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Not Evaluated
-
Resolution: Done
-
Affects Version/s: 1.10.1
-
Fix Version/s: 1.12.0
-
Component/s: Language Syntax & Semantics
-
Labels:None
-
Commits:2b14c324a337fec379e77ce0c12e273d08934537
Description
The following project
// modules/mybuildconfig/mybuildconfig.qbs Module { property bool falseProperty: false } // app.qbs Product { condition: mybuildconfig.falseProperty Depends { name: "does.not.exist" } Depends { name: "mybuildconfig" } }
produces the error
app.qbs:4 Can't find variable: mybuildconfig
because mybuildconfig is indeed not loaded, because the module loader bails out as soon as does.not.exist cannot be loaded.
Reordering the Depends items fixes the problem.
// app.qbs Product { condition: mybuildconfig.falseProperty Depends { name: "mybuildconfig" } Depends { name: "does.not.exist" } }
This is especially harmful in cases where inheritance is involved, because that makes it hard to control the order of Depends items.
Attachments
Issue Links
- relates to
-
QBS-1310 Cannot use module properties for Depends.condition in base items
-
- Open
-