[QBS] Project configuration from within qbs profile

Hi, I have a question regarding project configuration. A qbs project defines a property myProperty. I can of course set the property in the qbs file itself and I can set the property on command line via: qbs build myproject.qbs project.myProperty:bla Would it also be possible to set this

Re: [QBS] Project configuration from within qbs profile

Ok, I've tried to create a module MyModule and access one of its properties, but failed: mymodule.qbs import qbs.base 1.0 Module { name: MyModule property string myProperty } myproject.qbs import qbs.base 1.0 import

[QBS] How to resolve dependencies on generated header files

Hi, my question related to QBS release post at http://blog.qt.digia.com/blog/2014/05/05/qbs-1-2-0-released/ Qbs now supports rules with a flexible number of outputs. For example, you may write an IDL file containing the descriptions of several C++ interfaces. An interface compiler generates

Re: [QBS] How to resolve dependencies on generated header files

Hi, Qbs now supports rules with a flexible number of outputs. For example, you may write an IDL file containing the descriptions of several C++ interfaces. An interface compiler generates a number of header files. The generated header files are automatically taken into account as potential

[QBS] Preserve directory structure during installation

Hi, how can I install a specific file type from a given folder while preserving the folder hierarchy? Example: source-dir | +-- subdir1 | +--file1.h | +--file1.cpp | +-- file2.h +-- file2.cpp should install to: install-root | +-- include | +-- subdir1 | +--file1.h |

Re: [QBS] Enclosing a library product in special linker flags

I have a project with an application and a couple of static libary products as dependencies. When it comes to linking, I need all symbols of one library to be linked into the executable. This can be achieved with the --whole-archive flag. The following line applies this flag to only one

Re: [QBS] propagate compiler options

I have for example application A which depend on static library B and C. Static library B depends on static library C. No problem yet but now static library C depends on B. Now we have a problem because of creating a loop. This is however not uncommon. Most RTOSes will have such kind of

Re: [QBS] run script after building products

Currently I'm struggling that only inputs[application][0] is defined but not inputs[application][1] (I have two products of type application). I guess, You forgot to mark the rule as multiplex in order to catch all files at once. ___ QBS mailing

Re: [QBS] Linking inter-dependent libraries using gcc

I'm trying to link inter-dependent libraries, but as qbs merges the list of libraries it seems to be impossible now. I had a somehow related question some time ago [1] and created QBS-701 [2] which You may want to support. It addresses the same procedure. For example there are two libraries:

Re: [QBS] static library dependency always recompiles

> I develop an open source library which i also use in my projects. I have > created a qbs project for my applications that has the library's qbs as > a dependency, using reference. The problem is that whenever i start a > new application it recompiles the library completely. > > Instead of

Re: [QBS] static library dependency always recompiles

> i'm trying now to set the library in cpp.staticLibraries or directly the > full path to the .a as a cpp.linkerFlags but the project won't detect if > the library has changed. Shouldn't you use cpp.libraryPaths instead of cpp.linkerFlags? > if i modify the library and recompile it, then run the

Re: [Qbs] QBS usage

>> But I've had a hard time to sell Qbs at work for embedded C programming. >> The major issues is that Qbs doesn't support awkward toolchains like IAR >> or TI CGT. > > There is nothing magical about that. If you provide the necessary > information, these can simply be supported by a new cpp

Re: [Qbs] QBS usage

Hello Tino, > I’d like to conduct a small survey about QBS usage in the community to make > investment and feature decisions to the product. I was really worried when your handyman and chief evangelist jumped off the boat towards the dark side in February. So I've got a question back: What are

Re: [Qbs] Any novice tickets

>> https://bugreports.qt.io/browse/QBS-511 (QBS help text is not properly >> format in windows cmd shell) I guess, QBS doesn't use QCommandLineParser at >> the moment? > > No, and I don't think it can, because of the "command plus additional > arguments" syntax that qbs uses. This would be a

Re: [Qbs] Qbs vs Jenkins

> 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?

