Re: [Qbs] How to setup: QtC, Qbs, Clang on Windows

Right, that was it! I would have sworn I haven't touched the project files, maybe that error was there all along. Thanks, it works now. __ Od: "Иван Комиссаров" Komu: resurrect...@centrum.cz Datum: 27.03.2020 19:14 Předmět: Re: [Qbs]

[Qbs] How to setup: QtC, Qbs, Clang on Windows

I have been struggling with setting up Qbs inside Qt Creator so it uses clang-cl on Windows. On the command line it is auto-detected and works just fine. In QtC I need to add manually compilers for C and C++, both set to clang-cl.exe (in c:/program files/llvm/bin). Then I add new Kit and

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

What is the reason for the difference between compiler calls with moc between Qbs and CMake/Ninja? It looks like Qbs is actually compiling the moc stuff separately while CMake/Ninja don't or rather they compile it as part of other sources somehow? It would explain both the longer time they

Re: [Qbs] [RFC] Add a clang-format config file to qbs repo

+1   I cannot recommend clang-format enough. I can hardly imagine working without it.   __ Od: "Christian Gagneraud" Komu: "qbs" Datum: 08.07.2019 11:39 Předmět: [Qbs] [RFC] Add a clang-format config file to qbs repo Hi there, I

[Qbs] Qbs JavaScript processing limits

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 most problematic Probe is the "dependencyscanner". It

Re: [Qbs] Qbs vs Jenkins

I certainly don't want to reinvent the whole CI system. The Qbs can handle pretty much anything except one thing - its own bootstrapping. By that I mean how would you trigger a Qbs build on a remote server? The Jenkins comes with a server of its own that you can notify, trigger and get info

[Qbs] Qbs vs Jenkins

Hi,   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 typicial tasks performed by Jenkins easier?

Re: [Qbs] Creating many products from a list

I have a related question. Is the generic property multiplexing moving forward? I remember Jake saying that he would like to have it too but that there are some concerns about how it would fill in the current state of Qbs (hence the current limitation to those three properties).

Re: [Qbs] Creating many products from a list

I have been asking similar question before and the answer is sadly no there is not. Out of the box there is multiplexing but while in theory it could support any property it is currently limited to only a few. Nevertheless I have created something that might actually do exactly what you want -

[Qbs] qbs-autoproject 2.0.0

After some time improving the *qbs-autoproject* for my private use I have now released it as Version 2.0.0:   https://github.com/Resurr3ction/qbs-autoproject/releases/tag/Version_2.0.0   What it is in short:   Single project file that will automatically detect your projects, products and will

Re: [Qbs] Property from parent overridden instead of concatenated

And I will answer myself after re-examining the docs. One has to use `base.concat()` when appending inherited properties. I think I even understand why that is not default - it would not be possible to override the property entirely otherwise.   

[Qbs] Property from parent overridden instead of concatenated

I remember seeing something about this but I wanted to know if this is a WAD or bug. Consider:   //imports/MyProduct.qbs Product {     Depends { name: "cpp" }     cpp.defines: ["MY_DEF"] }   //SomeProject.qbs MyProduct {     cpp.defines: ["ANOTHER_DEF"] }   What will be the value of

Re: [Qbs] Qt Quick Tests and custom import paths

It does, I use following quite a lot:   property var foo: (function (arg1, arg2) { return arg1 + arg2; }) property var elsewhere: foo()   __ Od: Christian Kandeler Komu: qbs@qt-project.org Datum: 17.05.2018

Re: [Qbs] Linking with clang code coverage flags

Indeed I am. Works like a charm. :-) Thank you! __ Od: Christian Kandeler Komu: qbs@qt-project.org Datum: 27.04.2018 15:16 Předmět: Re: [Qbs] Linking with clang code coverage flags On Fri, 27 Apr 2018

[Qbs] Linking with clang code coverage flags

I ran into peculiar issue. Trying out the clang code coverage reporting using Source-base Code Coverage . The command line examples works as expected. Adapting it to link with Qt and again from the command line it works as expected.

Re: [Qbs] Unable to run qdoc in Qt 5.11

Well it is reported only as warning because it does not prevent qdoc from finishing but it will not find any of the project's headers so it will not create any documenation. As Martin Smith explained here

Re: [Qbs] Unable to run qdoc in Qt 5.11

So I finally figured it out after browsing through both qdoc 5.11 and qbs sources. Several things that needs to be done for the below product to work:   1. Install clang3.9 and put its bin into system PATH. Later versions do not work (contrary to what documentation claims)   2. All header files

[Qbs] Unable to run qdoc in Qt 5.11

