Re: [Qbs] Heads up: New project resolving implementation

That is great news, thank you! Best regards, Ola tor. 20. apr. 2023 kl. 10:18 skrev Christian Kandeler via Qbs < qbs@qt-project.org>: > Hi, > > > we have just merged > > https://codereview.qt-project.org/c/qbs/qbs/+/459764 into the master > branch, which improves speed and correctness when load

Re: [Qbs] Issues building for Android

tor. 15. okt. 2020 kl. 12:17 skrev Raphael Cotty : > Hi, > About the use of QtApplication instead of CppApplication in the wizard: > I don't think it's a QtCreator issue. It's a qbs regression actually. > The QtApplication.qbs not only adds a Depends on Qt.Core but it also > changes the targetName

Re: [Qbs] Issues building for Android

ons. 14. okt. 2020 kl. 21:03 skrev Raphael Cotty : > Hi, > Just tried the Qt Quick wizard. If you change the CppApplication into > QtGuiApplication then it works (instead of QtApplication). > > Thanks again everyone. So, my previous build error was eliminated by wiping the build directory complete

Re: [Qbs] Issues building for Android

ons. 14. okt. 2020 kl. 19:55 skrev Richard Weickelt : > Qt Creator is not part of the tests. We run everything with Qbs only on the > command line in a Docker image. > > Thanks!! Some progress now: first, if I set these two additional properties in the Qbs-part of the kit, I get further building

Re: [Qbs] Issues building for Android

man. 12. okt. 2020 kl. 20:34 skrev Raphael Cotty : > Hi, > Looks like your android profile is not correct. > Agreed. (It was set up automatically by QtCreator). > What do you have for the sdkDir/ndkDir keys? > Are they pointing to the android sdk/ndk? > Android.sdk.sdkDir: /home//Android/Sdk A

Re: [Qbs] Issues building for Android

man. 12. okt. 2020 kl. 16:45 skrev Christian Kandeler < christian.kande...@qt.io>: > Do you have qbs.architectures set in your project? You could try setting > it to some permutations of the supported set (as printed by the quoted Qt > detection code), and see whether they all fail or just e.g. th

Re: [Qbs] Issues building for Android

man. 12. okt. 2020 kl. 15:49 skrev Christian Kandeler < christian.kande...@qt.io>: > Looks like Android.sdk.buildToolsVersion is empty. Please verify. However, > I think this should have resulted in an error message from the respective > Probe. Are you sure your project loaded without warnings? Wh

Re: [Qbs] Issues building for Android

man. 12. okt. 2020 kl. 15:49 skrev Christian Kandeler < christian.kande...@qt.io>: > On Mon, 12 Oct 2020 15:07:14 +0200 > Ola Røer Thorsen wrote: > > > The process '/Android/Sdk/build-tools/aidl' could not be started: > > execve: No s

[Qbs] Issues building for Android

Hi, anyone know the status of building Qt apps for Android using Qbs now? I've successfully done this before, but now I can't get it to work. I've got QtCreator 4.13.2 installed, and have set up everything regarding the Android SDK/NDK from within QtCreator. Everything should be Ok (QtCreator says

Re: [Qbs] QtC 4.10.1 missed QBS 1.14.1!!

ons. 9. okt. 2019 kl. 09:20 skrev Christian Kandeler < christian.kande...@qt.io>: > What is all this talk about 1.14.1? 1.14.0 has not even been released yet. > We expect it shortly. > > FYI it became somewhat important because of this issue here, https://bugreports.qt.io/browse/QBS-1492 Ola

Re: [Qbs] QtC 4.10.1 missed QBS 1.14.1!!

ons. 9. okt. 2019 kl. 09:20 skrev Christian Kandeler < christian.kande...@qt.io>: > > What is all this talk about 1.14.1? 1.14.0 has not even been released yet. > We expect it shortly. > > It was shipped with Qt Creator 4.10.0 and now 4.10.1, it appears to me that it just has used whatever was at

Re: [Qbs] QtC 4.10.1 missed QBS 1.14.1!!

ons. 9. okt. 2019 kl. 09:20 skrev Christian Kandeler < christian.kande...@qt.io>: > On Tue, 8 Oct 2019 22:38:49 +0300 > Denis Shienkov wrote: > > > Seems, you are forgot to deliver QBS 1.14.1 with QtC 4.10.1. Right now I > > see that it use QBS 1.14.0. > > What is all this talk about 1.14.1? 1.14

Re: [Qbs] QtC 4.10.1 missed QBS 1.14.1!!

It looks like at least some fixes were included, as I'm able to build with Qt 5.13.1 now (which was impossible with Qt Creator 4.10.0). But I've got no idea exactly which commits were included either. Maybe it's just the version bump commit that is missing? Ola tir. 8. okt. 2019 kl. 21:39 skrev

