Hi Christian, thanks a lot for all your input. The build is very efficient now. The final solution was a partial "dry run" of the generator tool to help create the list of artifacts, and the usual full run in the "prepare" script.
Now that this is working we'll start migrating from qmake to qbs completely. The QtCreator integration seems to be much more stable now with the latest release as well. Best regards, Ola 2017-12-12 14:29 GMT+01:00 Christian Kandeler <[email protected]>: > On Tue, 12 Dec 2017 14:20:01 +0100 > Ola Røer Thorsen <[email protected]> wrote: > > > To run the command inside the outputArtifacts script, I'll use the > Process > > object, right? > > Yes. > > > What is the exact condition for when this script is run? Is it only > > whenever any of the inputs are modified (or the qbs file I guess)? > > Whenever any input has a timestamp newer than any output, or if a property > accessed in the rule has changed its value since the last run, or if the > rule source code has changed. > Modifications to the qbs file only cause rule re-execution if there are > relevant changes as described above. > > > What's the simplest way to define a dummy command in the prepare-script? > > var cmd = new JavaScriptCommand(); > cmd.silent = true; // Or cmd.description = "<your choice>"; > cmd.sourceCode = function() {} > > > Christian > _______________________________________________ > Qbs mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qbs >
_______________________________________________ Qbs mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qbs
