Re: [Qbs] Crash after build

Hello! Have you tried newer versions? The recent is 2.3.2 which fixed quite a few bugs. Logging won’t help much, the easiest way is to build Qbs from source in debug mode and run under debugger. Also you should try to reproduce the crash in console mode rather than in ide. You can copy the

Re: [Qbs] Problems with Xml.DomDocument through a module provider

and the problem persists. But only if the condition is false, if it's true (for another target) all is fine. There's a lot in that import, but nothing that sets the version, only one module which reads it. Am 14.07.2024 um 00:15 schrieb Иван Комиссаров

Re: [Qbs] Problems with Xml.DomDocument through a module provider

ot;1.0.0" > Export { version: exportingProduct.version } > } > > MyOwnApplicationImport { > condition: someConditionWhichEvaluatesToFalse > name: parent.name > version: details.version > > Depends { name: parent.name + " Details"; id: details } > } > } >

Re: [Qbs] Rule to create library symlinks on macos

That’s an interesting use-case you brought. I replied in the linked issue on how to achieve what you want. Ivan > 13 июля 2024 г., в 13:21, Maximilian Hrabowski > написал(а): > >  > Hi all, > > i use qbs on macos to combine arm64 and x86_64 library builds into one > universal library.

Re: [Qbs] How to provide an "export" header

You can add it once to the base item of the products (possibly with some customisation using a prop). Usually there is already such an item in every product. Ivan > 13 июля 2024 г., в 14:13, Björn Schäpers написал(а): > > Am 13.07.2024 um 02:15 schrieb Иван Комиссаров: >> >

Re: [Qbs] How to provide an "export" header

> 12 июля 2024 г., в 23:24, Björn Schäpers написал(а): > > Hi, > > I have multiple dynamic libraries in my project tree, and use an export > header similar to your qbs_export.h. Overtime the style of those headers had > changed a bit and recently I replaced them by something generated from

Re: [Qbs] Problems with Xml.DomDocument through a module provider

This (again) seems like an infinite recursion https://bugreports.qt.io/projects/QBS/issues/QBS-1793 and has nothing to do with XML. Do you have a property accessing itself (maybe indirectly) by any chance? Maybe in a Probe? You can try applying

Re: [Qbs] Passing data from current project to module-provider

You’d need to add a property in the provider and set in the top-level project to path. The reason that providers cannot access product/project props directly is because we use provider props as a prodiver cache key to avoid generating modules for every product. Adding all possible props of the

Re: [Qbs] Using ES6 templates string in qbs files

Before Qbs passes the JS code to the engine, it parses it using the QML parser (even for pure js files, not sure why though). We use a very old version of a parser copied from Qt which doesn’t support all JS features. Ivan > 26 июня 2024 г., в 14:58, Maximilian Hrabowski > написал(а): > > 

Re: [Qbs] Cross-build Qbs, in particular with Yocto

> 20 июня 2024 г., в 11:05, Uwe Salomon написал(а): > > Hi all, > > has anybody experience with cross-building Qbs itself? We are trying to build > Qbs for an embedded platform using Yocto, in order to be able to do builds on > that platform later. Should be possible, maybe with some

Re: [Qbs] WebAssembly Support

Hello! We have an open PR [0] but it’s still a work in progress. I am not sure if the original author has plans to finish it though. I’ll be able to take a look but not anytime soon. [0] https://codereview.qt-project.org/c/qbs/qbs/+/524245 Ivan > 16 июня 2024 г., в 19:02, Jochen Becher via

Re: [Qbs] Problems with Xml.DomDocument through a module provider

place. > > I did try to replicate the issue with a small example, but the problem did > not show. So I can't give you anything. > > Nevertheless thanks, > Björn. > > Am 12.06.2024 um 10:41 schrieb Иван Комиссаров: >> Hello. >> >> The usual. Build Qbs in

Re: [Qbs] Problems with Xml.DomDocument through a module provider

Hello. The usual. Build Qbs in debug mode and run in the debugger, possibly with --jobs=1. Or attach to the running Qbs Session in QtC/vscode. Alternatively, if you code is public, provide a link to repo to reproduce and we can take a look. Ivan > 12 июня 2024 г., в 00:31, Björn Schäpers

Re: [Qbs] qbspkgconfig in qbs 2.3.1

