aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Weickelt <richard@weickelt.de>2021-02-13 23:45:20 +0100
committerRichard Weickelt <richard@weickelt.de>2021-02-14 06:55:34 +0000
commit55f34da0a55d979c685e6693a177d8937363e0f1 (patch)
tree4132c61c367f7094da442d1a9a84edbe7735e6d0
parented47bcbd9536c133499c1bcb8e6188dc9cd2b6df (diff)
Get rid of product.moduleProperty() during project resolving
Although not documented, it was possible to access module properties via product.moduleProperty("module", "property"). That is still possible in the QJS port of Qbs, but would complicate the implementation of Evaluator unnecessarily. After all it was only needed in a single place. It can still be used in rules. Change-Id: I40f374a57a6fefc85eb45250b472fe732b66f0b7 Reviewed-by: Ivan Komissarov <ABBAPOH@gmail.com>
-rw-r--r--share/qbs/modules/bundle/bundle.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/share/qbs/modules/bundle/bundle.js b/share/qbs/modules/bundle/bundle.js
index 6d9305702..6bb43ecdc 100644
--- a/share/qbs/modules/bundle/bundle.js
+++ b/share/qbs/modules/bundle/bundle.js
@@ -89,7 +89,7 @@ function productTypeIdentifier(productType) {
}
function excludedAuxiliaryInputs(project, product) {
- var chain = product.moduleProperty("bundle", "_productTypeIdentifierChain");
+ var chain = product.bundle._productTypeIdentifierChain;
var bestPossibleType;
for (var i = chain.length - 1; i >= 0; --i) {
switch (chain[i]) {