https://codereview.qt-project.org/c/qt/qtbase/+/645694
> On 15. May 2025, at 17:23, Thiago Macieira wrote:
>
> On Thursday, 15 May 2025 01:35:35 Pacific Daylight Time Liang Qi wrote:
>> https://codereview.qt-project.org/c/qt/qtbase/+/643564 got merged.
>>
>> qtwayland client contents(exclude
Hi,
For Qt 6.10, changes were implemented to split QtModulePrivate targets into
separate CMake packages, to ease Linux distribution packaging,
so they have better file boundaries for their qtfoo vs qtfoo-devel packages.
See https://bugreports.qt.io/browse/QTBUG-87776 for details
Unfortunately t
Hi,
> But how are the ToolsDependencies.cmake files supposed to be found, i.e. why
> are there no extra paths given ?
Usually by calling delegating the lookup of the Tools packages to the Qt6
package.
E.g.
find_package(Qt6 COMPONENTS FooTools)
But I don't recall if the _DIR / HINTS / PATHS
Hi again,
It's taking a while to get internal input on what cmake requirements TQtC has
for yocto and any other configurations.
Due to platform and module freeze already being in place, and 6.9 branching
happening next week,
I took the conservative approach and bumped the minimum version to 3
> On 19. Nov 2024, at 17:07, Thiago Macieira wrote:
>
> On Tuesday 19 November 2024 02:43:14 Pacific Standard Time Alexandru Croitor
> via Development wrote:
>> It was brought to my attention that we might be limited by Qt's (or Qt
>> Company's) support f
> On 19. Nov 2024, at 16:58, Thiago Macieira wrote:
>
> On Tuesday 19 November 2024 02:38:36 Pacific Standard Time Alexandru Croitor
> via Development wrote:
>> I expect its usage will help in certain scenarios which allow using a newer
>> CMake feature during the qt
Hi,
> On 13. Nov 2024, at 18:09, Thiago Macieira wrote:
>
> But is there any chance of lowering the requirement to 3.25 instead?
It was brought to my attention that we might be limited by Qt's (or Qt
Company's) support for Yocto 4.0 (kirkstone) LTS which ships CMake 3.22.
Until it is clarifie
Hi,
> On 14. Nov 2024, at 09:25, Bogdan Vatra wrote:
>
> Hi,
>
> Just out of curiosity, what are the features added to cmake 3.26 that makes
> it so much better than 3.25 and which Qt really needs?
You can see my findings at
https://bugreports.qt.io/browse/QTBUG-131169?focusedId=841296&pag
> On 13. Nov 2024, at 16:01, Alexandru Croitor wrote:
>
>
>
>> On 13. Nov 2024, at 15:38, Sune Vuorela wrote:
>>
>> On 2024-11-13, Alexandru Croitor via Development
>> wrote:
>>> Which debian stable version are you using?
>>
>> D
> On 13. Nov 2024, at 15:38, Sune Vuorela wrote:
>
> On 2024-11-13, Alexandru Croitor via Development
> wrote:
>> Which debian stable version are you using?
>
> Debian stable is debian 12. It ships with 3.25.
>
>> Is it unreasonable to ask to install cmake
Hi,
Thanks for reaching out.
> On 13. Nov 2024, at 15:07, Sune Vuorela wrote:
>
> On 2024-11-13, Alexandru Croitor via Development
> wrote:
>> Hi,
>>
>> We'd like to bump the minimum required CMake version for building and using
>> Qt to CMake 3.2
Hi,
We'd like to bump the minimum required CMake version for building and using Qt
to CMake 3.26.
The pending change is https://codereview.qt-project.org/c/qt/qtbase/+/603886
The rationale is easier maintenance of build system code, and allowing to
provide better public cmake apis and behavior
Hi,
For a while now we had a slightly weird branching situation in qtqa,
where we had a master and a dev branch, and it was a bit unclear what is used
where.
Here's a summary of latest changes regarding that situation.
1) Since a few months, qt submodule integrations (qtbase, qtsvg, etc)
in t
Hi,
Once https://codereview.qt-project.org/c/qt/qt5/+/578757 merges, the CI will
use the license checker code
from the qtqa/dev branch rather than qtqa/master branch, for running the
license checker in
the dev and 6.8 branches of qt5.git and its submodules.
It will also use license checking c
Hi,
qtbase.git dev is open for staging again.
The submodule update round has also been restarted from latest qtbase.git
dev/HEAD, so the previously mentioned repos should also integrate in a few
hours.
> On 10. Jul 2024, at 12:09, Alexandru Croitor via Development
> wrote:
&
Hi,
There was a change that sneaked in between the qt5.git merge of SBOM activation
https://codereview.qt-project.org/c/qt/qt5/+/562482/17
and a change in qtbase https://codereview.qt-project.org/c/qt/qtbase/+/564088
which will now cause changes in qtbase, and some other repos to fail to
integr
Hi,
Starting with Qt 6.8, the build system will generate a Software Bill of
Materials (SBOM) file for each built repo in the CI.
These will be installed in $qt_prefix/sbom/${repo_name}.spdx.
This is only enabled by default in the CI, and not for your local builds.
These files will be included
Hi,
I would like to request a feature freeze and provisioning freeze exception for
SBOM (Software Bill of Materials) generation.
https://codereview.qt-project.org/c/qt/qtbase/+/546923
https://codereview.qt-project.org/c/qt/qt5/+/561694
SBOM generation is about shipping some text files alongside
> On 5. Mar 2024, at 11:43, Volker Hilsheimer via Development
> wrote:
>
>> On 4 Mar 2024, at 15:56, Kai Köhne via Development
>> wrote:
>>
>> Hi Marc,
>>
>> I've nothing against using '#pragma once' for private/internal headers.
>>
>> But you said you mainly want to have this to differen
> I found a way to reproduce it. Setting `CMAKE_INSTALL_PREFIX=/` or any path
> that is different from qt path breaks the docs compilation.
Should be fixed with https://codereview.qt-project.org/c/qt/qtbase/+/521024
--
Development mailing list
Development@qt-project.org
https://lists.qt-project
> On 21. Nov 2023, at 16:46, BogDan Vatra wrote:
>
> On 2023-11-21 16:47, Alexandru Croitor wrote:
>>> On 21. Nov 2023, at 13:21, Bogdan Vatra via Development
>>> wrote:
>>> Hello there,
>> Hi,
>
> Salut,
>
>>
>
> I tried qtmqtt to be sure that I didn't do any mistakes, it seems if I use
> On 21. Nov 2023, at 13:21, Bogdan Vatra via Development
> wrote:
>
> Hello there,
Hi,
>
> I'm trying to port a qt5 module to qt6 which it seems starting with 6.4.x
> the qmake support is broke/removed for modules so I'm forced to use cmake...
>
> I checked other qt modules (e.g. https
Hi,
The object file is supposed to be automatically linked into your application
when you link to the static library target.
That's handled by the qt6_add_resources call that qt6_add_shaders call, and it
assumes you use target names for linking, and not file paths.
If it doesn't, i suspect you'r
Hi,
Looking at the log, it appears that mingw's windres.exe can't handle spaces in
paths passed to -I?
-I "C:/Program Files/PostgreSQL/14/include"
cc1.exe: fatal error: Files/PostgreSQL/14/include: No such file or directory
compilation terminated.
In any case, you can work around it by either
The log told you
WARNING: QDoc will not be compiled, probably because libclang could not be
located. This means that you cannot build the Qt documentation.
You need to have a prebuilt libclang.
From https://wiki.qt.io/Building_Qt_Documentation#Building_Qt_6_Documentation
and https://doc.qt.io/
Hi,
In documentation that you linked, it's written that you will need qdoc,
qtattributionsscanner and possibly qhelpgenerator.
so running
$ ninja qdoc qtattributionsscanner qhelpgenerator.
should hopefully be sufficient
> On 17. Aug 2023, at 10:17, Haowei Hsu wrote:
>
> Hello, Alexandru. Than
Hi,
You can't use Qt 6.3.2 to build documentation of Qt 6.5 / 6.6 / 6.7 / dev.
Mixing versions like that is not supported.
The configure log even tells you that, but you passed
-DQT_NO_PACKAGE_VERSION_CHECK=TRUE anyway.
You need a Qt 6.5 build to build documentation for Qt 6.5.
You need a Qt 6.
Hi,
I think adding the 2 proposed features (showing include warnings and disabling
mocs_compilation) make sense.
Having global variables control the per target property values also makes sense.
Not sure how useful per-source-file properties would be, and it would also
complicate the implementat
> On 3. Jul 2023, at 16:50, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> El lunes, 3 de julio de 2023 11:47:44 -03 Lisandro Damián Nicanor Pérez Meyer
> escribió:
> [snip]
>> So far it has worked, but of course I'll have more feedback later on :-)
>
>
> I just built 5.6.1 as shared lib
> On 3. Jul 2023, at 16:47, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> Now the question is: is the CMake file used to only check for it's presence
> or will designer fail to load the static file?
If the CMake file is present, but not loaded (via an explicit find_package call
or transi
> On 3. Jul 2023, at 15:29, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> Hi!
>
> El lunes, 3 de julio de 2023 05:26:11 -03 Alexandru Croitor escribió:
>>> On 30. Jun 2023, at 20:04, Lisandro Damián Nicanor Pérez Meyer
>>> wrote:
> [snip]
>>> I recently noted the CMake variables QT_SKIP_
> On 30. Jun 2023, at 20:04, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> Hi!
Hi
>
> I recently noted the CMake variables QT_SKIP_AUTO_PLUGIN_INCLUSION and
> QT_SKIP_AUTO_QML_PLUGIN_INCLUSION, which default to undefined.
>
> If I understand correctly the CMake file for searching for p
Hi,
I would like to nominate Amir Masoud Abdol for approver rights in the Qt
project.
He's been doing good work in the Qt build system, as well as tidying up code
across all repositories to prepare Qt for unity builds.
I trust him to approve changes responsibly.
Work: https://codereview.qt-pr
Hi,
Is this still a problem? If yes, please file a bug report so this is not lost.
If I understand correctly, your host build had no protobufgen installed, and
the wasm build fails to configure then.
For other repos, in a situation like this, the module is skipped (e.g.
qtdeclarative + qmlcache
Hi,
We plan to do a video call to review the Qt 6.5 public CMake changes.
If you'd like to join, it will be next Tuesday at 13:00 CET (UTC+1) Berlin
time, until 14:00.
The agenda is to promote some API from Technical Preview, and review some new
and modified APIs.
You can see them here
https
Hi,
The feature is marked in configure.cmake as PRIVATE only.
Try explicitly including one or both of
#include
#include
Note that in src/corelib/ipc/qsystemsemaphore_p.h there is
#if QT_CONFIG(systemsemaphore)
#include "qcoreapplication.h"
#include "qtipccommon_p.h"
#include "private/qtcore-
36 matches
Mail list logo
