Happy New Year!
I havbe a question about qbs syntax. My qbs files look like this:
MyProject.qbs:
Project {
property string installDir: { throw "installDir must be set" }
}
AProject.qbs:
MyProject {
id: solution
installDir: "myfolder"
MyProject {
installDir: soluti
Thank you, I tried using parent.installDir and it works. Maybe you want
to document this property in the qbs manual under "Special Property
Values"?
Regards, Jochen
Am Montag, dem 08.01.2024 um 12:52 +0100 schrieb Christian Kandeler via
Qbs:
> On 1/8/24 12:37, Jochen Becher
Hi,
I tried to build a project for the first time after a couple of years
and qbs versions. I now use QtCreator 13.0.1 with qbs 2.3.1.
The product is a StaticLibrary and has dependencies
Depends { name: "Qt", submodules: ["core" , "gui"] }
Depends { name: "taglib" }
In the past "taglib" has bee
ing providers explicitly in the new node.
>
> Ivan
>
> > 1 июня 2024 г., в 13:21, Jochen Becher via Qbs
> > написал(а):
> >
> > Hi,
> >
> > I tried to build a project for the first time after a couple of
> > years
> > and qbs versions. I n
from the module name
> (e.g. «Qt» from «Qt.core») .
>
> The "named" lookup exists for backward compatibility and we advise
> listing providers explicitly in the new node.
>
> Ivan
>
> > 1 июня 2024 г., в 13:21, Jochen Becher via Qbs
> > написал(а):
>
Hi,
are there any plans to support WebAssembly with qbs soon? I would like
to build some software that are using qbs for wasm with emsdk and
QtCreator. It would be great if qbs would provide support like cmake
and qmake do.
Regards, Jochen
___
Qbs mail
gt; 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 Qbs > project.org> написал(а):
> >
> > Hi,
> >
> > are there any p
Qbs is now over 10 years old. We are using it with thousands of qbs
files. Still having breaking changes like this is a nightmare: We have
to go through formal release procedures for more than hundred
components, update binary deployments of these, integrate changes into
hundreds of streams, updat
w setting to generate the clangdb after each resolve
automatically.
Regards, Jochen
Am Freitag, dem 04.07.2025 um 11:30 +0300 schrieb Иван Комиссаров:
> Hello!
>
> > 2 июля 2025 г., в 19:38, Jochen Becher via Qbs
> > написал(а):
> >
> > HI,
> >
> >
Hi,
I get a "Using list properties as fallback values is deprecated" error
from the following code. What is the suggested way to do this?
property stringList additionalSystemLibs : []
Properties {
condition: qbs.targetOS.contains("windows")
additionalSystemLibs: [ "versio
be gone in 3.0.
>
>
> Christian
>
>
> Confidential
> ________________
> From: Qbs on behalf of Jochen Becher via
> Qbs
> Sent: Friday, July 4, 2025 4:55 PM
> To: qbs@qt-project.org
> Subject: [Qbs] Deprecation error message from qbs 2.6.1
>
&g
Done, see QBS-1845.
Regards, Jochen
Am Donnerstag, dem 10.07.2025 um 16:59 +0200 schrieb Christian Kandeler
via Qbs:
> On 7/10/25 1:16 PM, Richard Weickelt wrote:
> > > Qbs flattens nested and merges referenced project items during
> > > the
> > evaluation process.
>
> That's news to me ;)
>
Jochen Becher via
Qbs:
>
> I was able to create a small (not necessary minimal) example. Please
> see the attached zip file.
>
> It is much more complex than my original minimal code. The main
> aspect
> seems to me a change in qbs 3.0.0:
>
> SubProject { filePath: &quo
I was able to create a small (not necessary minimal) example. Please
see the attached zip file.
It is much more complex than my original minimal code. The main aspect
seems to me a change in qbs 3.0.0:
SubProject { filePath: "MyApp.qbs" }
seems to set parent differently than in the past. If I i
+0200 schrieb Jochen Becher via
Qbs:
>
> One more note: in the minimal example I can replace the SubProject
> with
> a references property and it works.
>
> Unfortunately, this is not a good work-around for me as I had to
> change
> hundreds of test frames in our code
I am currently also trying to get it reproduced in a small example but
cannot yet. Unfortunately, the real code is far too complex to discuss
it here. I will try to get it reduced to something small enough.
Am Donnerstag, dem 10.07.2025 um 11:27 +0200 schrieb Christian Kandeler
via Qbs:
> On 7/1
Am Donnerstag, dem 10.07.2025 um 11:08 +0200 schrieb Christian Kandeler
via Qbs:
> On 7/10/25 11:03 AM, Jochen Becher via Qbs wrote:
> > Project {
> > property bool mySetting: true
> >
> > Project {
> > property bool mySettings: parent.mySetti
Hi,
I have the following code:
Project {
property bool mySetting: true
Project {
property bool mySettings: parent.mySetting ?
parent.mySetting : false
}
}
In the past this worked but with qbs 3.0.0 is is no longer accepted.
How can I access a property of
HI,
I am currently working on some improvements of the VSCode extension
vscode-qbs. I would like to add some support for clangd: whenever a
project is resolved, it should also generate the clangdb
(compile_commands.json). With some configuration of the clang extension
it is possible to have full a
duplicates from the array and the
warnings are gone.
Is that the correct solution? Should I open an issue for this?
Regards, Jochen
Am Dienstag, dem 22.07.2025 um 22:17 +0200 schrieb Jochen Becher via Qbs:
> Hi,
>
> With qbs 3.0.0 I get hundred of thousands (litterally!) warnings
Hi,
With qbs 3.0.0 I get hundred of thousands (litterally!) warnings from qbs
saying that some Qt types are defined twice:
Warning: qabstractitemmodel.h:258: Multiple C++ types called QAbstractItemModel
found!
(other occurrence in : qabstractitemmodel.h : 258 )
This violates the One Definitio
Am Donnerstag, dem 24.07.2025 um 14:15 +0200 schrieb Christian Kandeler via Qbs:
> On 7/22/25 10:17 PM, Jochen Becher via Qbs wrote:
> > With qbs 3.0.0 I get hundred of thousands (litterally!) warnings from qbs
> > saying that some Qt types are defined twice:
&
22 matches
Mail list logo
