Re: [Qbs] Future of Qbs

On Wed, 2018-10-31 at 20:45 +1300, Christian Gagneraud wrote: > > > > Qbs is open source but the largest part of development has always > > been > > shouldered by The Qt Company and the decision processes have never > > been open > > and transparent. > > It looks to me a bit early to make some

Re: [Qbs] QBS usage

Hi Tino, On Sat, 2018-06-16 at 03:58 +, Tino Pyssysalo wrote: > I’m Tino Pyssysalo, the new product owner of QBS at the Qt Company. Congrats on your new role! > I’d like to conduct a small survey about QBS usage in the community > to make investment and feature decisions to the product.

Re: [Qbs] qbs, qmake and filename case sensitivity

Hi Chris, > I am not sure what is the best behaviour: > - QMake being convenient. > - Qbs being strict. > > Should Qbs mimic what qmake does? I would suggest something in between: be convenient like qmake, but generate a warning when the filename doesn't exactly match. Alternatively, maybe add

[Qbs] Layout of qbs cpp documentation

Hi, I've recently visited the docs at http://doc.qt.io/qbs/cpp-module.html It looks like this: https://imgur.com/a/SwIm6 Is this the intended look-and-feel of the docs? I think it is currently very hard to read with all the property descriptions squeezed in that table and hidden with a scroll

Re: [Qbs] Passing unescaped flags to the linker

Hi, > I use the latest versions (Qt Creator 4.4.1 and QBS 1.9.1) available on > Windows. > I just configured a Kit with my ARM toolchain, created a minimal qbs > project that compile > and run the static analyzer. What I did was to set up scan-build as a compiler wrapper in my qbs file, so

Re: [Qbs] Passing unescaped flags to the linker

@Christian: >> Yes, that is a bit of a problem. We really need cpp.linkerDriverFlags with >> the semantics "flags to pass only when linking using the compiler binary". >> The need for that has been debated in the past, but I think the case is >> pretty clear now. Could you please create a task

[Qbs] Using clang-tidy with Qbs

Hi, I've found this bugreport: https://bugreports.qt.io/browse/QBS-997 However it's unclear to me whether this actually made it into Qbs yet. What's the right way to use clang-tidy with my Qbs-based project? Thanks, Timur ___ Qbs mailing list

Re: [Qbs] Linker Flags auto escaping troubles

Hi Benjamin, The solution is described here: http://lists.qt-project.org/pipermail/qbs/2017-May/001735.html Short answer: try driverFlags instead of linkerFlags. This question comes up quite often, it might be worth to put it into a FAQ or something. Hope this helps, Timur On Tue, 2017-07-04

Re: [Qbs] Qbs: how to use a pre-build script

>    "GIT_TAG=" + "\"" + gitProbe.tag + "\"", >    "GIT_COMMIT_DATE=" + "\"" + > gitProbe.commitdate + "\"", >   ]) > > return result > } > &

[Qbs] Qbs: how to use a pre-build script

Hi, What is the correct way to execute a pre-build script with Qbs whose output is a dependency to the product being built? For example, I have a script that generates a C++ header file containing the current git revision and the date of the build. This header is then included into one of the

Re: [Qbs] Concatenating include paths with Qbs

Hi Christian, Thanks for your answer! > A product's properties are "private" in that they are not accessible > from other products. You add module properties such as > cpp.includePaths to depending products using an Export item: > > Product { > name: "ex" > // ... > Export { >   

[Qbs] Concatenating include paths with Qbs

Hi, I have a Qbs project that contains a static library and an executable that depends on the static library. The static library has some features which can be enabled or disabled through a couple of bool properties. It has a "myIncludes" property which contains the pathList of the include paths