but not the one I use for actual
development.
> -Original Message-
> From: QBS [mailto:qbs-bounces+johannes.matokic=microchip.com@qt-
> project.org] On Behalf Of Christian Kandeler
> Sent: Mittwoch, 6. Juli 2016 15:33
> To: qbs@qt-project.org
> Subject: Re: [QBS] Support for
Hi,
we have rules which generate additional wxs-artifacts for application-products.
Those wxs-files are fragments containing a component with all relevant
information for installing the application.
However I have problems using them with the qbs-wix module. The rules of this
module has wxs
Not sure if this is really your problem but I suspect that heat.exe expects the
value of parameters to be in different arguments:
var args = [];
args.push(dir, .);
args.push(-cg, MyProjectFiles);
args.push(-gg);
args.push(-scom);
So it looks like I either have to stay with QBS 1.2, live with often
broken compilation or have to work around a bad output path (Rename
files, change other rules/tools that rely on the path, etc).
Are there any other options?
I don't understand the last paragraph at all, particularly
Hi,
I attached a small project with instructions how to reproduce the Conflicting
rules for producing artifact-bug (491) with instructions.
At least on my system I can reproduce it with Qt Creator 3.1.0.
Johannes
___
QBS mailing list
Hello,
I have a generic preprocessing tool that I use almost everywhere for different
purposes.
This preprocessing tool generates the real files that are used in my products.
Now in some products there are files that require different module-properties.
Let's assume I want to set