[Qbs] Meta-modules in Qbs

Hi, this patch introduces meta-modules in Qbs: https://codereview.qt-project.org/#/c/249274/1 > If a dependency is not found, we now search for a matching meta-module > that can generate one for us. We also provide a generic fall-back > meta-module which uses pkg-config to locate the dependency

Re: [Qbs] Including project files matching git submodules

> But I have one more question: Is Project { references: [...] } the only way > to include other files, apart from defining new modules? Please specify "include other files". Did you want to say "include other .qbs files into a project"? If yes, then in addition to the 2 ways you mentioned, you

[Qbs] tst_blackbox-qt fails

Hi, 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 tests failing in tst_blackbox-qt (see log below). Looking closer

Re: [Qbs] bare-metal: Need help with adding of SDCC compiler

> I have planns to add support for SDCC [1] compiler to QBS/QtC for > bare-metal devices. > > But problem is that this compiler supports multiple different arcitectures: Unlike your IAR implementation, I wouldn't probe the compiler and guess qbs.architecture. Instead I would expect the user

Re: [Qbs] Unexpected behavior of MSVC generator

Denis, > > What’s the point of implementing a rule for cpp files directly in the > solution and not implementing it for other cases? I don’t see any use cases. > > I'm don't understand a bit, what do you mean here? I think your view on the build process is too narrow. If all you care about is

Re: [Qbs] tst_blackbox-qt fails

Christian, >> 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 build -p autotest-runner profile:qt >> >>

Re: [Qbs] Future of Qbs

for your reply. Best regards Richard Weickelt ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs

Re: [Qbs] How do I use Parameter property in a module itself?

