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

2020-05-18 Thread Kai Dohmen via Qbs
Hello. I archived my goal with the following code: Yocto_Conan_Qbs.qbs: import qbs import qbs.File import qbs.FileInfo import qbs.Probes import qbs.Process import qbs.TextFile import qbs.Utilities Project { references: conanFileProbe.generatedFilesPath + "/conanbuildinfo.qbs" Probe {

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

2020-05-15 Thread Kai Dohmen via Qbs
> > Do you know how I can easily extract the environment variables? > > https://doc.qt.io/qbs/jsextension-environment.html#currentenv seems like a > > solution but I don't know how to access a process environment with this. > > Which environment variables? If I understood you correctly, then you

[Qbs] Using ConanfileProbe with yocto cross compiling toolchain

2020-05-15 Thread Kai Dohmen via Qbs
Hello, 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

2020-05-15 Thread Kai Dohmen via Qbs
> 1. Add an additionalEnvironmentVariables property to ConanfileProbe > 2. Append these to the process environment in ConanfileProbe. See >https://doc.qt.io/qbs/jsextension-process.html#setenv > 3. Add an additional Probe item in your project file that extracts >the environment variables

[Qbs] Building Qbs for conan/bintray on Gitlab

2020-03-21 Thread Kai Dohmen via Qbs
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 following

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

2020-03-24 Thread Kai Dohmen via Qbs
> I don't see compiler/linker invocations for any of the plugins in the gitlab > output, so it seems to be a build system issue. When running locally in a > Docker container, Qbs builds correctly. I have put above lines (without > invoking python build.py) in a Dockerfile and ran > > docker

[Qbs] Why was protobuf.outputDir removed

2020-09-15 Thread Kai Dohmen via Qbs
Hello, the subject states my Question. Normally I create a static library from proto files. This static library can be linked into different applications. This really comes in handy when using conan. But since protobuf.outputDir was removed I cannot set the Exported includePaths dir properly.

Re: [Qbs] Why was protobuf.outputDir removed

2020-09-16 Thread Kai Dohmen via Qbs
») to make filtering more fine-grained and avoid > overlapping with other headers. > > Ivan > > > 15 сент. 2020 г., в 09:00, Kai Dohmen via Qbs > написал(а): > > > > Hello, > > > > the subject states my Question. > > Normally I create a static libr

Re: [Qbs] Problem getting build order right when I use a header generator

2022-07-13 Thread Kai Dohmen via Qbs
Hello, did you try to append "hpp" to the static libraries type property? Maybe this would force Qbs to generate the headers before consuming the library. Regards, Kai Am Mi., 13. Juli 2022 um 22:50 Uhr schrieb Jochen Becher < jochen_bec...@gmx.de>: > Another observation: > > After I built the