Hi,
I try to use self compiled Qbs and QtCreator on Windows (MinGW not MSVC, no msys
or cygwin). I'm using a separate Qbs checkout, not the one delivered with QtCreator.
My first problem was while compiling QtCreator the linker looked for
libqbscore.a, but the file is named libqbscore1.a.
Hi,
I'm trying to build a repository for multiple libraries and applications, where
every product is located in an own submodule. Right now I'm at this point:
root/
- all.qbs
- libs/
- libs.qbs
- up.qbs
- lib1/
- lib1.qbs
- lib2/
- lib2.qbs
Lib2 needs lib1. The file contents
Am 03.01.2019 um 22:36 schrieb Silvano Cerza:
I think it should be enough to delete up.qbs and remove references:
["../up.qbs"] from lib2.qbs.
Obviously if you export cpp.includePaths you must export a dependency to cpp.
Il giorno gio 3 gen 2019 alle ore 22:17 Björn Schäpers <ma
Am 04.01.2019 um 10:21 schrieb Christian Kandeler:
On Thu, 3 Jan 2019 22:14:09 +0100
Björn Schäpers wrote:
I'm trying to build a repository for multiple libraries and applications, where
every product is located in an own submodule. Right now I'm at this point:
root/
- all.qbs
- libs
Hi,
I'm trying to incorporate Howard Hinnant's date library and he states
"mingw users: -lpthread and -lole32 are required"
So I tried
StaticLibrary {
files: ["date/include/date/*.h", "date/src/*.cpp"]
name: "date"
Depends { name: "cpp" }
Am 22.02.2020 um 09:56 schrieb Richard Weickelt:
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
Hi,
I have a lot of products which have spaces in their name. Until now everything
was fine, but now I want to access the property of one of my dependencies. How
to do that with a space in the name, or should spaces in the name be banned
completely?
Works:
DynamicLibrary {
name:
Am 26.06.2020 um 13:42 schrieb Christian Kandeler:
On Fri, 26 Jun 2020 13:14:11 +0200
Björn Schäpers wrote:
DynamicLibrary {
name: "FooBar"
}
CppApplication {
Depends { name: "cpp" }
Depends { name: "FooBar" }
cpp.defines = ["F
Hi,
I've added a AutotestRunner to my Project, but it does not show up in the
Creator, I think this is because it does not create a binary, right?
I've not looked into the code, but how feasible would it be to give the Creator
a fake executable to run the tests?
Another idea I had, but not
roduct X", if it's not a run target.
-Original Message-
From: "Björn Schäpers"
To: qbs@qt-project.org
Sent: Tue, 24 Nov 2020 9:21
Subject: [Qbs] AutotestRunner in QtCreator
Hi,
I've added a AutotestRunner to my Project, but it does not show up in the
Creator, I think this is
Am 24.11.2020 um 14:19 schrieb Richard Weickelt:
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,
Hi,
I'm developing on Windows and have a 64 Bit Qt in my path, but because the
linker in 64 Bit mode is much slower than its 32 Bit counterpart I often develop
in 32 Bit. If I run the programs directly from the Creator everything is fine.
If I click build for the AutotestRunner it seems that
Am 29.11.2020 um 12:37 schrieb Иван Комиссаров:
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
Hi,
I've tried to create a product which sets compiler warnings (because
cpp.warningLevel: "all" is not enough), and I want to be able to opt in some
more warnings. I found "Parameter" but I have no idea how to use it.
My product:
Product {
name: "All Warnings"
property
Am 01.12.2020 um 11:04 schrieb Christian Kandeler:
On 12/1/20 8:48 AM, Björn Schäpers wrote:
I've tried to create a product which sets compiler warnings (because
cpp.warningLevel: "all" is not enough), and I want to be able to opt in some
more warnings. I found "Parameter"
Am 01.12.2020 um 10:50 schrieb Christian Kandeler:
On 12/1/20 8:59 AM, Björn Schäpers wrote:
I'm developing on Windows and have a 64 Bit Qt in my path, but because
the linker in 64 Bit mode is much slower than its 32 Bit counterpart I
often develop in 32 Bit. If I run the programs directly
Am 15.11.2021 um 09:18 schrieb Christian Kandeler:
On 11/12/21 20:33, Björn Schäpers wrote:
This should work if you include "hpp" in the type of the generating product.
Adding "hpp" as type does indeed result in the complete compilation of the
generating product, befo
Am 04.11.2021 um 12:45 schrieb Christian Kandeler:
On 11/4/21 11:22, Björn Schäpers wrote:
we have a static library which uses Protobuf, thus generates the headers, and
compiles the code directly into it.
Static Library {
...
Export {
Depends { name: "cpp" }
Depe
Hi there,
we have a static library which uses Protobuf, thus generates the headers, and
compiles the code directly into it.
Static Library {
...
Export {
Depends { name: "cpp" }
Depends { name: "protobuf.cpp" }
cpp.systemIncludePaths: [product.protobuf.cpp.outputDir]
}
}
Hi there,
my setup is msys2 gcc in 64 and 32 bit, a from msys installed protobuf, and a
self compiled qbs. The protobuf module does not find the header or the
libraries, it seems the search path is just empty, and for the libraries it
looks for the wrong files. It searches protobuf.lib, but
currently working on the feature to implement this .
https://codereview.qt-project.org/c/qbs/qbs/+/315910
https://codereview.qt-project.org/c/qbs/qbs/+/350654
Ivan
21 июля 2021 г., в 03:07, Björn Schäpers написал(а):
Hi there,
my setup is msys2 gcc in 64 and 32 bit, a from msys installed
Am 15.02.2022 um 16:40 schrieb Christian Kandeler:
Hi,
we branched off Qbs 1.22 today. Scheduled release date for
version 1.22.0 is end of March (together with Qt Creator 7.0).
We recommend users to try this branch with their projects and report back any
new problems they find.
Contributors are
Hi,
my main problem is I have MinGW32 und MinGW64, the pkg-config of the latter is
first (or only) in PATH, thus dependencies through pkg-config will get the
inlcude paths etc. for the 64 bit variant. Now I have a dependency which checks
the bitness in the header and errors out on 32 bit.
I
Am 15.02.2022 um 17:08 schrieb Christian Kandeler:
On 2/15/22 16:54, Björn Schäpers wrote:
You could mention *explicitly* that the meaning of product within an Export
has changed.
I have a lot of
Export {
...
cpp.cxxLanguageVersion: product.cpp.cxxLanguageVersion
}
And that blew on me
Yes.
Am 02.05.2022 um 18:27 schrieb Карелин Павел:
I am using the construct:
Product {
name: "SharedLib"
property var exportIncludePaths: [
"./",
"./shared",
]
Export {
Depends { name: "cpp" }
cpp.includePaths: product.exportIncludePaths
}
Good Day,
I was recently forced to use Windows 11 at work and was puzzled why many
of my programs (but not all!) failed to start with the code 0xc7b.
After a lot of investigation I found the issue to be the subsystem values.
All affected programs use Qt, which sets the minimum windows
Am 10.04.2023 um 23:21 schrieb Иван Комиссаров:
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
Hi,
I have a project with multiple sub projects and products and want to move it to
embedded platforms, and thus I want to set compiler flags like mpcu, which
should be the same for all products. I know I can do it through the QtCreator
kit or the command line, but I'd like that to be
But I still need all products to use the module.
Currently I just have all the options within the module and switch depending on
qbs.architecture.
Am 29.05.2024 um 18:12 schrieb Иван Комиссаров:
You can put the other_project_buildconfig module in your projects search paths
- that way it will
29 matches
Mail list logo