In Qt 5.11 qdoc underwent major rewrite with Clang as its backend. Unfortunately there is something wrong or missing now in the Qbs product that is supposed to build documentation with qdoc. Product that works with Qt 5.10 qdoc (no clang): Product {     Depends { name: "Qt"; submodules: [

[Qbs] qbs-autoproject 1.1

Hello again,   I have successfully updated the qbs-autoproject to work with the new release of Qbs and dubbed the new release 1.1 found at  https://github.com/Resurr3ction/qbs-autoproject. It continues to work with Qbs 1.10 as well.   qbs-autoproject is a qbs project file that automatically

Re: [Qbs] Property accessibility from Probe in 1.11

Alright I see. Currently I am using it to access "global" functions defined as properties in top-level Project. Would moving them to external Module and importing that work in Probe? Or do I need to specify re-declare those I use in each Probe?

Re: [Qbs] Build QTests from single Product

And in fact I do have a suggestion, what about new property in the common.qbs:   property var userValues: [] property var userValue readonly property var multiplexMap: ({     userValues: "userValue",     profiles: "profile",   With this one could multiplex over pretty much anything as in any

Re: [Qbs] Build QTests from single Product

I tried what you suggested and it seems to work without problems:   In common.qbs I created two new properties:   ``` property stringList files: []` property string file ```   And modified the internal property:   ``` readonly property var multiplexMap: ({     files: "file",     profiles:

[Qbs] Build QTests from single Product

In other testing frameworks like Google Test the test executable typically contains all test cases for the given module under test so there typically are as many products for tests as there are production modules. With QTest this is unsupported (although doable) and for good reasons too (mainly

Re: [Qbs] qbs-autoproject

> A desirable feature here would be to be able to control the order in > witch the match are done, this way one could, for example, put specific > patterns at the top, and catch-all at the bottom. The items are prioritized in order of their definition. I believe I do mention that somewhere in

Re: [Qbs] qbs-autoproject

We have discussed some configuration issues via separate e-mail but few things worth pointing out here: - I should likely call close() explicitly after reading a file. One gets spoiled from QFile's destructor. :-) That might alleviate the too many open files issue. I reckon it ultimately hits

[Qbs] qbs-autoproject

Hi everyone,   I would like to announce:   qbs-autoproject "A project file to end all project files." https://github.com/Resurr3ction/qbs-autoproject     It is the generic qbs project file that automatically detects projects, products and

Re: [Qbs] How to make 'cpp.link: false' part of the Export item within custom item?

And I will answer myself as the answer was in the Parameters item documentation: http://doc.qt.io/qbs/parameters-item.html   __ Od: Komu: Datum: 22.10.2017 08:24 Předmět: [Qbs] How to make

[Qbs] How to make 'cpp.link: false' part of the Export item within custom item?

Having a custom Item I would like to disable linking to the dynamic library for all those that depend on it since it is a plugin just like what Jake talks about in the 1.9 release blog . Qbs generates the warning that cpp.link property was

[Qbs] Depending on item with dynamic name

Hi, is there a way do depend on a product with dynamically generated name? Via id prehaps or some other identifier?   E.g.:   import qbs import qbs.FileInfo   Project {     Product     {         name: FileInfo.baseName(sourceDirectory)     }     Product     {         Depends { name: "???" }    

[Qbs] Getting Qt directory in Project or Probe

Hi,   is there a way that one could access Qt.core properties outside of a Product item? I am after binPath but I cannot get it from Project or Probe. Since Depends is illegal but in Product and there does not seem to be an option to "import" it otherwise I wonder if there is a way to access

Re: [Qbs] Relation between Product and Export

Thanks for the clarification Christian and Joerg! I am looking forward to the new version. Let me know if I could help in any way like testing out some specific features or so. I like Qbs and what it can do. :-) Michael __ Od:

[Qbs] Relation between Product and Export

Hello, I think I have another possible issue that you may be aware of as well (or I am just missing something). The Export item is a great way to control what the items that use the Product that defined it recieve. While that direction works pretty well I have major problems using the

Re: [Qbs] Probes caching in Qt Creator

It worked! Thank you so much, it was really bothering me. :-) Best wishes, Michael __ Od: Christian Kandeler Komu: qbs@qt-project.org Datum: 24.07.2017 10:22 Předmět: Re: [Qbs] Probes caching in Qt Creator

[Qbs] Probes caching in Qt Creator

tl;dr Qbs Probes that write project files are not correctly evaluated (at least not in Qt Creator)     I do not know whether this is an issue of Qbs or Qt Creator but I will describe it, provide the minimal source and you could probably tell me. :-)   So I continue in my efforts of

Re: [Qbs] Building QDoc based documentation with Qbs

I made it to work by providing all variables to the qdocconf file I possibly could. Then it started working but I would love to know which one(s) are mandatory when running through Qbs as they apparently were not needed for running from the command line. I have also discovered some

[Qbs] Building QDoc based documentation with Qbs

How do one build QDoc based documentation with Qbs? I have been struggling with making this to work. The documentation says next to nothing about it and the use case I found in Qbs source code did work only partially (it created qch file for one module but no HTML or anything else so

Re: [Qbs] Qbs Automatic Projects

Thank you and I understand the reluctance. In this case I believe it would be worth it. What I did is merely a workaround because there is no other way to dynamically create products in Qbs. By lifting that restriction (QML supports dynamically created objects) it would open almost endless

[Qbs] Qbs Automatic Projects

Hi, my name is Michael and I have originally posted this to Qt Forums but it was pointed out that this mailing list is probably better place for it (original post ):       For a long time I was using qmake in a forgetful manner. Letting Qt