Re: [Qbs] External Dependencies

And while we are on the subject of finding libs. Is it possible to somehow indicate that a library you are trying to link isn't compatible with the compiler? Somethe _other_ than "unresolved external" error that can indicate anything from lib not being where you want it to be, a mistype in the

Re: [Qbs] External Dependencies

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? On Tue, May 14, 2019 at 9:26 PM Иван Комиссаров wrote: > I would like to discuss the way how external dependencies should be

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

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

On Tue, May 14, 2019 at 08:42:50PM +0200, Richard Weickelt wrote: > 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

[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] 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

+1 14.05.2019 11:54, Алексей Скородумов пишет: Hi, Is it hard to make "donate" button on "QBS site" as a part of "transition to community"? I can't contribute time right now, but would like to support the project. -- Best regards, Aleksei Skorodumov

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

We can see Qbs development is active. https://github.com/qbs/qbs/commits/master?before=ca4987ae21f3cb30fde699448abc213b37b90214+35 Therefore I don't think it is dead. On Tue, 14 May 2019 at 16:09, Pier Luigi Fiorini < pierluigi.fior...@gmail.com> wrote: > Il giorno mar 14 mag 2019 alle ore

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

tir. 14. mai 2019 kl. 09:45 skrev Vincent Hui : > Hi, > > Qt Creator was ported to CMake > . It is interesting to > compare build times of Qt Creator with CMake and Qbs. > > Did anyone benchmark qbs against cmake? > > I'd like to know if Qt Creator

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

tir. 14. mai 2019 kl. 10:12 skrev Vincent Hui : > We can see Qbs development is active. > https://github.com/qbs/qbs/commits/master?before=ca4987ae21f3cb30fde699448abc213b37b90214+35 > Therefore I don't think it is dead. > > Sure I agree, however if the mindset elsewhere is that "Qbs is dead",

[Qbs] Donation to QBS developers/maintainers/contributes

Hi, Is it hard to make "donate" button on "QBS site" as a part of "transition to community"? I can't contribute time right now, but would like to support the project. -- Best regards, Aleksei Skorodumov ___ Qbs mailing list

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

Hi, Qt Creator was ported to CMake . It is interesting to compare build times of Qt Creator with CMake and Qbs. Did anyone benchmark qbs against cmake? ___ Qbs mailing list Qbs@qt-project.org

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

Il giorno mar 14 mag 2019 alle ore 10:04 Ola Røer Thorsen < o...@silentwings.no> ha scritto: > > tir. 14. mai 2019 kl. 09:45 skrev Vincent Hui : > >> Hi, >> >> Qt Creator was ported to CMake >> . It is interesting to >> compare build times of Qt

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

On Tue, 14 May 2019 at 20:58, Tobias Hunger wrote: > > On Tue, 2019-05-14 at 10:04 +0200, Ola Røer Thorsen wrote: > > I'd like to know if Qt Creator will phase out Qbs support completely, > > seeing the comments and summary in that commit ("Qbs is dead"). Would be > > really bad for at least my

Re: [Qbs] External Dependencies

> 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? On Tue, May 14, 2019 at 11:32 PM Иван Комиссаров wrote: > On Tue, May 14, 2019 at 11:09 PM

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

Let me use Cpp module as example. We have macos-gcc.qbs: DarwinGCC { priority: 1 condition: qbs.targetOS.contains('macos') && qbs.toolchain && qbs.toolchain.contains('gcc') } And we have UnixGCC.qbs: GenericGCC { priority: -50 condition: qbs.toolchain &&

Re: [Qbs] External Dependencies

Unfortunately I still don't see how or where the chain of dependencies on DarwinGCC and GenericGCC is being set up. Will it be in zlib module ? I am trying to understand how will the application know what is the "recovery" option and when to consider all recovery paths exhausted and can't bc I do

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

On Tue, 2019-05-14 at 21:06 +1200, Christian Gagneraud wrote: > From the change description: > All plugins have been converted to CMake, with the following exceptions: > - qbsprojectmanager > > Any reason why? There is no find_package script for qbs that we can just use. Don't panic, it will

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

I don't know how does the cmake scripts work, but it should not require building qbs with cmake However, it might be a good idea to retire qmake for qbs as well to reduce Qt dependencies. But it seems quite a huge job since qbs build is quite complicated and supports lots of configurations.

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

On 5/14/19 10:57 AM, Tobias Hunger wrote: > The challenge will be Qt 6: Creator will use Qt 6 ASAP and since qbs is linked > into Creator, that will also need to be ported to Qt 6 to stay feasible. ...which shouldn't pose a challenge at all given that Qt 6 is to keep source incompatible changes

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] Donation to QBS developers/maintainers/contributes

On Tue, 14 May 2019 at 21:46, Иван Комиссаров wrote: > > +1 > > 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

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

If I am right, one urgent task is to remove the dependency of Qt Script. Vincent On Tue, 14 May 2019 at 17:51, Christian Gagneraud wrote: > On Tue, 14 May 2019 at 21:46, Иван Комиссаров wrote: > > > > +1 > > > > However, will this help to get new developers? Right now, there are not > that

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

On Tue, 14 May 2019 at 22:02, Joerg Bornemann wrote: > > On 5/14/19 10:57 AM, Tobias Hunger wrote: > > > The challenge will be Qt 6: Creator will use Qt 6 ASAP and since qbs is > > linked > > into Creator, that will also need to be ported to Qt 6 to stay feasible. > > ...which shouldn't pose a

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

On 5/14/19 12:04 PM, Christian Gagneraud wrote: > On Tue, 14 May 2019 at 22:02, Joerg Bornemann wrote: >> >> On 5/14/19 10:57 AM, Tobias Hunger wrote: >> >>> The challenge will be Qt 6: Creator will use Qt 6 ASAP and since qbs is >>> linked >>> into Creator, that will also need to be ported to

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

On Tue, 14 May 2019 at 22:51, Иван Комиссаров wrote: > > I wonder how hard is to implement pure c++ "declarative" library. Afaik, > qtdeclarative originally used v8 JavaScript engine which got replaced with > Qt-ish engine to avoid conversions to/from Qt types. Maybe, it's possible to > go the

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

On Tue, 14 May 2019 at 23:11, Christian Gagneraud wrote: > > On Tue, 14 May 2019 at 22:51, Иван Комиссаров wrote: > > > > I wonder how hard is to implement pure c++ "declarative" library. Afaik, > > qtdeclarative originally used v8 JavaScript engine which got replaced with > > Qt-ish engine to

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 make "donate" button on "QBS site" as a

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

I wonder how hard is to implement pure c++ "declarative" library. Afaik, qtdeclarative originally used v8 JavaScript engine which got replaced with Qt-ish engine to avoid conversions to/from Qt types. Maybe, it's possible to go the opposite direction and remove Qt dependency in the first place?

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

Another issue is that Qt Creator will not ship with Qt Script if Qt Script will be dropped in Qt 6. Don't know whether Qt Creator team is willing to ship a forked Qt Script library. Vincent On Tue, 14 May 2019 at 19:51, Christian Gagneraud wrote: > On Tue, 14 May 2019 at 23:10, Joerg

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

Good information, thanks. Qbs itself has a huge dependency on a QtCore, but some stuff is present in standard library and can be easily changed to that (we still have enourmous amount of places where qlist is used instead of a qvector/std::vector and used inefficient); others are trickier but