an official way to use pkg-config > or will that be removed in a future version of qbs? > > Regards, Jochen > > > Am Sonntag, dem 02.06.2024 um 19:04 +0300 schrieb Иван Комиссаров: >> Hello! >> >> Short answer: >> >> Use qbsModuleProviders:

Re: [Qbs] qbspkgconfig in qbs 2.3.1

Hello! Short answer: Use qbsModuleProviders: ["Qt", "qbspkgconfig"] A longer answer: Setting qbsModuleProviders property disables «named» lookup for providers when Qbs tries to guess provider name from the module name (e.g. «Qt» from «Qt.core») . The "named" lookup exists for backward

Re: [Qbs] Setting properties for all products

You can put the other_project_buildconfig module in your projects search paths - that way it will override subproject module. Here QtC overrides Qbs buildconfig https://github.com/qt-creator/qt-creator/blob/master/qbs/modules/qbsbuildconfig/qbsbuildconfig.qbs However, this requires some

Re: [Qbs] qbs 2.3 released

It seems we forgot to write the file. Hopefully, the blog post will cover the details. Ivan > 9 апр. 2024 г., в 11:37, Leon Buckel написал(а): > > Where can we find the changlog? It doesn’t seem to be in the usual location. > >> On 8. Apr 2024, at 12:52 PM, Christian Kandeler via Qbs >>

Re: [Qbs] Code Generator with shared library dependencies

I think, this is the official way to do so. You are not supposed to run binaries from build dir. If Qbs does not ensure that files are installed prior to usage, this should be fixed. Ivan > 12 янв. 2024 г., в 13:10, Leon Buckel написал(а): > > In the past I’ve solved this problem by

[Qbs] Fwd: Accessing overloaded properties

Fwd to the mail list > > Hello! > > We typically discourage usage of the id properties (the only use-case are > Probes for the lack of other syntax) since Qbs is more «context» dependent > and we provide some «magic» variables such as «product», «importingProduct» > and so on. > > You can

Re: [Qbs] No functional TLS backend warning

Hi, we’ve ported Qbs to Qt6 a while ago - maybe it caused the issue? It might be that runtime deps in Brew formulae are not configured properly for Qt6. Ivan > 26 окт. 2023 г., в 17:33, Leon Buckel написал(а): > > Hi, > > With the current qbs version 2.1.2 (maybe earlier 2.x ones too)

Re: [Qbs] get path of qbs executable within Project/Product?

Hello, I don’t think this is possible. What’s your use-case? Ivan > 5 окт. 2023 г., в 18:02, Heiko Nardmann > написал(а): > >  > Hi together, > > is it possible to get the folder resp. path of the qbs executable from within > a Project or Product item? > > > > Kind regards, > > Heiko

Re: [Qbs] Windows 11 & (major|minor)-subsystem-version

Maybe the fix is trivial after all https://codereview.qt-project.org/c/qbs/qbs/+/471291 Can someone verify this on Win7? Ivan > 10 апр. 2023 г., в 23:31, Иван Комиссаров написал(а): > > Hello! > > Someone reported an issue a while ago and I created a ticked just yester

Re: [Qbs] Windows 11 & (major|minor)-subsystem-version

Hello! Someone reported an issue a while ago and I created a ticked just yesterday in order to to not forget it. https://bugreports.qt.io/projects/QBS/issues/QBS-1724 I suppose, the issue was introduced by this patch https://codereview.qt-project.org/c/qbs/qbs/+/459921 which was an attempt to

Re: [Qbs] Qbs 1.23.2 released

I think, both RPATH and RUNPATH should work. Do I understand correctly that you use self-built QtC and you built it using Qbs? In that case, that might be a bug in how QtC project overrides Qbs rpaths. Ivan > 26 окт. 2022 г., в 12:15, Карелин Павел написал(а): > > Christian, does it make

Re: [Qbs] Language Proposal: A generic `Item{}` for classifying bindable objects

> Why would the item pool use `std::vector m_items;` instead of a QList > ( Or QVector ) ? I imagine it was a performance consideration, but it always > puzzles me to see stdlib in most qt code. There were plans to migrate to pure stdlib and some parts of the code have been ported already

Re: [Qbs] Language Proposal: A generic `Item{}` for classifying bindable objects.

