Copying directories is not a good idea because it can introduce undefined
behavior to the build process, since the build system itself does not know
which files were copied.
Perhaps if you explain your use case in a wider context we can better
understand the issue you're trying to solve.
> On
On Fri, 16 Jun 2017 13:29:06 +0200
Christian Gudrian wrote:
> Thanks for the quick reply. I've added the "inputsFromDependencies"
> property, but there's still a race condition: the rule gets executed
> though the final code generator executable has not yet been created.
> Only the intermediat
Hello!
Thanks for the quick reply. I've added the "inputsFromDependencies"
property, but there's still a race condition: the rule gets executed
though the final code generator executable has not yet been created.
Only the intermediate version (intermediate.CodeGenerator.exe) is
present. Is th
On Fri, 16 Jun 2017 09:14:30 +0200
Christian Gudrian wrote:
> We're using a Module to define a code generation rule. This module
> however depends on a code generation tool which itself is part of the
> project.
>
> With Qbs 1.8.1 we're facing a race condition: Qbs executes the code
> generat
Hi,
Thank you both for your answer, so if i want to copy every item from the
bundle, i have to check every file name and rebuild bundle directory
from scratch ? Old solution was better since i only had to copy the app
directory like this : File.copy(inputs.bundle[0]...) but anyway it's
worki
Hello!
We're using a Module to define a code generation rule. This module
however depends on a code generation tool which itself is part of the
project.
With Qbs 1.8.1 we're facing a race condition: Qbs executes the code
generation step before the generator has been built. Both the generator
