OK, understood.
Thank you!
18.12.2017 14:15, Christian Kandeler пишет:
On Mon, 18 Dec 2017 14:04:21 +0300
Карелин Павел wrote:
In my project, I use the following construction:
cpp.defines: {
var def = [];
if (project.simdDebug)
def.push("SIMD_DEBUG");
On Mon, 18 Dec 2017 14:04:21 +0300
Карелин Павел wrote:
> In my project, I use the following construction:
>
> cpp.defines: {
> var def = [];
> if (project.simdDebug)
> def.push("SIMD_DEBUG");
>
> if (project.useSimd)
> def.push("USE_SIM
Hi,
In my project, I use the following construction:
cpp.defines: {
var def = [];
if (project.simdDebug)
def.push("SIMD_DEBUG");
if (project.useSimd)
def.push("USE_SIMD");
return def;
}
It works fine.
But I decided to experiment
Could a warning be emitted on value overwrites though?
Christian raises a very valid point of these errors being kinda difficult
to trace.
Obviously there will need to be a way to say to qbs that this write is
valid to silence the warning though.
On Mon, Dec 18, 2017 at 1:21 PM, Christian Kandeler
On Sun, 17 Dec 2017 08:53:42 +1300
Christian Gagneraud wrote:
> Could someone explain the rules as to when to use base.concat or not, eg is
> it necessary here just because of the group? Or should this be always used?
> (Project, Product, Module, ...)
You use "base" if and only if there is a bas
> VSCode is actually one of the reasons why I brought up a qbs "server mode"
> that would just use REST APIs for IDE integration (including solving the
> compatibility issue for Qt Creator).
I would love to see something like this :)
> > On Dec 15, 2017, at 5:33 AM, Heiko Nardmann <
> heiko.nar