+1 here. Maybe Object (or Gadget/smth else since JS has “object” type already) as it is not a generic Item used in other items would be better. Otoh if we choose the Item { id/name: foo } syntax, Item would be fine. Ivan > Perhaps also: > > property MyItem prop

Re: [Qbs] Language Proposal: A generic `Item{}` for classifying bindable objects.

This seems like a nice idea, I was wondering the same thing myself if can we enforce the “schema” on object properties. Иван Комиссаров > 2 сент. 2022 г., в 05:14, hug-animals via Qbs написал(а): > >  > Greetings. I've been using QBS for quite awhile and have been expanding its

Re: [Qbs] Dynamic generation of the resource file

You can just do outputArtifacts: { return [{ fileTags: input.fileTags.contains("encription") ? ["encript-resource"] : ["encript-resource2"], filePath: FileInfo.joinPaths(project.buildDirectory, "encription", input.baseName + ".enc") }]; } Ivan > 8 окт. 2021 г., в

[Qbs] 1.21 branch created

Hello, We branched off Qbs 1.21 today. Scheduled release date for version 1.21.0 is end of November (together with Qt Creator 6.0) [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] Dynamic generation of the resource file

In Qbs, you can set properties for individual files using Group item: Qt.core.resourceFileBaseName: "trigrams" Group { fileTagsFilter: [«qrc_input1»] // trigrams-map in your example fileTags: ["qt.core.resource_data»] Qt.core.resourcePrefix: «prefix1" } Group { fileTagsFilter:

Re: [Qbs] IRC: Freenode -> Libera.Chat ?

Hello, most of the community moved to the Discord server https://discord.gg/5mFfku5y - looks like IRC was not very popular, so there were no plans to move it to Libera.Chat. Ivan > 13 авг. 2021 г., в 15:28, Heiko Nardmann > написал(а): > > Hi together, > > is

Re: [Qbs] Library- and Include-Probe for msys GCC on the example of the protobuf module

n thus when compiling for 32 > bit the wrong libraries are picked up. > > Regards, > Björn. > > Am 21.07.2021 um 07:16 schrieb Иван Комиссаров: >> You will get more feedback once I’ll be back from vacation ^^ >> >> Your assumption that it should work out if the

[Qbs] 1.20 branch created

Hello, We branched off Qbs 1.20 today. Scheduled release date for version 1.20.0 is mid of August (together with Qt Creator 5.0) [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] Library- and Include-Probe for msys GCC on the example of the protobuf module

You will get more feedback once I’ll be back from vacation ^^ Your assumption that it should work out if the box is correct. However, it should not use probes, but pkg-config instead (I assume, msys provides correct .pc files). I am currently working on the feature to implement this .

Re: [Qbs] Settings module properties globally in root qbs project?!

Hello! The module approach you’ve suggested is probably the best way of doing this. Requires some additional work, unfortunately. I’d also suggest adding helper items that inherit base items provided by Qbs, such as CppApplication, DynamicLibrary, etc - in that case, you can use these items

Re: [Qbs] Build and run a AuxiliaryApplication before build a MainApplication

Hello!. In the second variant - do you need Group { fileTagsFilter: "application" fileTags: "trigrams-generator" } ? The product has that type already I’d say both variants are OK and there’s no preference. > 1 марта 2021 г., в 21:43, Карелин Павел написал(а): > >

Re: [Qbs] (no subject)

Hello, Dan! Any chance you publish your solution? I am interested in wasm support as well Ivan > > The goal is to get qbs projects compiled to WebAssembly using the emscripten > toolchain (and Qt WebAssembly). As for upstreaming: I have managed to come up > with a working but hacky solution

Re: [Qbs] Qt6 support

Did you install this module using the MaintenanceTool? It doesn’t get installed by default Ivan > 4 дек. 2020 г., в 10:44, Maximilian Hrabowski > написал(а): > > Hi all, > > Is Qt6 already supported by qbs?If so which version is required? Doing a > naive “Depends { name: “Qt.core5compat” }

Re: [Qbs] AutotestRunner in QtCreator

I personally use the «tests» tab (on the bottom panel) in QtCreator - it allows to run all tests (similar to building AutotestRunner) as well as running tests in single file. Similar to AutotestRunner, QtC recognizes products with the tag «autotest» as tests Ivan > 28 нояб. 2020 г., в 20:44,

Re: [Qbs] Why was protobuf.outputDir removed

nd > install the static library for use in the consuming application. > I would rather append the proto files to an products source files If there is > a (non hacky) way to it (with conan), > > Kai > > > > Am Di., 15. Sept. 2020 um 09:41 Uhr schrieb Иван Комиссаров &g

Re: [Qbs] Why was protobuf.outputDir removed

This won’t work in case of the protoc - the generated tree does not always match the tree in the source and it depends on the order of the -I flags passed to protoc. Ivan > 15 сент. 2020 г., в 10:35, Oswald Buddenhagen > написал(а): > > On Tue, Sep 15, 2020 at 09:00:50AM +0200, Kai Dohmen

Re: [Qbs] Why was protobuf.outputDir removed

Hello, Kai First of all, the property was not removed but was made «private» and is now called _outputDir. You can still override it or read it. The reason why it was removed is that I didn’t see valid use-cases for that. For example, to export include paths you should do something like that:

Re: [Qbs] Applying cxxFlags to certain files

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", } > 10

Re: [Qbs] building android aab package help

s.profiles: ["a", "b"] > files: [ "main.cpp" > ] > } > I get this error: Result of expression 'qbs.targetOS' [undefined] is not an > object. In NativeBinary.qbs > > Am I missing something here? The targetOS property is not set when the >