> Is it true that all module properties should be allowed to be set per-file? > > Product { > Depends { name: "mymodule"; } > mymodule.useFeature: true // enable some probes here, do heavy checks > > Group { files: «file»; mymodule.useFeature: false; } // does nothing, > all

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

Tobias, I think it is of utmost importance for the survival of Qbs that it is fully supported by an IDE like QtCreator. > Note that this is about the build system used to *build Qt Creator with*, not > about *build systems supported by Qt Creator*. I would personally like to keep > qbs supported

Re: [Qbs] Donation to QBS developers/maintainers/contributes

> If I am right, one urgent task is to remove the dependency of Qt Script. I don't think it's urgent. It might not even be necessary given that Qbs won't be Qt's next build system and won't have to be bootstrapped. But if you have good ideas, feel free to discuss in

Re: [Qbs] Donation to QBS developers/maintainers/contributes

>> However, will this help to get new developers? Right now, there are not that >> many contributors. > > I agree, how much money do you want to raise? And what for? > For now Qbs can use Qt (company/project) infra, so there's no need to > manage an infra. The Qt Company pays for qt.io. We can

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

> 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 an option when it comes to CI integration etc. > > Next time I

Re: [Qbs] Any novice tickets

> Meanwhile, I get another question… I think, I already asked it, but still. Is > the magic behind config parameter documented somewhere? Have you looked at https://doc.qt.io/qbs/cli-build.html#parameters ? This was updated only recently. ___ Qbs

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

> My next question is how to fix the bug in conan qbs generator? driverFlags > does not exist in conan qbs generator. You can either 1. Wait for this fix to be integrated: https://github.com/conan-io/conan/pull/5452 2. Modify the Qbs generator in your Conan installation 3. Implement your own

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

>> 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. Regardless of the CMake inherent beauty. If you (Victor) want to have a profound answer to your question, you should explain what

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

> No, this is not possible. The reason is that in common case those products > (applications, libraries) will diverge in some way. For example, you might > want to use different resources - icons (you probably do not want to name > them icon1.png and icon2.png, right?), .desktop entires on Linux,

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

Nice, is there a possibility that the Qt Sanity Bot will review the style and give feedback immediately? ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs

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

> How to add -pthread option into projects? > ... >     cpp.cppFlags: ["-pthread"] Try using cpp.cxxFlags or cpp.driverFlags instead. cpp.cppFlags has a different meaning. See https://doc.qt.io/qbs/qml-qbsmodules-cpp.html#cppFlags-prop > I encountered this error too when use qbs file generated

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

> How to add -pthread option into projects? > ... >     cpp.cppFlags: ["-pthread"] Try using cpp.cxxFlags or cpp.driverFlags instead. cpp.cppFlags has a different meaning. See https://doc.qt.io/qbs/qml-qbsmodules-cpp.html#cppFlags-prop > I encountered this error too when use qbs file generated

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

> Why not have a central property that controls these dependencies everywhere? > Can be done without redundant code via a proxy product: > > Product { > name: "A" > property string libAVariant: "a1" > Export { > Depends { name: "A-1"; condition: product.libAVariant === "a1" }

Re: [Qbs] Will Qbs 1.15 be developed and released by The Qt company?

> Thanks to The Qt company and all Qbs contributors, we know Qbs 1.14 release > is around the corner. > > I think it should be the time to let Qbs contributors and users to know > more the future of Qbs. > > Will Qbs 1.15 be developed and released by The Qt company? If the Qt Company follows

Re: [Qbs] run test executables outside QBS environment

> I'm looking for a way to run test executables - created by QBS - outside > of a QBS environment. To me this looks problematic since you can define > runVars inside QBS that are not known outside of QBS. > > Any idea how to handle this? An idea, not a solution. You could generate a shell

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

> CppApplication { > name: "test" > cpp.includePaths: sourceDirectory > files: [ > "main.cpp", > ] > Depends { name: "Qt"; submodules: ["core", "xml"] } > Depends { name: "kdsoap" } > Rule { > multiplex: true >

Re: [Qbs] How to download and uncompress files with Qbs directly?

> Does Qbs support downloading and uncompressing files directly? Not directly, because it is a build automation tool and not a package manager. > For example, I need to use Eigen 3.3.7 > in my project, and > install it in the build folders of

Re: [Qbs] How to download and uncompress files with Qbs directly?

> Do you think I can use Network Access API of Qt to download files and > QByteArray::qUncompress to uncompress files in Qbs code? Qbs doesn't provide access to these API. And even if it would, they are not sufficient to achieve what you want. I think you are better off using external tools for

Re: [Qbs] How to download and uncompress files with Qbs directly?

>> Another automated and platform-independent library interface would be Conan >> or vcpgkg. Have you searched for packages on bintray? >> > these are some of the services that would need wrapping. Why would you wrap these tools with Qbs and not use them side-by-side or - the other way round -

[Qbs] Define the link order without an explicit dependency

Hello, 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 can only depend on one of them at a time StaticLibrary {

Re: [Qbs] Ideas inspired by pro2cmake.py

> On Fri, Sep 20, 2019 at 10:14:54PM +0800, Vincent Hui wrote: >> It seems that it is possible to develop pro2qbs.py, [...] >> > patches for https://bugreports.qt.io/browse/QBS-586 welcome. ;) Indeed, that would be a great contribution, Vincent. ___ Qbs

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

> I created a simple project to copy an executable generated by > CppApplication. However the executable is not copied. > > I cannot figure out why? Can anyone tell me why? Please read https://doc.qt.io/qbs/qml-qbslanguageitems-rule.html#rules-and-product-types Your rule is not executed because

Re: [Qbs] Understanding installation rules

> The reason why I added the "application" tag to the rule is that this > seemed to force the execution of the rule, with otherwise wouldn't be > considered. This is semantically wrong because your rule does not produce an "application" artifact. I'd suggest to add "desktopfile" to the

Re: [Qbs] [baremetal] I looking proffesionals faced with Cypress FX2 && IAR

> It did not helps, because a problem is somewhere  deeped. E.g. in this code: > > static BOOL ep0_std_descriptor_proc(void) > { >     BYTE XDATA *pdesc = >     (BYTE XDATA *)hid_ep0_std_desc_get(); >     if (pdesc) { >     SUDPTRH = usb_word_msb_get(pdesc); >     SUDPTRL =

[Qbs] 1.15 branch created

Hi, Christian has branched off qbs 1.15 yesterday. Scheduled release date for version 1.15.0 is end of November (together with Qt Creator 4.11) [1]. We recommend users to try this branch with their projects and report back any new problems they find. Qt Creator 4.11 beta still ships the Qbs 1.14

Re: [Qbs] [baremetal] I looking proffesionals faced with Cypress FX2 && IAR

Hi, > Currently it does work with Keil C51 compiler && SDCC compiler. But, it does> > not work with an IAR 8051 compiler. I guess you do not have JTAG access to this device and can step-debug. But it looks like you have GPIOs that you could access with a logic analyzer. > I don't know why, but

Re: [Qbs] Session at Qt Contributor Summit next month?

Hi Kai, thanks for the heads-up. > Nov 19-21th 2019 Qt contributors gather in Berlin to discuss the state of > the project, make plans and sometimes also do decisions  I'm wondering > whether there's interest also for a Qbs session? So far nobody registered > one ... Since Qbs will not become

Re: [Qbs] Module adding source files to a project

> Should the AppImageKit repository (or only the parts needed for building > the runtime.c file) be imported into the QBS repository (maybe added as > a git submodule)? Or should we fetch the sources at runtime? Ideally, I think, the user would just invoke some tool and use a prebuilt binary and

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

sure whether you will do the 1.15.0 release at all, please communicate that as well. That is the only chance for the community to step up and take over responsibilities. Thanks Richard Weickelt ___ Qbs mailing list Qbs@qt-project.org https://list

Re: [Qbs] Construction project.buildDirectory

Hello Pavel, >> Some code has been moved around to fix a different problem with >> Project-level probes, so this appears to be a side effect of that. >> However, you can just leave off the "project.", and it will work both >> with 1.15 and 1.14. > Yes, i did so. But I wanted to find out if the

Re: [Qbs] Construction project.buildDirectory

> 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/snapshots/qtcreator/4.11/4.11.1/187/ or just wait for > the official

Re: [Qbs] Interfacing Qbs to Conan

Hello Leon, I am really glad to read that Clausmark is looking into interfacing Qbs with Conan. Since Conan gets more and more traction and brings great advantages, Qbs should support it well. That's why I want to share some more detailed thoughts on this topic. I'll start with what I originally

Re: [Qbs] QBS behaviour while linking

Hi, > Hmm ... I observe that the "Compile Output" inside QtC sometimes stops while > linking a library and (using htop) one can see that no other core is used. > After that further compilations can be seen. > Maybe the linking of the component A has to be completely finished before > compiling

Re: [Qbs] Passing paths to properties

> 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? That is - by definition - relative to qbs.installRoot. > Also, while

Re: [Qbs] Exporting libraries to link only for MinGW

> You don't need a group here in the first place. Just > cpp.dynamicLibraries: { >var libs = []; >if(qbs.toolchain.contains("mingw")) >libs = libs.concat(["pthread", "ole32"] ) >return libs; > } Or to be more explicit: You **must** not use the Group item for this purpose. The

Re: [Qbs] Interfacing Qbs to Conan

Jochen, > Basically, we are doing it the way you described. However, we decided not > to make a conan module which the generated modules depend on because we > expect that this would lead to multiple invokations of `conan install` > (one for each generated module) which we want to avoid. This

[Qbs] Qbs 1.15.0 released

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

Re: [Qbs] Deployment and dependency bundling

> I've got it working to some point by adding these properties to the Rule: > > inputsFromDependencies: ["application", "dynamiclibrary"] > multiplex: true > outputFileTags: ["deployed_library"] > > but this causes the Rule to be run only for the application's > dependencies, and not

Re: [Qbs] Mingw issues

> It looks like the value of > `profiles.mxe-i686-w64-mingw32-static.cpp.toolchainPrefix` was > incomplete (you can see it from the config pasted above). It should have > been "i686-w64-mingw32.static-", and after changing it to that value, > the build started. > > So, actually, my problem is

Re: [Qbs] Building Qbs for conan/bintray on Gitlab

> Oh. Interesting. I did not saw that the plugins are not compiled. But I > don't know why. If you look into conanfile.py it just calls > > qmake -r qbs/qbs.pro CONFIG+=qbs_no_dev_install > CONFIG+=qbs_no_man_install CONFIG+=qbs_use_bundled_qtscript > > Followed by a simple >

Re: [Qbs] Qtc: Cannot find the androiddeploy Json file

> When i want to "run" on the device: > Initializing deployment to Android device/simulator > Deploying to 150c980e8288de07 > Cannot find the androiddeploy Json file. > Error while building/deploying project Neon Factory Tools (kit: > Android for arm64-v8a (Clang Qt 5.12.8 for Android ARM64-v8a))

Re: [Qbs] setup-android, no --system?

> Because this file will end up in some "home" directory, which might > not be accessible to the end user (eg. custom UID, GID, home, ...) > Having a system wide qbs conf is bullet-proof in that regard. > So, yes i would prefer to run the above command, but with '--system' > and no, you cannot

Re: [Qbs] Using ConanfileProbe with yocto cross compiling toolchain

> Sorry. I meant how to extract the environment variables from the yocto script. > My idea was to source the script in a process > with https://doc.qt.io/qbs/jsextension-process.html  > and then just query all the process environment variables with >

Re: [Qbs] setup-android, no --system?

> I find this quite useful when creating docker container. > The idea is that the container (name) completely define the whole > build config, and running "qbs build" in there build an APK with the > "right" configuration. > No env involved, no foreknowledge of the profile name, it just work > out

Re: [Qbs] setup-android, no --system?

> Thanks for the detailed explanation, i've been looking at your scripts > and docker files recently (and have adopted your install-qt.sh! ;)) > I think we don't have the same use case, you need to build and test > qbs, i need to build and test a android+qt+qbs container that works > "out of the

Re: [Qbs] Using ConanfileProbe with yocto cross compiling toolchain

> I just stumbled across a scenario in which we use with multiple profiles for > different cross compiling toolchains. Yocto creates a script which exports > environment variables. We normally just extract the needed values from the > script and set them as additional qbs profile settings. > This

Re: [Qbs] Using ConanfileProbe with yocto cross compiling toolchain

> I will try this approach. But maybe I use `conan install -e` instead of > setting the environment variables for the complete process. If the result is the same, then why not. > Do you know how I can easily extract the environment variables? >  

Re: [Qbs] Android multiarch

> As an experiment, i've just tried Qt-5.14, and this has enabled > multi-arch on Android. > I can select the list of architecture i want to support with > qbs.architectures. > This works for libraries, but my application is disabled: > Error while handling 'TestApp' > Product 'TestApp' had

[Qbs] 1.16 branch created

Hello, we branched off qbs 1.16 today. Scheduled release date for version 1.16.0 is mid of April (together with Qt Creator 4.12) [1]. We recommend users to try this branch with their projects and report back any new problems they find. Snapshots of Qt Creator can then be obtained from [2].

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

> 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 iOS-arm64 but attempting to link with file built for

Re: [Qbs] Building Qbs for conan/bintray on Gitlab

Hello, > I try to build a Qbs conan package (with static linked Qt) so conan could > just install Qbs with a simple "build_requires". Building the conan package > works fine on my local machine. But when I use Gitlab-CI to build the > packages it fails to build. > To build locally I use the

[Qbs] Qbs 1.15.0 released

Hello, I'd like to announce the release of Qbs 1.16.0 if you haven't seen the blog post, yet. Source and binary packages as well as a change log can be found at https://download.qt.io/official_releases/qbs/1.16.0/. This release of Qbs is also shipped as part of Qt Creator 4.12.0. Please refer to

Re: [Qbs] Issues building for Android

t 5.15 was missing so far (https://bugreports.qt.io/projects/QBS/issues/QBS-1580), but there is a good chance that this will be fixed soon. Best regards Richard Weickelt ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs

Re: [Qbs] Issues building for Android

> I now also tried to build using Qt 5.14.2, but no change (still problems > starting with not finding the aidl tool).  > > Seems like something is broken where the kit is set up, as the > Android.sdk.buildToolsVersion is not set. > > Is a clean install of Qt, QtCreator + QtCreator setting up

Re: [Qbs] How to explicitly prohibit the use of qt-framework in project

Hi, you may try qbs build ... moduleProviders.Qt.qmakeFilePaths:/invalid to configure a non-existing location. You can also set this property in your profile if you like. -Original Message- From: "Карелин Павел" To: qbs@qt-project.org Sent: Mon, 19 Oct 2020 20:26 Subject:

Re: [Qbs] Using ConanfileProbe with yocto cross compiling toolchain

> I archived my goal with the following code: Good to hear. Thanks for posting the code. > But this code has some restrictions (like using bash or zsh but not fish). I wouldn't consider it a restriction not to support an exotic shell. > Thus I don't think that it should be made into the

Re: [Qbs] dependency tracking

>> "testinput.h" file contains "#include "a.h" directive. Changing >> testinput.h results in a generator run followed by a C++ compiler run. >> Changing a.h results in no action, although in this case the generator >> is intended to reprocess its input. > > It's expected that the generator

Re: [Qbs] Cpp module for WebAssembly

On 27.10.2020 12:27, Dan Pat wrote: > You can provide your own cpp implementation by overriding the search > path, but I don't see how you would be able to refer to the contents of > the original directory. Note that the files there are implementation > details and their presence

Re: [Qbs] QBS script parsing speed

> I would like to know if any measures are being planned to > increase the speed of re-parsing a project? I am using QtCreator 4.11.2 > (QBS 1.15.1) Some ideas: 1. Incremental project resolving: Take the dependency graph into account when re-resolving a project so that unchanged products are not

Re: [Qbs] QBS script parsing speed

> We faced similar problems but our resolve times were even higher (30 s to > 2 mins). > > We were able to work around this and significantly reduce the resolve > times by avoiding transitive dependencies (meaning exporting > dependencies). I would like to understand why exactly this pattern

Re: [Qbs] QBS script parsing speed

Jochen, >> Well [the time] goes into "Handling Products". So it is >> ModuleLoader::handleProduct(). >> And there, it could be the ModuleMerger. But speculation is dangerous when >> discussing about performance. > See https://lists.qt-project.org/pipermail/qbs/2019-August/002546.html > > You

Re: [Qbs] Applying cxxFlags to certain files

> Hi. I have a code generator, encapsulated in a dedicated Module, producing > c++ source files. The generator's artifacts are then picked up by the > "cpp" > module according to the rules. For such generated files (and for them > only) > I would like to pass certain flags to the compiler (to

Re: [Qbs] Applying cxxFlags to certain files

On 10.07.2020 14:18, Иван Комиссаров wrote: > You can access the original value via input.cpp.prop: > > fileTags:[tag], > > filePath:outputDir+"/"+FileInfo.baseName(input.fileName)+suffix, > > cpp:{ > > includePaths:[].concat(input.cpp.includePaths,outputDir), > > warningLevel:"none", > > }

[Qbs] 1.17 branch created

Hello, we branched off Qbs 1.17 today. Scheduled release date for version 1.17.0 is end of August (together with Qt Creator 4.13) [1]. We recommend users to try this branch with their projects and report back any new problems they find. Snapshots of Qt Creator can then be obtained from [2].

Re: [Qbs] Evaluation of Conditional Depends

Christian Kandeler wrote on 10. June 2020 10:09 (GMT +02:00): > On Tue, 9 Jun 2020 20:55:43 +0200 > Christian Gudrian wrote: > >> Could it be that only a restricted set of variables is available during >> evaluation of the module’s „condition“ property? Neither >> „product“ nor any imported

Re: [Qbs] Evaluation of Conditional Depends

> And of course the module's own properties set in the module file, except > those referring to probes. But we do evaluate the module condition in a > product context. Is that not the real product context or at least very > close? E.g. if product sets moduleX.propA to true and depends on moduleX,

Re: [Qbs] Evaluation of Conditional Depends

Christian Gudrian wrote on 7. June 2020 10:48 (GMT +02:00): > > I’ve put a simple example project on GitHub: > https://github.com/cgudrian/QbsConfigurationDemo > . > > I am trying to implement basic Qbs support for the RT operating system >

Re: [Qbs] Evaluation of Conditional Depends

> In ModuleA there is a property enableFeature which by default is false. > > ModuleB conditionally depends on ModuleC, if ModuleA.enableFeature is true. > > A Product depends on ModuleA and ModuleB and sets ModuleA.enableFeature to > true. However, ModuleC is not used as a dependency. Could

Re: [Qbs] Rule.Return dynamic list for outputArtifacts

> However, yesterday I came across a small > sip-file, and the generated cpp-files turned out to be not 6, but only 5. > Naturally, my rule failed. > > Question: how can I resolve my situation? > Of course, I can tell the sip-generator to create fewer cpp-files (parameter > -j), but I would like

Re: [Qbs] Deploying broken symbolic links?

Hello Heiko, > Is there any option to tell Qbs not to follow a symbolic link given > within the "files" list? This seems to be impossible, probably because Qbs for validity of source artifacts. But you can write a rule that creates the symlink when building: Product { type:

Re: [Qbs] AutotestRunner in QtCreator

What do you mean, it does not show up? It should show up as a product in the project view, but it is not built by default. In order to "run" it, you need to 1. have application products with the additional type autotest. Just write something like: Application { type:

Re: [Qbs] Qt6 support

1.17.1 as in the 1.17 branch is shipped with latest Qt Creator 4.13.x, but we haven't made the tag yet nor published any packages. 1.18.0 is around the corner and will be released in about 2 weeks. -Original Message- From: Maximilian Hrabowski To: "Иван Комиссаров" Cc:

Re: [Qbs] AutotestRunner in QtCreator

> 2. Build the AutorestRunner product explicitly. It will not show up under > "run". > That's what I meant, I can not select it as a run target. > And I don't know how to say "just build product X", if it's not a run target. In the Projects view, right-click on the autotest-runner product and

[Qbs] 1.18 branch created

Hello, we branched off Qbs 1.18 recently. Scheduled release date for version 1.18.0 is begin of December (together with Qt Creator 4.14) [1]. We recommend users to try this branch with their projects and report back any new problems they find. Snapshots of Qt Creator can then be obtained from

Re: [Qbs] How to explicitly prohibit the use of qt-framework in project

>> qbs build ... moduleProviders.Qt.qmakeFilePaths:/invalid > Yes, it works. But is it possible to do such a disconnection from the > project itself? You mean in the project files? You can do that only on Product level, not for the entire project: Project { // cannot set global

[Qbs] 1.19 branch created

Hello, we branched off Qbs 1.19 today. Scheduled release date for version 1.19.0 is mid of April (together with Qt Creator 4.15) [1]. We recommend users to try this branch with their projects and report back any new problems they find. Snapshots of Qt Creator can then be obtained from [2].

Re: [Qbs] Depending on binary from install-root

> Any idea how I can force the rule to depend on the binary in install- > root/bin? I think it's cleaner to follow https://code.qt.io/cgit/qbs/qbs.git/tree/examples/code-generator and use the transpiler binary in the build directory. That is what your rule really depends on

Re: [Qbs] Failed build the project with QBS 1.22.1

Hi, My old version works with replacing 'product' on 'exportingProduct':    property var exportIncludePaths: [     "./",     "./shared",     ]     cpp.includePaths: exportIncludePaths     Export {     Depends { name: "cpp" }     cpp.includePaths:

  1   2   >