[Qbs] Qbs with Qt 5.13.1 broken

Hi all Qbs users, just FYI, it's currently not possible to use Qbs to build Qt applications with the just recently released Qt 5.13.1. I made a bug report (where the reason has been found already, see comments) https://bugreports.qt.io/browse/QBS-1492 Best regards, Ola ___

Re: [Qbs] Who compared build times of Qt Creator with CMake and qbs?

tir. 14. mai 2019 kl. 10:12 skrev Vincent Hui : > We can see Qbs development is active. > https://github.com/qbs/qbs/commits/master?before=ca4987ae21f3cb30fde699448abc213b37b90214+35 > Therefore I don't think it is dead. > > Sure I agree, however if the mindset elsewhere is that "Qbs is dead", the

Re: [Qbs] Who compared build times of Qt Creator with CMake and qbs?

tir. 14. mai 2019 kl. 09:45 skrev Vincent Hui : > Hi, > > Qt Creator was ported to CMake > . It is interesting to > compare build times of Qt Creator with CMake and Qbs. > > Did anyone benchmark qbs against cmake? > > I'd like to know if Qt Creator wi

[Qbs] Some dependency scanning/tracking-questions

I'm trying to replace a large scons-based build system with Qbs, mainly to try to improve incremental build times. So far it's looking very promising. We're curious about how Qbs deals with a couple of things, to be sure before we might decide to leave scons behind for good. - How does Qbs keep tr

[Qbs] How to use ">" as argument to cat in the Command item

I'm writing a Rule where one of the commands is using cat like this: cat file1 file2 file3 > finalfile My qbs code does this: var cmd = new Command("cat", ["file1","file2","file3",">","finalfile"]); The command line being used wraps > like '>', which doesn't work: cat file1 file2 file3 '>' fin

Re: [Qbs] Can't find variable when using custom property

> Custom properties are collected and made accessible in rules for the > Product, Project and Modules items. > For all other items, only the built-in properties are retrieved and acted > upon according to their documented semantics. > > Right. What's the reasoning why custom properties aren't gener

[Qbs] Can't find variable when using custom property

I'm trying to do something like this: import qbs Rule { property var myProperty: "test" ... outputArtifacts: { console.warn(myProperty); } } qbs can't find "myProperty" in the line trying to print it, saying ReferenceError: Can't find variable: myProperty I've tried sett

Re: [Qbs] How to pass -march=armv7-a to the g++ linking command line (without -Wl, )

Hi all, thanks for the replies guys. Yes the cpp.driverFlags option did the trick, I don't know why I didn't see it although "driver" is not the first that came to my mind while searching. And sorry about the misleading email title, my head must have been elsewhere. The toolchain I'm using is wha

[Qbs] How to pass -march=armv7-a to the g++ linking command line (without -Wl, )

I've got a product running on Linux arm imx6. It's being cross-compiled on Linux x86_64. I've got it set up with both qmake and now qbs that hopefully should replace qmake at some point. The binary created by qbs fails to run as it's set up to use the wrong interpreter. I need to pass "-mfloat-abi

Re: [Qbs] "qbs setup-qt" and Qt built for cross-compilation

Hi, thanks for the reply. 2018-01-04 12:00 GMT+01:00 Christian Kandeler : > > > When using cross-compilation, the host tools such as qmake are separated > > from the installed Qt headers and libraries that are installed into the > > target device's sysroot. > > > > /hostqt contains the host tools

[Qbs] "qbs setup-qt" and Qt built for cross-compilation

I'm building an application on a linux host computer for a target imx6-based device. I built the Qt version myself configured for cross-compilation. So far I've only used qbs via QtCreator and the kits configured there, and this works fine. When using cross-compilation, the host tools such as qmak

Re: [Qbs] How do I tell qbs to use the nasm assembler when building using QtCreator and a Qt kit?

> > > > Group { > > name: "asm-linux-x86_64" > > condition: qbs.architecture === "x86_64" > > files: [ ...the .asm files ] > > cpp.assemblerName: "nasm" > > } > > That's due to an implementation detail in the cpp module: The assembler > path is read from the product-global instance,

Re: [Qbs] How do I tell qbs to use the nasm assembler when building using QtCreator and a Qt kit?

2017-12-14 18:02 GMT+01:00 Christian Kandeler : > On Thu, 14 Dec 2017 17:46:56 +0100 > Ola Røer Thorsen wrote: > > > It's running when I tag the files with "asm", but using the assembler > "as" > > instead of "nasm". Any way to overr

Re: [Qbs] How do I tell qbs to use the nasm assembler when building using QtCreator and a Qt kit?

