Re: [Qbs] Set cpp properties for generated cpp files (moc) does not seem to work

On Thu, 14 May 2020 14:49:25 + Maximilian Hrabowski wrote: > Isn’t unmocable used to tag cpp/header files that should not be processed by > moc? Sure, that's why the generated cpp files get it, so they won't get processed again. Christian ___ Q

Re: [Qbs] Set cpp properties for generated cpp files (moc) does not seem to work

On Thu, 14 May 2020 12:22:53 + Maximilian Hrabowski wrote: > we have quite a strict warning policy so all warnings are treated as errors > in our code. This creates problems when including third-party code that > produces warnings, so usually those files are put in a special group and > wa

Re: [Qbs] Undocumented SubProject.condition property

On Thu, 16 Apr 2020 11:57:08 + Jochen Ulrich wrote: > We found that there is an undocumented `condition` property on SubProject > items. > It seems to have the same effect as setting the `condition` property inside > the Properties block. > However, I find it more readable to have the condi

Re: [Qbs] building android aab package help

[Redirecting back to the mailing list] On Thu, 16 Apr 2020 20:17:47 +0200 Raphael Cotty wrote: > Le mer. 15 avr. 2020 à 09:48, Christian Kandeler > a écrit : > > > Building an aab is similar to building apk. They both take the same inputs > > > (including java files)

Re: [Qbs] building android aab package help

