[Qbs] Some dependency scanning/tracking-questions
Ola Røer Thorsen
ola at silentwings.no
Wed Feb 7 12:34:47 CET 2018
I'm trying to replace a large scons-based build system with Qbs, mainly to
try to improve incremental build times. So far it's looking very promising.
We're curious about how Qbs deals with a couple of things, to be sure
before we might decide to leave scons behind for good.
- How does Qbs keep track of depedencies, like when including c-headers
that include other c-headers etc.?
- Is the compiler used for the scanning of dependencies, or does Qbs scan
- Is the file timestamps used to check for modified files, or a checksum of
- Will/could Qbs be able to scan dependencies in ld linker scripts? We've
got several of those where there are .ld files with "INCLUDE
xxxxx.ldscript" inside, and it's important that binaries are linked again
if any of those are modified. If Qbs can't scan these itself, is it
possible to somehow list those files so that the linking can be done again
if any of them are modified?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Qbs