://codereview.qt-project.org/q/owner:lucie.gerard%2540qt.io
Reviews:
https://codereview.qt-project.org/q/reviewer:lucie.gerard%2540qt.io
Disclaimer: We are working in the same team.
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org
.
Then, QDoc won't generate their corresponding documentation. Right?
I would assume so, yes.
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
that the whole of Qt has been built. You did build
the documentation only.
You want to run "ninja install_docs" or "ninja install_html_docs".
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On 10/7/23 19:10, Haowei Hsu wrote:
It's been a while since the last time we discuss this issue.
And recently, I re-tried to configure qt-6.2.4 with msys2/mingw64 shell.
However, it still failed with the same error again:
Sounds like https://bugreports.qt.io/browse/QTBUG-105267
--
Jörg
developer-build-on-linux:
$ rg QT_POSIX_IPC
install/target/include/QtCore/qtcore-config.h
91:#define QT_POSIX_IPC
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
just because you're working on one
file. One thing we're hoping for is improved CI times with unity builds.
BR,
Joerg
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
- rename qmake to qmake_orig
- create a wrapper script that calls "qmake-orig -qtconf
somethingelse.conf $@"
- name that wrapper script qmake
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
that lupdate-pro is located in the same host Qt that
lupdate belongs to. That's why LibraryExecutables is used.
> The same problem occurs again when it enters usr/libexec since there
is a separate qt.conf
Why is there a separate qt.conf?
--
Jörg Bornemann | The Qt Company
--
Development mailing l
On 3/29/23 15:31, Alexandru Croitor via Development wrote:
I would like to nominate Amir Masoud Abdol for approver rights in the Qt
project.
+1
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Hi,
we're proposing a new QUIP: License specification in Qt's modules
Please review https://codereview.qt-project.org/c/meta/quips/+/436096
Cheers,
--
Jörg Bornemann | The Qt Company
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
: CMAKE_UNITY_BUILD is documented to not play
well with CMAKE_EXPORT_COMPILE_COMMANDS. This might hurt users of clangd
(using clangd with Qt's sources).
--
Jörg Bornemann | The Qt Company
___
Development mailing list
Development@qt-project.org
https://lists.qt
ke-private files I've filed
https://bugreports.qt.io/browse/QTBUG-107621
--
Jörg Bornemann | The Qt Company
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
meshdebug
qdistancefieldgenerator
qmldom
qmljs
qmlplugindump
qmltc
--
Jörg Bornemann | The Qt Company
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On 7/16/22 12:00, Felix Crazzolara wrote:
I wanted now to write some CMake code to ensure that Qt is always and
entirely linked dynamically. For that purpose, I intended to iterate
through the target properties LINK_LIBRARIES and
INTERFACE_LINK_LIBRARIES of Qt5::Widgets or Qt6::Widgets and
completed for qtbase and qttools.
More to follow.
Cheers,
Joerg
--
Jörg Bornemann | The Qt Company
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
s maturity by converting the existing
Qt modules.
--
Jörg Bornemann | The Qt Company
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On 1/18/22 15:10, Cristián Maureira-Fredes wrote:
Due to her contributions in qtbase and other modules [3],
I firmly believe she will manage to maintain it.
+1
I share your belief. :)
--
Jörg Bornemann | The Qt Company
___
Development mailing
-devtools . QML: Provides the QmlDevtools library and
various utilities.
...
$ ../qtbase/bin/qt-configure-module ~/dev/qt/dev/qtdeclarative
-no-feature-quick-designer
--
Jörg Bornemann | The Qt Company
___
Development mailing list
On 1/3/22 2:40 PM, Lars Knoll wrote:
One other possible solution to improve compile times is the hack we used
15 years ago in KDE, where we grouped many .cpp files into one
compilation unit. There’s however a balance needed here, as it reduces
the efficiency of -j, but maybe compiling 4-8
On 1/3/22 12:09 PM, Ulf Hermann wrote:
d, We used to build at least Qt itself with PCH by default. Why did we
change the default?
Building Qt with PCH is still the default.
Unless you're on macOS with CMake < 3.18 and build for multiple
architectures.
Cheers,
Joerg
20 matches
Mail list logo
