I updated QtC to version 4.12.3 (QBS 1.16.0). After that, parsing my
project from scratch took 4-7 seconds. With this times is possible to
work quite comfortably. Thanks for speeding up! :)))
--
BR, Pavel Karelin
30.06.2020 18:09, Jochen Ulrich пишет:
Nice!
It brings a ~44% speed improvemen
Nice!
It brings a ~44% speed improvement in the problematic case according to your
numbers:
> Resolving withLeafExports/9-2-implicit
real0m43.592s
real0m24.494s
Thanks, Richard!
So for "medium" projects in terms of depth of the dependency tree, it's
sensible to use transitive dependenci
I already use the second variant.
The maximum that I export this:
Export {
Depends { name: "cpp" }
cpp.includePaths: product.exportIncludePaths
}
But to connect files, I use wildcard mask almost everywhere. In topic
"Improving qbs resolve performance"
(https://lists.qt-p
Jochen,
>> Well [the time] goes into "Handling Products". So it is
>> ModuleLoader::handleProduct().
>> And there, it could be the ModuleMerger. But speculation is dangerous when
>> discussing about performance.
> See https://lists.qt-project.org/pipermail/qbs/2019-August/002546.html
>
> You ca
My analysis back then was:
> Well [the time] goes into "Handling Products". So it is
> ModuleLoader::handleProduct().
> And there, it could be the ModuleMerger. But speculation is dangerous when
> discussing about performance.
See https://lists.qt-project.org/pipermail/qbs/2019-August/002546.htm
> I would like to know if any measures are being planned to
> increase the speed of re-parsing a project? I am using QtCreator 4.11.2
> (QBS 1.15.1)
Some ideas:
1. Incremental project resolving: Take the dependency graph into account
when re-resolving a project so that unchanged products are not
> We faced similar problems but our resolve times were even higher (30 s to
> 2 mins).
>
> We were able to work around this and significantly reduce the resolve
> times by avoiding transitive dependencies (meaning exporting
> dependencies).
I would like to understand why exactly this pattern mak
We faced similar problems but our resolve times were even higher (30 s to 2
mins).
We were able to work around this and significantly reduce the resolve times by
avoiding transitive dependencies (meaning exporting dependencies).
So instead of this:
>>>
Product {