On 5/7/22 10:33, Jochen Becher wrote:
Am Mittwoch, dem 22.09.2021 um 10:45 +0200 schrieb Christian Kandeler:
On 9/9/21 1:25 PM, Jochen Becher wrote:
thank you for the prompt answer. Adding explicit dependency on
"installable" works. But adding the input dependency on application
does not:
The
Am Mittwoch, dem 22.09.2021 um 10:45 +0200 schrieb Christian Kandeler:
> On 9/9/21 1:25 PM, Jochen Becher wrote:
> > thank you for the prompt answer. Adding explicit dependency on
> > "installable" works. But adding the input dependency on application
> > does not:
> >
> > The rule uses
> >
> >
On 9/9/21 1:25 PM, Jochen Becher wrote:
thank you for the prompt answer. Adding explicit dependency on
"installable" works. But adding the input dependency on application
does not:
The rule uses
inputs: [ "alang"]
to depend on the alang source code files. When I add additionally
Hi Richard,
thank you for the prompt answer. Adding explicit dependency on
"installable" works. But adding the input dependency on application
does not:
The rule uses
inputs: [ "alang"]
to depend on the alang source code files. When I add additionally
inputsFromDependencies: [ "application" ]
> Any idea how I can force the rule to depend on the binary in install-
> root/bin?
I think it's cleaner to follow
https://code.qt.io/cgit/qbs/qbs.git/tree/examples/code-generator and use the
transpiler binary in the build directory. That is what your rule really
depends on
Hi,
I develop a transpiler for some language into C. The qbs project
contains products to build the compiler, the runtime and unit tests
that are executed with every build.
To compile the unit test source code with the new compiler I use the
following rule. Unfortunately, when I change something
