On 05/22/2014 06:07 PM, Tim Hutt wrote:
Product {
property string foo: baz
Rule {
prepare: {
var a = product.foo;
Sure it does. We use that all the time. Try again ;)
Here is a full example that I just tested:
$ cat project.qbs
import qbs
Product {
type:
On 22-May-14 23:47, olivier musse wrote:
It looks like I found myself the solution :
Only need to QDESIGNER_EXPORT_WIDGETS to cpp.defines.
Yes, that's the only thing that's done in qmake's designer_defines.prf.
Not sure whether a dedicated property for designer plugins is justified.
BR,
Ah it seems to work now, weird. I may have typo'd project instead of
product. Also, good news! I have found a reliable way to trigger the
qbs-isn't-updated bug:
1. Create a new C++ QBS project in QtCreator.
2. Rename main.cpp to foo.txt
3. Paste this in the QBS file:
import qbs
Product {
type:
On 22-May-14 16:14, Christian Kandeler wrote:
On 05/22/2014 04:00 PM, Tim Hutt wrote:
Relatedly, how can I access properties from a Rule's prepare script?
E.g. this does not work - it thinks foo is not defined.
Rule {
property string foo: baz
Hi all,
E.g. I want to use the WiX module. But this module by default works only in
build step. I.e. works when I try to build my Products from the Project.
But I want to run my WiX product separately, e.g. in deploy step..
The WiX module it is just as example.
A main question is:
it is
I agree, no need for specific config, but perhaps simply add information
to the Qbs quick reference page in the same section as CONFIG+=console
http://qt-project.org/wiki/Qbs-Quick-Reference
BR
Olivier
On 22-May-14 23:47, olivier musse wrote:
It looks like I found myself the solution :
Only
Am Donnerstag, den 22.05.2014
schrieb Christian Kandeler christian.kande...@digia.com:
On 05/22/2014 05:04 PM, Kurt Keller wrote:
Is this a self-compiled Creator or did you download it in binary form?
This is a self-compiled Creator.
In that case it's much simpler. Just do a make
On 05/23/2014 11:44 AM, Kurt Keller wrote:
Am Donnerstag, den 22.05.2014
schrieb Christian Kandeler christian.kande...@digia.com:
On 05/22/2014 05:04 PM, Kurt Keller wrote:
Is this a self-compiled Creator or did you download it in binary form?
This is a self-compiled Creator.
In that case
On 23-May-14 11:38, Denis Shienkov wrote:
A main question is:
it is possible to do something that my Products (Rules of module) was
launched only in appropriate steps?
or, it is possible to introduce an custom additional steps (not only
Build, Install, Deploy) ?
Not yet. But soon (QBS-262).
Hi,
we have just released qbs 1.2.1, which fixes a number of bugs uncovered
after the release of 1.2.0. As usual, source packages and a binary
package for Windows can be downloaded from
http://download.qt-project.org/official_releases/qbs/1.2.1.
Christian
Hi,
Once again an issue while trying to get properties in a Rule, I found
the following is not working and ask myself if it is a bug or not.
This should really nice if it works then enabling to add to any product
a set of properties and use them in associated rules.
See my example below
On 05/23/2014 01:53 PM, olivier musse wrote:
Once again an issue while trying to get properties in a Rule, I found
the following is not working and ask myself if it is a bug or not.
This should really nice if it works then enabling to add to any product
a set of properties and use them in
On 05/23/2014 11:50 AM, Kurt Keller wrote:
I have a linux server with multiple users. All users want to use the same
qbs profile. (They all use the same Qt Versions, the same Qt Creator, the
same environment, the same compilers.)
How can I set up a single profile for all users? (They want
Clear, thanks.
2014-05-23 15:08 GMT+04:00 Joerg Bornemann joerg.bornem...@digia.com:
On 23-May-14 11:38, Denis Shienkov wrote:
A main question is:
it is possible to do something that my Products (Rules of module) was
launched only in appropriate steps?
or, it is possible to introduce
On 05/23/2014 11:05 AM, Tim Hutt wrote:
I have found a reliable way to trigger the
qbs-isn't-updated bug:
1. Create a new C++ QBS project in QtCreator.
2. Rename main.cpp to foo.txt
3. Paste this in the QBS file:
import qbs
Product {
type: foo
Group {
files: foo.txt
fileTags:
Am Freitag, den 23.05.2014
schrieb Christian Kandeler christian.kande...@digia.com:
On 05/23/2014 11:44 AM, Kurt Keller wrote:
Am Donnerstag, den 22.05.2014
schrieb Christian Kandeler christian.kande...@digia.com:
On 05/22/2014 05:04 PM, Kurt Keller wrote:
Is this a self-compiled
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
17 matches
Mail list logo