Re: [Qbs] building android aab package help

Hello, Raphael! I’ve seen your new patch and it looks really interesting. So, for now, you have 2 separate patches for the AAB support, right? [0] https://codereview.qt-project.org/c/qbs/qbs/+/303358 [1]

Re: [Qbs] isystem with clang

Hello, you can find the generated modules in the build directory. $ pwd /Users/abbapoh/Programming/qt5/alien/qbs/examples/helloworld-qt $ qbs Build graph does not yet exist for configuration 'default'. Starting from scratch. Resolving project for configuration default Setting up Qt at

Re: [Qbs] Binary stripping

It looks like strip is only used in android and Darwin toolchains Maybe, it’s makes sense to add a rule that strips binary in the release mode as well Ivan > 9 апр. 2020 г., в 21:49, Alberto Mardegan > написал(а): > > Hi all! > Sorry for spamming the list :-) > I noticed that binaries

Re: [Qbs] Changing the default value of consoleApplication

I don’t mind adding QtWidgetsApplication item Ivan > 8 апр. 2020 г., в 22:33, Alberto Mardegan > написал(а): > > On 08/04/20 13:21, Oswald Buddenhagen wrote: >> i'm not convinced. qt.widgets and qt.quick could reasonably do that, but >> gui is perfectly suitable for console-only apps. > >

Re: [Qbs] Q_INIT_RESOURCE on Windows

From the Qt documentation: "The Q_INIT_RESOURCE() macro is necessary on some platforms for resources stored in a static library.» This is a workaround to tell the linker not to throw resources away when linking a static library. It is not required when using a dynamic library as far as I

Re: [Qbs] Changing the default value of consoleApplication

consoleApplication is set to undefined by default which means «use the default compiler value» which seems to be «console» on Windows But I agree it makes sense to override it in «gui» application. Maybe it also make sense to have this property set to true in debug build. Feel free to submit a

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

There’s also no such property, there’s cpp.compilerName. Are you sure you’re not using «qbs.compilerName» in your project somewhere? Ivan > 27 марта 2020 г., в 18:58, Иван Комиссаров написал(а): > > Hello, what version of QtC / qbs / LLVM are you using? > > Ivan > >>

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

Hello, what version of QtC / qbs / LLVM are you using? Ivan > 27 марта 2020 г., в 18:20, > написал(а): > > 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

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

Ah, never mind, you should not since you’re not inheriting the project.profile > 20 марта 2020 г., в 19:53, Иван Комиссаров написал(а): > > This looks like a bug - this property is not set in Profile item context. > > Shouldn't you also set qbs.architecture to «x86_64» in

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

This looks like a bug - this property is not set in Profile item context. Shouldn't you also set qbs.architecture to «x86_64» in the hostProfile ? > 20 марта 2020 г., в 17:01, Leon Buckel написал(а): > > Here's a small test project I set up that has the issue. Note that I have to > set

Re: [Qbs] Using QBS with an nonexistent $HOME

