| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Parameters of Depends items within Export items were ignored.
Project {
Product {
name: "foo"
Export {
Depends { name: "dep"; cpp.link: false } // dep
}
}
Product {
name: "bar"
Depends { name: "foo" }
}
}
The instance of foo in bar has an Depends child depinst. The item
depinst was created by createChildInstances and is an empty item with
the prototype dep, which is the Depends item in foo's Export item.
Thus, extractParameters must look up properties in the deepest
prototype (dep), not in the Depends item itself (depinst).
Unfortunately, this fix triggers
SOFT ASSERT: varValue in ../../../../1.10/src/lib/corelib/language/evaluatorscriptclass.cpp:574
which will be fixed separately.
Task-number: QBS-1287
Change-Id: I56b5464aad2578bb5ddab2e831fc607d6634ac8d
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After adding an external file dependency, we would never remove it from
the global list again, meaning the look-up table would contain stale
entries if an external header file was moved around. Because we still
checked the status of the artifact-local list of dependencies, the
result was that in such a situation, the files including such a header
would get recompiled on every build.
[ChangeLog] Fixed constant rebuilding after moving an external header
file.
Task-number: QBS-1285
Change-Id: Id764da7485dd540f2ff64bcd890e43723f18e6cd
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Dependencies must be merged before their dependents, because the merging
process for the former sets up data to be consumed by the merging
process for the latter.
Task-number: QBS-1275
Change-Id: Ide9146add79bf2b4fcf80d7ce95ac1d9d4ac20b2
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
Only the values in Depends items of products had a scope, and that one
did not allow to access module instances.
Now the scope always is the surrounding item, which should be a sensible
one in all contexts.
Task-number: QBS-1253
Change-Id: Iedca2d98f82f71887373579f8e4dc91f057eded3
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
...rather than leaving them undefined. This way, the string "undefined"
will not end up in file names.
It's safer to do it this way compared to checking for "undefined" in all
the places that could make use of the properties. Due to the semantics
of these properties, there is also no value in treating "undefined" in a
special way.
Task-number: QBS-1265
Change-Id: I6ce7626485baa284a6c782b513740f9d150e18c3
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
|
| |
|
|
|
|
| |
Task-number: QBS-1256
Change-Id: I286327f8b33ecb72851551bbbf2108717a116b1a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Problem was uncovered by d08ce8f643, after which the Depends item used
for loading a module is no longer the original one from the prototype
(i.e. the one that got the id assigned by the AST visitor).
Task-number: QBS-1264
Change-Id: Id8bdf0cc903aaabfb3eaafc56445064ed49d1cd7
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
| |
|
|
|
|
|
|
|
| |
The input to the look-up function is a relative file path, not
necessarily just a file name as the code assumed.
Task-number: QBS-1261
Change-Id: Iaad4629ea92f327edc3dca7f012d82a00669994f
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
| |
|
|
|
| |
Change-Id: I7b8a3f0a05a4af793c8ded6de9642184c15fc331
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
|
|
Move over one change that did not make it into 1.10.0.
Change-Id: Id960525fd829da133b61c1c3cfed782b50a5273c
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