2017-12-14 17:27 GMT+01:00 Christian Kandeler : > Have you tagged them properly? The .asm extension is not auto-tagged on > Linux; you will need to do that "manually" via a Group or a FileTagger > item. > See https://doc.qt.io/qbs/cpp-module.html#relevant-file-tags for the > assembler-related fil

[Qbs] How do I tell qbs to use the nasm assembler when building using QtCreator and a Qt kit?

I'm trying to build a project that has some assembly files as well as C++ code. I'm building from QtCreator using the latest Qt 5.10 release kit (Linux x86_64) on KDE Neon. The assembly files are added to the files property along with the rest, and end with .asm. While building qbs seems to just i

Re: [Qbs] Need help with setting up a code generator

2017-12-13 17:36 GMT+01:00 Christian Kandeler : > > That happens automatically if the product has a dependency on the Qt.core > module. > Note: The correct file tag for headers is "hpp" (not "h", as I wrote in my > first reply.) > > Yes using "hpp" fixed it, thanks :-)

Re: [Qbs] Need help with setting up a code generator

Now I've got a new problem related to the code generated library. I've set up a second version of the library (new templates, basically), where the code generated is using Qt. So there are a few QObject-based classes etc. My Rule item that produces the files are setting the fileTags "h" for the he

Re: [Qbs] Need help with setting up a code generator

grating from qmake to qbs completely. The QtCreator integration seems to be much more stable now with the latest release as well. Best regards, Ola 2017-12-12 14:29 GMT+01:00 Christian Kandeler : > On Tue, 12 Dec 2017 14:20:01 +0100 > Ola Røer Thorsen wrote: > > > To run the c

Re: [Qbs] Need help with setting up a code generator

> > > > Does this mean I need to know the exact list of files the code generator > > outputs before it is run? Normally I'd only know that after having run > the > > code generator and look into it's output directory. > > Then you'll have to run the tool in the outputArtifacts script already. > Unl

Re: [Qbs] Need help with setting up a code generator

Thanks a lot for the help, Christian! 2017-12-11 13:27 GMT+01:00 Christian Kandeler : > Group { > name: "header inputs" > files: ["dir1/*.h"] > fileTags: ["generator.in.headers"] > } > Group { > name: "template inputs" > prefix: "dir2/" >

[Qbs] Need help with setting up a code generator

Hi all, I've got a code generator tool that I'm trying to include in a qbs project. Currently it's been used in a project using qmake, but I'd like to move on to qbs. The code generator (a commandline tool) takes a set of C header files (.h) in a given directory, and another set of template files

Re: [Qbs] How do I build using GCC with the "-march=native" option?

2017-12-08 11:17 GMT+01:00 Christian Kandeler : > > I believe qbs is being overly strict here. There seem to be legitimate > use cases for -march not covered by dedicated properties. See also > https://bugreports.qt.io/browse/QBS-1018. > > Ah, I missed that bugreport. Yes I'd agree it's being too

[Qbs] How do I build using GCC with the "-march=native" option?

differs from the architecture produced by this compiler (x86_64)" How do I fix this? The -mtune option works but it's not quite what I'm after here. Best regards, Ola Røer Thorsen ___ Qbs mailing list Qbs@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs

Re: [Qbs] How to set GCC optimization -O3 in releasebuilds?

2017-12-01 10:03 GMT+01:00 Christian Kandeler : > > In this case, do not set cpp.optimization and use cpp.cxxFlags directly. > We've decided against allowing more values for cpp.optimization because of > the difficulties to abstract away the differences between the platforms > (see https://coderev

[Qbs] How to set GCC optimization -O3 in releasebuilds?

) at some point. Is it best to create my own "CustomStaticLibrary" and "CustomApplication"-items and make sure to use those everywhere instead of the regular ones provided with Qbs? Best regards, Ola Røer Thorsen ___ Qbs mailing list Qbs@

Re: [Qbs] Detecting changes in files inside .qrc-files automatically?

I've updated the bug with my findings so far ( https://bugreports.qt.io/browse/QBS-697). I think this issue should be re-opened, it looks like some rather subtle bug. Best regards, Ola > Best regards, > Lars Ivar Igesund > > On Thu, Oct 26, 2017 at 8:36 PM Ola Røer T

Re: [Qbs] Detecting changes in files inside .qrc-files automatically?

2017-10-26 20:31 GMT+02:00 Jake Petroules : > This is supposed to work, but there may be a bug in the qrc scanner > (QBS-697). > > Can you update that issue with an exact set of steps to reproduce the > issue? We tried to reproduce it before but could not. > > Sure. I'll see if I can isolate the i

[Qbs] Detecting changes in files inside .qrc-files automatically?

Hi, I'm trying out qbs by building an existing Qt Quick-application normally being built with qmake. I've got my qml files in a qml.qrc file, and have included this qrc file in the files list in my qbs file. Everything builds fine from scratch. However it does not seem like qbs is able to detect