That’s a very interesting article! However, I’ve noticed a strange thing. The doc [0] says that CPPFLAGS variable is the "Options for the C preprocessor» which means this variable should map to cpp.cppFlags, not to cpp.commonCompilerFlags This also means that duplicated values passed as

Re: [Qbs] Using QBS with an nonexistent $HOME

Hello! Have you tried the --settings-dir option to some existent (maybe temporary) directory? I can’t test it as I don’t have Qbs 1.10, but it should help. Ivan > 29 февр. 2020 г., в 09:05, Alberto Mardegan > написал(а): > > Hi there! > I'm trying to build a Debian/Ubuntu package of a QBS

Re: [Qbs] (no subject)

ed after any Product > dependencies, any libraries specified directly in cpp.dynamicLibraries (as an > experiment, we normally use Depends) come before Module dependencies but > after any Product dependencies, any cpp,linkerFlags (tried as a last resort) > go the end of the linker's arguments s

Re: [Qbs] (no subject)

Hello, Dan! It’s very sad to hear that QtC crashes for you. There’s one known issue in qbs which will be fixed with QtC 4.11 release. Can you please try release candidate if it works better or not? https://download.qt.io/development_releases/qtcreator/4.11/4.11.0-rc1/ If release candidate

Re: [Qbs] (no subject)

It’s worth mentioning, that compiling with verbose flag can give some insight on what libraries/options clang-cl passes to the linker: clang-cl -v -fsanitize=address main.cpp Иван Комиссаров > 28 нояб. 2019 г., в 17:23, Иван Комиссаров написал(а): > > I did a small research and

Re: [Qbs] (no subject)

g-cl uses), maybe it’s worth using clang-cl for linking... or just add support for the usual clang with msvc ABI (I have plans for that for 1.16) Иван Комиссаров > 28 нояб. 2019 г., в 15:53, Christian Kandeler > написал(а): > > On Thu, 28 Nov 2019 18:58:54 +0500 > Dan Pat wrote:

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

I guess, documentation is updated manually as a part of the release process (which did not happen yet AFAIK). Christian should know better, he is the maintainer:) I hope that some day when we will have a proper CI for Qbs, we can update doc on a daily basis Иван Комиссаров > 9 авг. 2019 г.

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

Yeah, blog post would be nice. I'd wait for the product graph feature though so we could compare cmake buildgraph and Qbs build graphs as well. Иван Комиссаров > 23 июля 2019 г., в 4:49, Vincent Hui написал(а): > > Hi Chris, > > Thank you for your benchmark. > > W

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

You can make two top-level projects, something like «my lib-standalone.qbs» which includes «mylib.qbs» and setups the properties to enable tests/whatever. All what you don’t want for users is disabled by default. > 20 июля 2019 г., в 6:27, Vincent Hui написал(а): > > Hi Christian, > > Thank

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

Never used clang-format before, but +1. I don't want waste my time searching for those long lines too=) Иван Комиссаров > 8 июля 2019 г., в 11:39, Christian Gagneraud написал(а): > > Hi there, > > I would like to propose to add a clang-format config file to qbs repo. >

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

ly. > > I know I can add all cpp files automatically by using Group. However, I don't > know how to build 2 executables without hardcode 2 CppApplication. > > Thank you again, > Vincent > > > On Sat, 6 Jul 2019 at 23:15, Иван Комиссаров <mailto:abba...@gmail.com>

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

https://codereview.qt-project.org/c/qbs/qbs/+/267333 > 6 июля 2019 г., в 15:51, Иван Комиссаров написал(а): > > Ivan. ___ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs

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

Yes, Qbs doc is a bit incomplete and contains some confusing and misleading examples. I even failed to answer your question myself. Well, I understood the reason correctly (there’s no dependent product), but failed to provide a working example in reasonable time. Feel free to create tickets

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

useFeature: false; } // does nothing, all checks are already done } What worse, this won’t work at all: Product { Depends { name: "mymodule"; } Group { files: «file»; mymodule.useFeature: true; } // ooops } > 10 июня 2019 г., в 20:45, Иван Комиссаров написал(а): >

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