On Tue, 14 Apr 2020 21:27:18 +0200 Raphael Cotty wrote: > I am struggling to find a way to build the aab package (non runnable > package required by google store) on the android platform. > For this platform the default qbs product type is changed from application > to android.apk (runnable packa

Re: [Qbs] Binary stripping

On Thu, 9 Apr 2020 22:49:48 +0300 Alberto Mardegan wrote: > I noticed that binaries generated by mingw are quite large, and when I > ran the "strip" command on them, the size was reduced by more than half, > without losing functionality. > > I'm building my application with the `config:release`

Re: [Qbs] Building code generator and its dependencies for a different architecture than the rest of the products

> I think you should write: > CppApplication { >name: "app" >files: ["gen.cpp"] >Depends { name: "lib"; profiles: "targetProfile" } > } Ah right, I completely forgot about that property... ___ Qbs mailing list Qbs@qt-project.org https://lists

Re: [Qbs] Building code generator and its dependencies for a different architecture than the rest of the products

On Fri, 20 Mar 2020 16:01:09 + Leon Buckel wrote: > I think I almost got it to work. The problem I have now is that the app seems > to link against the wrong version of the library: > ld: warning: ignoring file > /.../lib.eyJwcm9maWxlIjoiaG9zdFByb2ZpbGUifQ--.cd69e9f1/.tmp/lib, building for

Re: [Qbs] Building code generator and its dependencies for a different architecture than the rest of the products

On Fri, 20 Mar 2020 15:41:21 +0100 Christian Kandeler wrote: > Your app and build tool use normal Depends items for pulling in the library; > the matching should work automatically. Addendum: Of course, you also need to set the host profile in your build tool: CppAppli

Re: [Qbs] Building code generator and its dependencies for a different architecture than the rest of the products

On Fri, 20 Mar 2020 14:10:49 + Leon Buckel wrote: > I have a project with the following products: > > * Shared library > * Code generator tool > * Application > > The code generator and application both depend on the shared library. The > build process is as follows: > > 1.

Re: [Qbs] qmath3d build issue

On Wed, 19 Feb 2020 12:18:13 + Wookey wrote: > I maintain a couple of debian packages that build with qbs. > > Last night, whilst fixing a couple of bugs in qmath3d > (https://tracker.debian.org/pkg/qmath3d) I found a problem: it used to build > but no longer does. > > Well it builds fine

Re: [Qbs] Construction project.buildDirectory

On Thu, 6 Feb 2020 16:08:42 +0100 Richard Weickelt wrote: > > sorry for breaking this. The issue has been fixed by > > https://codereview.qt-project.org/c/qbs/qbs/+/289271 and the fix will be in > > Qt Creator 4.11.1 which is about to be released this week. You may try > > http://download.qt.io/s

Re: [Qbs] Passing paths to properties

On Tue, 4 Feb 2020 21:40:24 +0300 Alberto Mardegan wrote: > I was happy to see that the FileInfo.resolvePath() already exists. :-) > It's not documented, however; is there any reason for that, or should we > add it to the reference? The missing documentation is probably unintended. Christian _

Re: [Qbs] Use of qbs.architecture with qtc

On Mon, 3 Feb 2020 18:09:57 +0100 Raphael Cotty wrote: > I was using it at the project level which was obviously wrong. > I managed to change all the occurrences of the test by moving them in the > condition of the different products. > > Except in this case: > Depends { > name: "Qt"; >

Re: [Qbs] Use of qbs.architecture with qtc

On Sun, 2 Feb 2020 11:57:20 +0100 Raphael Cotty wrote: > I see that the qbs.architecture property is set for the android platform by > the different qbs tools. > But it's not set by qbs-setup-qt or qbs-setup-toolchains for gcc. That's because the cpp module sets it automatically using informatio

Re: [Qbs] Passing paths to properties

On Sat, 1 Feb 2020 09:30:33 +0100 Richard Weickelt wrote: > > I believe that most other properies which accept a path (like installDir, > > and the prefix property within a Group) all happily accept a relative > > path, so can we consider this a bug in Android.sdk? > > You mean qbs.installDir? T

Re: [Qbs] Accessing qbs.architecture in Probe

On Thu, 30 Jan 2020 12:41:44 + Leon Buckel wrote: > > Though it will still work if you set the architecture via a profile. > How would I access a property set in a profile? I think I've tried it before > but I probably did something wrong. $ qbs config profiles..qbs.architecture x86 $ # ...

Re: [Qbs] Accessing qbs.architecture in Probe

On Thu, 30 Jan 2020 11:30:24 + Leon Buckel wrote: > Here's the probe. I is instantiated at project level where the value of > 'generatedQbsFilePath' is added to the 'references' property. That's generally a problem. Modules are per-product, and with very few exceptions (constants like qbs.

Re: [Qbs] Accessing qbs.architecture in Probe

On Thu, 30 Jan 2020 10:01:17 + Leon Buckel wrote: > I’m running conan from a probe to get all required dependencies for the build > and to be able to directly include the generated qbs file into the project. > For the windows build I need to know whether to request the package for 64 or > 3

Re: [Qbs] QBS behaviour while linking

On Tue, 28 Jan 2020 18:22:31 +0100 Heiko Nardmann wrote: > I wonder why parallel building stops when libraries are linked ... It does not. > Every time a library is linked (Linux) one core is busy and all others > are completely idle. Is this a known bug? Presumably the library to be built is

Re: [Qbs] Construction project.buildDirectory

On Thu, 19 Dec 2019 16:35:22 +0300 Карелин Павел wrote: > My colleague decided to try QtCreator 4.11 (QBS 1.15), and faced a problem. > At this project the QtCreator 4.11 issues a mistake: > > import qbs > Project { >     minimumQbsVersion: "1.12.0" > >     Probe { >     id: projectProbe

Re: [Qbs] (no subject)

On Thu, 28 Nov 2019 18:58:54 +0500 Dan Pat wrote: > Hello. I am trying to use Asan in my project (windows 10, clang-cl). > There's a requirement for the Asan import library to appear first in the > linker's list of import libraries. Who imposes that requirement and why? > I cannot seem to find

Re: [Qbs] Passing settings to qbs generators using the command line

On Tue, 19 Nov 2019 08:07:22 + Maximilian Hrabowski wrote: > Is there a way to pass settings to qbs generators using the command line? Not yet, because no one has needed it so far. This feature can be easily added, though: Just extend the GenerateCommand class to behave like RunCommand (usi

[Qbs] qbs 1.14.1 release

Hello, I'd like to announce the release of Qbs 1.14.1. This is a bugfix release. Source and binary packages as well as a change log can be found at https://download.qt.io/official_releases/qbs/1.14.1/. This release of Qbs is also shipped as part of Qt Creator 4.10.2. Christian _

[Qbs] qbs 1.14.0 released

Hello, I'd like to announce the release of Qbs 1.14.0. Source and binary packages as well as a change log can be found at https://download.qt.io/official_releases/qbs/1.14.0/. This release of Qbs is also shipped as part of Qt Creator 4.10.1. Note that this release is not compatible with Xcode 11.

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

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.0 has not even been released yet. We expect it shortly. Christian

Re: [Qbs] avoid RPATH pointing to Qt installation folder

On Tue, 8 Oct 2019 11:39:09 +0200 Heiko Nardmann wrote: > The question is whether to include Qt.core.libPath (as defined inside > core.qbs) into the list of rpaths. If I put it into the list then it > also is part of the binaries RPATH - which I want to avoid. I I leave it > out then I get ld err

Re: [Qbs] avoid RPATH pointing to Qt installation folder

On Tue, 8 Oct 2019 09:53:32 +0200 Heiko Nardmann wrote: > I'm looking for a way to prevent the RPATH of an executable pointing to > the installed Qt. From the "core.qbs" file I see that cpp.rpaths is set > to libPath for Linux by default. There should probably be a Qt.core property that controls

Re: [Qbs] Android deployment

This is a bug. If you can reproduce it, please create an issue at bugreports.qt.io. Make sure to add an example project that triggers the problem. Christian From: Qbs on behalf of Raphael Cotty Sent: Monday, September 9, 2019 11:20 PM To: qbs@qt-projec

Re: [Qbs] Use compiler flags file generated by a rule

On Thu, 29 Aug 2019 13:19:49 +0200 (CEST) "Richard Weickelt" wrote: > I want to integrate a generator tool into a Qbs build flow. This tool is very > slow and produces a bunch of .h/.c files and a "compiler.opt" file with some > compiler flags. I need to use these flags to build the current pro

Re: [Qbs] Generating a c++ class with Q_OBJECT

On Wed, 28 Aug 2019 12:56:56 +0200 Raphael Cotty wrote: > I've created a module: > Module { > FileTagger { > patterns: "*.wsdl" > fileTags: ["wsdl"] > } > Depends { name: "kdsoap" } > Rule { > multiplex: false > inputs: ["wsdl"] > Artifact {

Re: [Qbs] A simple project that copy an executable does not work

On Tue, 13 Aug 2019 11:50:38 + Christian Kandeler wrote: > On Mon, 12 Aug 2019 21:57:34 +0800 > Vincent Hui wrote: > > > Do you know why the document for Rule is not updated? > > https://doc-snapshots.qt.io/qbs/qml-qbslanguageitems-rule.html > > The snapshots ar

Re: [Qbs] A simple project that copy an executable does not work

On Mon, 12 Aug 2019 21:57:34 +0800 Vincent Hui wrote: > Do you know why the document for Rule is not updated? > https://doc-snapshots.qt.io/qbs/qml-qbslanguageitems-rule.html The snapshots are probably updated manually, or the script is broken. I'll ask a doc person. Christian ___

Re: [Qbs] Define the link order without an explicit dependency

On Fri, 9 Aug 2019 02:15:31 +0200 Richard Weickelt wrote: > I have the following scenario: > > Product { > name: "some-headers" > } > > // Implementations of some-headers > // A-1 and A-2 define the same symbols and are mutually exclusive. > // An application product

Re: [Qbs] Android: -target unknown option

On Thu, 1 Aug 2019 10:45:35 +0200 Christian Gudrian wrote: > I am trying to build a simple application for Android. Current setup: > > - Qt 5.13.0 > - Qt Creator 4.9.2 (Qbs 1.13.1) Qt Creator has traditionally supported only qmake for Android development. This will change with 4.10, to be rel

Re: [Qbs] Graphviz export/generator

On Sun, 21 Jul 2019 15:32:37 +1200 Christian Gagneraud wrote: > Hi there, > > I would like to be able to export a (graphviz) graph of a project and > i'm thinking about writing a new ProjectGenerator plugin for that. > The first kind of graph would be a product dependency graph. > > Once i have

Re: [Qbs] How to check whether a project is a subproject of another project?

On Wed, 17 Jul 2019 23:25:49 +0800 Vincent Hui wrote: > I want to check whether a project is a subproject of another project. If a > project is not a subproject, its examples and tests are built. If a project > is a subproject, its examples and tests are not built. Declare a property in your pro

Re: [Qbs] qbs resolve, multi-threaded or not?

On Thu, 18 Jul 2019 00:52:25 +1200 Christian Gagneraud wrote: > When I run qbs resolve (on a 8 cores machine), i can see 3 qbs > threads, and only 2 are busy (100% CPU). The resolve procedure is offloaded into a dedicated thread. Otherwise it would block the main application, which would be a p

Re: [Qbs] dump-nodes-tree broken?

On Thu, 18 Jul 2019 00:26:50 +1200 Christian Gagneraud wrote: > On Wed, 17 Jul 2019 at 23:52, Christian Kandeler > wrote: > > > > On Wed, 17 Jul 2019 23:41:54 +1200 > > Christian Gagneraud wrote: > > > > > I'm trying to use dump-nodes-tree with qb

Re: [Qbs] dump-nodes-tree broken?

On Wed, 17 Jul 2019 23:41:54 +1200 Christian Gagneraud wrote: > I'm trying to use dump-nodes-tree with qbs 1.13.1 (from QtC), and i > get nothing except a message 'Restoring build graph from disk'. > I've tried 'qbs dump-nodes-tree' and 'qbs dump-nodes-tree -p > qtcreator', still the same.. > Is

Re: [Qbs] Qbs (way) faster than cmake (or benchmark issue)

On Tue, 16 Jul 2019 18:29:35 +1200 Christian Gagneraud wrote: > I finally found time to start my qbs vs cmake build perf. > > What i found is that qbs beats cmake 'big time' on my build machine > and i was actually surprised, so surprised that i'm trying to find > where is the mistake. Precompi

Re: [Qbs] Improving qbs resolve performance

On Sat, 13 Jul 2019 17:37:04 +1200 Christian Gagneraud wrote: > On Sat, 13 Jul 2019 at 00:48, Christian Kandeler > wrote: > > > > On Fri, 12 Jul 2019 12:05:48 + > > Maximilian Hrabowski wrote: > > > > > >> I have a fairly large project with a

Re: [Qbs] Improving qbs resolve performance

On Fri, 12 Jul 2019 12:05:48 + Maximilian Hrabowski wrote: > >> I have a fairly large project with a root projects that pulls in several > >> SubProjects, altogether with unit tests its about 313 qbs files that are > >> pulled in. > > > > The number of project files is not all that impor

Re: [Qbs] Improving qbs resolve performance

On Thu, 11 Jul 2019 12:18:30 + Maximilian Hrabowski wrote: > I have a fairly large project with a root projects that pulls in several > SubProjects, altogether with unit tests its about 313 qbs files that are > pulled in. The number of project files is not all that important by itself. Qt

Re: [Qbs] How to reload a parent project after inserting a sub-project

On Mon, 8 Jul 2019 22:13:48 +1200 Christian Gagneraud wrote: > On Mon, 8 Jul 2019 at 22:09, Christian Kandeler > wrote: > > I don't know what you mean by "simulating a full project reload". Lots of > > tst_api test cases do project reloads. > > I just

Re: [Qbs] How to reload a parent project after inserting a sub-project

On Mon, 8 Jul 2019 21:22:13 +1200 Christian Gagneraud wrote: > On Mon, 8 Jul 2019 at 20:50, Christian Kandeler > wrote: > > > > On Mon, 8 Jul 2019 18:08:25 +1200 > > Christian Gagneraud wrote: > > > > > I'm back on https://codereview.qt-project.or

Re: [Qbs] How to reload a parent project after inserting a sub-project

On Mon, 8 Jul 2019 18:08:25 +1200 Christian Gagneraud wrote: > I'm back on https://codereview.qt-project.org/c/qbs/qbs/+/260217, i > decided that I should get that done and tested before I move on > QtCreator integration. > Conceptually, it works, i added a test that check that a sub-project > is

Re: [Qbs] Is there a feature similar with cmake option?

On Fri, 5 Jul 2019 16:06:28 +0200 Richard Weickelt wrote: > And it sounds like CMakeCache.txt is used to prevent from typing a CMake > command line with lots of -D. Is that correct? There is no direct > equivalent in Qbs. But note that the property values are stored in the build graph, so yo

Re: [Qbs] Is there a feature similar with cmake option?

On Fri, 5 Jul 2019 21:33:12 +0800 Vincent Hui wrote: > Cmake options can be overridden by CMakeCache.txt files inside build > folders. Is there similar feature in qbs? No, and it sounds like a horrible idea. Christian ___ Qbs mailing list Qbs@qt-proj

Re: [Qbs] Is there a feature similar with cmake option?

On Fri, 5 Jul 2019 16:01:02 +0800 Vincent Hui wrote: > In qbs, is there a feature similar with cmake option > ? Doesn't that just map to properties? Christian ___ Qbs mailing list Qbs@qt-project

Re: [Qbs] How to add -pthread option into projects? a bug in qbs ?

On Thu, 4 Jul 2019 14:20:09 +0800 Vincent Hui wrote: > cpp.cppFlags: ["-pthread"] cpp.driverFlags: "-pthread" Christian ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs

[Qbs] 1.14 branch created

Hi, we have branched off qbs 1.14 today. Scheduled release date for version 1.14.0 is end of July. We recommend users to try this branch with their projects and report back any new problems they find. Contributors are requested to push bug fixes and small, zero-risk improvements to this branch,

[Qbs] qbs 1.13.1 released

Hello, I'd like to announce the release of Qbs 1.13.1. This is a bugfix release. Source and binary packages as well as a change log can be found at https://download.qt.io/official_releases/qbs/1.13.1/. This release of Qbs is also shipped as part of Qt Creator 4.9.1. Christian __

Re: [Qbs] Install/Depends resolution changed from qbs 1.12.2 to qbs 1.13.0?

On Mon, 20 May 2019 09:01:02 +0200 Richard Weickelt wrote: > > Oh yeah, it has been an unsatisfying surprise that default installation > > prefix changed from empty string to "usr/local/" on Linux. All builds > > are broken, all scripts working on the results are broken. Not > > hardcoding is not

Re: [Qbs] Install/Depends resolution changed from qbs 1.12.2 to qbs 1.13.0?

On Thu, 16 May 2019 12:20:25 +0200 Frederik Christiani via Qbs wrote: > I ran into a similar problem and solved it by explicitly setting > qbs.installPrefix to an empty string. Though you should generally not hardcode such locations in a rule, but retrieve the path from the artifact. There is a

Re: [Qbs] Install/Depends resolution changed from qbs 1.12.2 to qbs 1.13.0?

On Thu, 16 May 2019 09:17:37 + Maximilian Hrabowski wrote: > after upgrading to qbs 1.13 our build was broken. > > During the build process a generator tool it built that depends on a > framework which is also build. The generator tool is later used to generate > code that will be compiled

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

On Wed, 15 May 2019 19:16:01 +0300 Orgad Shaneh wrote: > Probably because cmake aggregates files, while qbs builds each one > separately. One could verify: https://doc.qt.io/qbs/qml-qbsmodules-cpp.html#combineCxxSources-prop https://doc.qt.io/qbs/qml-qbsmodules-qt-core.html#combineMocOutput-prop

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

On Thu, 16 May 2019 02:01:21 +1200 Christian Gagneraud wrote: > As well, please note that the current CMake doesn't build as much > stuff as the qbs one. Not sure the difference is huge, but you need to > compare "equal jobs". For instance, all autotests are missing from the cmake build, so this

Re: [Qbs] Any novice tickets

On Tue, 30 Apr 2019 08:22:05 +0200 Иван Комиссаров wrote: > I want to add doc about how to run tests using QBS. But I can’t find Appendix > A page, surprisingly, it is not near Appendix B page. > Christian, can you please point to the correct page location? You mean in the sources? In the qbs.q

Re: [Qbs] qbs 1.13 released

On Tue, 23 Apr 2019 13:29:57 +0300 Иван Комиссаров wrote: > I’ve noticed, that cpp.minimumOsxVersion was renamed to > cpp.minimumMacosVersion at some point of time and QtCreator’s clang code > model does not understand this property. At least, it highlights std::visit() > call which requires c

[Qbs] qbs 1.13 released

https://blog.qt.io/blog/2019/04/18/qbs-1-13-released/ Christian ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs

Re: [Qbs] Qbs status update - looking for a maintainer

On Thu, 4 Apr 2019 22:29:59 +0200 Richard Weickelt wrote: > Christian, are you planning to step down as a maintainer in 2019 or will you > make that dependent on the amount of external contribution? Right now, the > amount of contribution doesn't look overwhelming. If no one takes over, I can co

Re: [Qbs] Any novice tickets

On Wed, 13 Feb 2019 15:26:00 +0100 Иван Комиссаров wrote: > I see that module providers feature was implemented. Is it now possible to > use a provider to create a module for auto-detected protobuf library (via > probes and via pkg-config)? Which problem are you trying to solve? Christian __

[Qbs] 1.13 branch created

Hi, we have branched off qbs 1.13 today. Scheduled release date for version 1.13.0 is beginning of April. We recommend users to try this branch with their projects and report back any new problems they find. Contributors are requested to push bug fixes and small, zero-risk improvements to this

Re: [Qbs] tst_blackbox-qt fails

On Wed, 30 Jan 2019 07:20:30 +0100 Richard Weickelt wrote: > >> This is how I build and test now: > >> > >> qbs build profile:qt > >> qbs run -p qbs_app profile:qt -- setup-toolchains --detect > >> qbs run -p qbs_app profile:qt -- setup-qt > >> /usr/local/Qt/5.9.7/gcc_64/bin/qmake qt > >> QBS_AUT

Re: [Qbs] lupdate/ts-file generation support in qbs

On Thu, 24 Jan 2019 07:08:03 + Maximilian Hrabowski wrote: > is there already some support in “Qt.core” to create ts files from cpp > sources using lupdate? I can only find lrelease/qm support in the doc. No, because lupdate was tied tightly to qmake project files. However, this has recent

Re: [Qbs] Qbs Rule for a tool like syncqt.pl

On Wed, 23 Jan 2019 14:32:03 +0100 Christian Gudrian wrote: > Usually the list of outputArtifacts is known beforehand or can be > derived from the inputs. What about scenarios where this is not the > case? Is it "allowed" to perform the actual transformation while > evaluating the outputArtifa

Re: [Qbs] Qbs Rule for a tool like syncqt.pl

On Tue, 22 Jan 2019 09:23:01 +0100 Christian Gudrian wrote: > Am 21.01.2019 um 11:55 schrieb Christian Kandeler: > > but technically, they aren't the "real" headers, since they are not > > what you include. > > That's true. They are however the head

Re: [Qbs] Qbs Rule for a tool like syncqt.pl

On Mon, 21 Jan 2019 08:45:30 +0100 Christian Gudrian wrote: > I'm struggling with writing a Rule for a tool like Qt's syncqt.pl script > which automatically generates a set of API headers from the source code > with the source itself already referencing these generated headers (that > basicall

Re: [Qbs] qbs command line help vs. documentation on qbs.io needs clarification

On Fri, 18 Jan 2019 15:40:04 + Maximilian Hrabowski wrote: > It seems > > > qbs config:release profile:xxx > > just works. but when i try to build both configurations > > > qbs config:debug config:release profile:xxx > > it fails with errors for configuration "release" (can’t resolve modu

Re: [Qbs] qbs command line help vs. documentation on qbs.io needs clarification

On Fri, 18 Jan 2019 13:35:24 + Maximilian Hrabowski wrote: > Hi all, > > when looking at the command line help of the build command i get: > > qbs build [options] [[config:] [:] ...] … > Builds a project in one or more configuration(s). > … > So for me this means i can build my project with

Re: [Qbs] Including project files matching git submodules

On Thu, 3 Jan 2019 22:14:09 +0100 Björn Schäpers wrote: > I'm trying to build a repository for multiple libraries and applications, > where > every product is located in an own submodule. Right now I'm at this point: > > root/ > - all.qbs > - libs/ >- libs.qbs >- up.qbs >- lib1/ >

Re: [Qbs] tst_blackbox-qt fails

On Wed, 2 Jan 2019 17:27:29 +0100 Richard Weickelt wrote: > This is how I build and test now: > > qbs build profile:qt > qbs run -p qbs_app profile:qt -- setup-toolchains --detect > qbs run -p qbs_app profile:qt -- setup-qt > /usr/local/Qt/5.9.7/gcc_64/bin/qmake qt > QBS_AUTOTEST_PROFILE=qt qbs

Re: [Qbs] debian patches

On Sat, 22 Dec 2018 03:31:16 + Wookey wrote: > On 2018-12-21 09:18 +0000, Christian Kandeler wrote: > > By the way, I was looking at the patches Debian applies, and I have a > > couple of questions/comments. > > - remove_rpaths.diff: Why is the line that *conditio

Re: [Qbs] tst_blackbox-qt fails

On Sat, 29 Dec 2018 08:48:37 +0100 Richard Weickelt wrote: > I tried to build Qbs from source and to run the autotests on Debian stretch > with Qt 5.9.7 and 5.12.0. After creating a Qt profile (with the built Qbs) > and setting the undocumented QBS_AUTOTEST_PROFILE variable I still see some > tes

Re: [Qbs] --more-verbose causes segfault

On Mon, 17 Dec 2018 05:15:40 + Wookey wrote: > I just uploaded dewalls 1.0.0+ds1-7 to debian to fix some minor lintian > issues: > https://lintian.debian.org/full/woo...@debian.org.html#dewalls > > However I noticed (whilst trying to comply with the new debian policy about > making build lo

Re: [Qbs] How QBS && QtCreator integration does work?

On Thu, 13 Dec 2018 12:52:58 +0300 Denis Shienkov wrote: > > The compiler is looked up in the PATH if the respective property is not > set. > > I'm don't understand a bit.. What if my PATH contains two compilers? Then the first one will be picked up. > > if the respective property is not set

Re: [Qbs] How QBS && QtCreator integration does work?

On Thu, 13 Dec 2018 12:16:52 +0300 Denis Shienkov wrote: > How does it work? Why we need in this Probes at all? The compiler is looked up in the PATH if the respective property is not set. In the case of Qt Creator, all the relevant information comes from the Kits (which are turned into qbs pr

Re: [Qbs] Any novice tickets

On Tue, 11 Dec 2018 21:27:00 +0100 Иван Комиссаров wrote: > That helped, thanks! > > Now I’ve a got a question about module priority. Perhaps I didn’t get the > idea - I tried to use two "internal.libprotobuf" modules with different > priority hoping that if failed to configure, the other wil

Re: [Qbs] iOS code signing

On Sun, 11 Nov 2018 20:18:14 +0300 Павел Лысенко via Qbs wrote: > I'm trying to run application on iOS device. It was built successfully, but I > see no option to sign a bundle. > If I build with qmake, it creates an xcode project where I can set code sign > settings. > If I build with qbs, it

Re: [Qbs] Include current git branch in installation directory

On Fri, 9 Nov 2018 13:53:25 +0100 Christian Gudrian wrote: > Am 09.11.2018 um 13:49 schrieb rich...@weickelt.de: > > I think You can use the Probe item for that purpose. > > That would help to determine the current git branch. But how do I tell > Qbs to prefix that branch to all installation

Re: [Qbs] Include current git branch in installation directory

On Fri, 9 Nov 2018 12:49:12 + wrote: > I think You can use the Probe item for that purpose. > > https://doc.qt.io/qbs/qml-qbslanguageitems-probe.html > > You would combine it with Process service. Search for gitProbe in the > following file to get inspired: > > https://github.com/qbs/qbs

Re: [Qbs] Include current git branch in installation directory

On Fri, 9 Nov 2018 12:18:43 +0100 Christian Gudrian wrote: > I would like to have Qbs automatically install all artifacts into a > directory that contains the current git branch of the working copy. How > can I accomplish that? I'm afraid I don't understand this. Can you elaborate? In particul

Re: [Qbs] Mysterious config: parameter

On Sun, 4 Nov 2018 00:54:25 +0300 Иван Комиссаров wrote: > Perhaps, I am blind, but I can’t find any mentions in documentation. E.g. https://doc-snapshots.qt.io/qbs/cli-build.html#config-configuration-op-op-name > What’s this is used for? It's the name of the configuration to which subsequen

Re: [Qbs] Future of Qbs

On Wed, 31 Oct 2018 06:51:43 +0100 Richard Weickelt wrote: > It would be great if the TQtC could clarify what is planned for the next > feature release and why. That's easy: The release will simply contain everything that has been done since 1.12, i.e. all patches that have already landed in m

Re: [Qbs] Qbs JavaScript processing limits

On Sat, 13 Oct 2018 10:46:47 +0200 wrote: > Hi, I have noticed that my probes that use heavy JavaScript crashes Qbs when > processing very large files/data. The probes in question are here: > > https://github.com/Resurr3ction/qbs-autoproject/blob/master/.autoproject/autoproject.qbs > > > The

Re: [Qbs] Unwanted linkage of non-cpp product by MSVC

On Sun, 7 Oct 2018 15:17:17 +0300 Павел Лысенко via Qbs wrote: > >> I have a project with some cpp products. > >> Also the project includes a non-cpp product. > >> Non-cpp product depends on my custom module that creates a custom > >> deployment package. > >> Module can process both cpp and non-

Re: [Qbs] Relative paths in custom modules

On Thu, 11 Oct 2018 15:35:30 +0200 Christian Gudrian wrote: > I am currently trying to wrap a 3rd party libray in a Qbs module > following the example at > https://doc.qt.io/qbs/howtos.html#how-do-i-create-a-module-for-a-third-party-library. > > I would like to use relative paths to the includ

Re: [Qbs] ERROR: Project file 'foo.qbs' has invalid type.

On Tue, 9 Oct 2018 11:15:13 +0200 Алексей Скородумов <2350...@gmail.com> wrote: > I got the following error with debian:experimental Docker image and qbs > 1.11.1 and 1.12.1: > > ERROR: Project file 'foo.qbs' has invalid type. That's what qbs prints if the project file is neither a regular file

Re: [Qbs] Same precompiled headers for multiple CppApplications

On Fri, 28 Sep 2018 09:45:54 +0200 Mitja Schmakeit wrote: > is it possible to have a single > > Group { > name: "Precompiled Headers" > files: ["precompiled-header.h"] > fileTags: ["cpp_pch_src"] > } > > where the prec

Re: [Qbs] Qbs vs Jenkins

On Tue, 25 Sep 2018 08:00:56 +0200 wrote: > I am wondering if it was possible to replace the Jenkins pipeline with only > Qbs. In theory I see no reason why this should not work given the flexibility > of the Qbs but is there any specific functionality out of the box that could > make the typi

Re: [Qbs] Unwanted linkage of non-cpp product by MSVC

On Sat, 22 Sep 2018 16:15:43 +0300 Павел Лысенко via Qbs wrote: > I have a project with some cpp products. > Also the project includes a non-cpp product. > Non-cpp product depends on my custom module that creates a custom deployment > package. > Module can process both cpp and non-cpp products (

Re: [Qbs] Qbs and Q_PRIVATE_SLOT

On Wed, 19 Sep 2018 14:16:58 +0200 Christian Gudrian wrote: > Am 19.09.2018 um 13:00 schrieb Christian Gudrian: > > How do I prevent one particular moc file from being automatically > > compiled by Qbs? > > To answer the question myself: apart from #including the moc file > explicitly one ha

Re: [Qbs] Building more than one binary from the same sources with multiplexing

On Tue, 4 Sep 2018 17:27:16 +0200 Алексей Скородумов <2350...@gmail.com> wrote: > > (I assume here that you want to build ony a selected subset of products > > twice. Otherwise, you should of course rather build the project for two > > different configurations: > > $ qbs build config:configBar cpp

Re: [Qbs] Building more than one binary from the same sources with multiplexing

On Tue, 4 Sep 2018 15:53:59 +0200 Алексей Скородумов <2350...@gmail.com> wrote: > I would like to build several binaries from the same sources with different > compiler settings (defines). Is this a correct way to go: > > import qbs > > CppApplication { > name: "foo-bar" > multiplexByQbs

Re: [Qbs] cpp.runtimeLibrary:"static" under MSVC2013

On Mon, 6 Aug 2018 16:45:09 +0300 Иван Комиссаров wrote: > Not sure if that helps, but i got same error with _shared_ linkage when > library didn't exported any symbols due to incorrect defines passed to the > linker (Q_DECL_EXPORT/Q_DECL_IMPORT); in that case linker doesn't create an > empty .li

Re: [Qbs] cpp.runtimeLibrary:"static" under MSVC2013

On Mon, 6 Aug 2018 15:16:10 +0200 Dorian Jicquel wrote: > C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN/link.exe > /nologo /DEBUG /PDB:untitled2.pdb /MACHINE:X86 /APPCONTAINER:NO > /OSVERSION:5.01 "/SUBSYSTEM:CONSOLE,5.01" /MANIFEST:embed > C:\Users\djicquel\Documents\build-untitl

Re: [Qbs] Running a helper application right after it is build

ory, "data/trigrams"); >     var outputFile = > FileInfo.joinPaths(product.destinationDirectory, "trigrams.map"); > >     console.info("=== runUtl ==="); >     console.info(runUtl); >     co

Re: [Qbs] Running a helper application right after it is build

rams.map"); > >     console.info("=== runUtl ==="); >     console.info(runUtl); >     console.info(sourceDir); >     console.info(outputFile); > >     var cmd = new Command(runUtl, [sourceDir, outputFile]); >     cmd.descriptio

Re: [Qbs] Running a helper application right after it is build

On Sun, 12 Aug 2018 22:56:31 +0300 Карелин Павел wrote: > I have a project in which, in addition to the main application, > auxiliary utilities are builded. In this regard, I have two questions: > > 1) How do I run an auxiliary utility right after his built, so that it > could generate necessa

<    1   2   3   4   5   6   >