Yes, I’d like to have some syntax sugar here. But 2-liner is probably OK too. > 10 июня 2019 г., в 20:32, Richard Weickelt написал(а): > > Ivan, > > Do you actually want to achieve this? > >Module { >property bool useFeature: false > >Probes.BinaryProbe { >

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

I’d like to do something like this: Module { Parameter { property bool useFeature: false } Probes.BinaryProbe { condition: useFeature } } So I’d be able to write: Depends { name: "mymodule"; useFeature: true; } ___ Qbs

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

any difference so I understand that change is annoying (I was the one who could not run tests on macOS) But the doc should be updated... Иван Комиссаров 20 мая 2019 г., в 9:01, Richard Weickelt написал(а): >> Oh yeah, it has been an unsatisfying surprise that default installation >

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

isited, switching to more suitable containers (QVector or std::vector/std::deque). > 16 мая 2019 г., в 0:00, Christian Gagneraud написал(а): > > On Thu, 16 May 2019 at 09:32, Иван Комиссаров wrote: >>> 15 мая 2019 г., в 19:50, André Pönitz написал(а): >>> >>> G

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

+1 from me, hidden detaches are evil =) > 15 мая 2019 г., в 19:50, André Pönitz написал(а): > > Getting rid of implicitly shared containers should be a rather obvious move > when "performance" is part of any "final picture", coherent or not. > > Andre' >

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

Interesting. Any idea why Qbs is so slow with ccache? Иван Комиссаров > 15 мая 2019 г., в 17:29, Orgad Shaneh написал(а): > > du -shc build-qtc-qbs > 15G build-qtc-qbs > 15G total > du -shc build-qtc-cmake > 4.0Gbuild-qtc-cmake > 4.0Gtotal > >

Re: [Qbs] External Dependencies

Application should not be aware about this property at all, this is a hardcoded _module_ property (similar to priority), this is just a way to modify the way how modules are loaded. > 14 мая 2019 г., в 23:54, NIkolai Marchenko > написал(а): > > Unfortunately I still don't see how or where

Re: [Qbs] External Dependencies

мая 2019 г., в 22:44, NIkolai Marchenko > написал(а): > > > by adding property bool recover to the Module which tells Qbs to try > > loading next module in a chain > Probably needs a code example of a proposed solution. What is a "chain" like > in this case? > &

Re: [Qbs] External Dependencies

> On Tue, May 14, 2019 at 11:09 PM NIkolai Marchenko > wrote: > Wouldn't it be more reasonable to implement something like OptionalDepends > where you could just list all possible dependencies in the order in which it > should be loaded? > This doesn’t solve

[Qbs] External Dependencies

I would like to discuss the way how external dependencies should be searched by qbs. While implementing support for the protobuf I found that there several place where a generic c++ can come from. 1. It can be detected via pkg-config 2. It can be detected using probes 3. Other pkg-config-like

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

but can be bootstrapped (like qfile) if needed. But what about QtScript's dependency on the QtCore/other libs? My point was that it may depend on the qtlibs more than Qbs does and the biggest job is there, not in Qbs core. Иван Комиссаров > 14 мая 2019 г., в 14:08, Christian Gagneraud написа

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

irst place? Except for GUI and script module, I don't think there's a lot of Qt stuff. Иван Комиссаров > 14 мая 2019 г., в 12:33, Richard Weickelt написал(а): > > >>> However, will this help to get new developers? Right now, there are not that >>> many contributors.

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

. Иван Комиссаров > 14 мая 2019 г., в 11:44, Denis Shienkov написал(а): > > 14.05.2019 12:32, Tobias Hunger пишет: >> There is no find_package script for qbs that we can just use. >> >> Don't panic, it will be there. > > In that case, you need to add possib

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

+1 However, will this help to get new developers? Right now, there are not that many contributors. Иван Комиссаров > 14 мая 2019 г., в 11:18, Карелин Павел написал(а): > > +1 > > 14.05.2019 11:54, Алексей Скородумов пишет: >> Hi, >> >> Is it hard to

Re: [Qbs] Any novice tickets

upport for «releaseWithDebugInfo»? This is kinda common usecase. > 30 апр. 2019 г., в 9:59, Christian Kandeler > написал(а): > > 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 &g

Re: [Qbs] Any novice tickets

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? > 13 февр. 2019 г., в 16:10, Иван Комиссаров написал(а): > > The same as we discussed ea

Re: [Qbs] qbs 1.13 released

Done: https://bugreports.qt.io/browse/QTCREATORBUG-22355 > 23 апр. 2019 г., в 13:03, Christian Kandeler > написал(а): > > On Tue, 23 Apr 2019 13:29:57 +0300 > Иван Комиссаров wrote: > >> I’ve noticed, that cpp.minimumOsxVersion was renamed to >> cpp.minimumMaco

Re: [Qbs] qbs 1.13 released

Thanks for the job! 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 cpp.minimumMacosVersion: «10.14» or higher. Qbs

Re: [Qbs] Unexpected behavior of MSVC generator

Anyway, I still don’t see the problem - QBS can emulate the build process for that an IDE normally does, placing the artifacts in the exact places where IDE would place them. At least, that’s how (unfinished) Xcode generator works - it builds the app to a generic folder and then creates

Re: [Qbs] Unexpected behavior of MSVC generator

CMake)? It is a main dilemma! :) > It’s open source now. If personally you need this feature, contribute it. > BR, > > Denis > > > > 16.02.2019 20:14, Иван Комиссаров пишет: >> I can comment. If you want a real generator, you should use cmake=) >> >> Bein

Re: [Qbs] Unexpected behavior of MSVC generator

I can comment. If you want a real generator, you should use cmake=) Being serious, it is not a recursion, it is a proxy - solution is the proxy for the IDE to call the build tool (which is QBS). Creating a «proper» solution that invokes compilers directly is a very challenging task… Imagine you

Re: [Qbs] Any novice tickets

k occurred. Иван Комиссаров > 13 февр. 2019 г., в 15:59, Christian Kandeler > написал(а): > > 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 m

Re: [Qbs] Any novice tickets

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)? Иван Комиссаров > 12 дек. 2018 г., в 10:24, Christian Kandeler > написал(а): > > On Tue, 11 Dec 2

Re: [Qbs] Any novice tickets

is loaded, with the highest priority and if it fails, others are not loaded. Maybe it’s worth trying to load all modules in a chain one after the other? > 11 дек. 2018 г., в 10:37, Christian Kandeler > написал(а): > > On Mon, 10 Dec 2018 22:50:14 +0100 > Иван Комиссаров wrote: &g

[Qbs] Mysterious config: parameter

Perhaps, I am blind, but I can’t find any mentions in documentation. What’s this is used for? Does this parameter only specifies the output folder where QBS will build sources? Or it has some other usages I am not aware of? ___ Qbs mailing list

Re: [Qbs] Future of Qbs

Richard, thank you for writing this post. I was thinking of doing it myself, but I never was good at writing long letters=) Anyway, I would like to suggest that people who interested in QBS start contributing in it now. We have half a year to get familiar with the codebase while Christian

Re: [Qbs] Any novice tickets

Christian Kandeler : > On Thu, 9 Aug 2018 03:53:50 +0300 > Иван Комиссаров wrote: > > > Im a bit stuck with protobuf module. I’m trying to make the module > behave different for different languages, i.e. generate .cc files for cpp > project, java for java project and so on. >

Re: [Qbs] Any novice tickets

Properties but it seems my condition function is not called at all (at least, throwing in it makes no result) > 6 авг. 2018 г., в 16:39, Иван Комиссаров написал(а): > > https://bugreports.qt.io/browse/QBS-563 > <https://bugreports.qt.io/browse/QBS-563> (Add support for Google

Re: [Qbs] Any novice tickets

I don’t think it’s too hackish, but there may be some corner cases that will require proper documentation. What comes to my mind, how you suppose to treat positionalArguments() of the top-level parser? Should it be empty/contain all subparser arguments/what’s left after subparsing? Anyway, I

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

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 .lib file (is that a QBS bug, btw?). So you can try checking if the

Re: [Qbs] Any novice tickets

use QCommandLineParser at the moment? 2018-08-06 11:28 GMT+03:00 Christian Kandeler : > On Mon, 6 Aug 2018 11:21:28 +0300 > Иван Комиссаров wrote: > > Hi Ivan, > > > Hello, I want to participate in QBS development, > > That's great to hear. > > > but I

Re: [Qbs] Multiple install paths

Anyone?:( Иван Комиссаров > 16 мая 2018 г., в 12:44, Иван Комиссаров <abba...@gmail.com> написал(а): > > Hello, is it posssible to install same product to different folders using one > group? > For example, i have 2 Application Bundles on mac and a plugin that should be

  1   2   >