【 在 iambigcat 的大作中提到: 】
【 在 passbyer 的大作中提到: 】
: 1. 因使用的数据库是sqlserver2008r2，因为不使用事务显示正常，使用事务就被清空，因此只能是使用事务的原因，通过db.driver()->hasFeature(QSqlDriver::Transactions)查看，发现居然不支持事务，有点不可思议。而采用sqlite居然就支持...
【 在 hgoldfish 的大作中提到: 】
: 不知道跟 vcpkg 有多大区别。
We would like to provide more flexibility to the Qt users via leveraging a package manager in addition to the traditional Qt Installer.
Delivering additional components in source code form utilizing a package manager allows releasing updates when needed,
not only as part of a new Qt release.
There is also a benefit of being able to have much more libraries to the users without increasing the complexity of the baseline Qt unnecessarily.
For the user it's more straightforward to pick up the component once in the Installer component page rather than selecting the same component separately to each target and Qt version.
To make it easier to leverage new package manager functionality Qt Installer starts providing conan(.exe) client (https://conan.io)
which can be used to build the additional libraries from source packages along with your CMake project.
Conan provides a way to a vast collection of packages (e.g. openssl, zlib, etc. in https://conan.io/center/) which can be further utilized in your project.
In Qt Installer there are two additional packages utilizing conan, qtnetworkauth and qtimageformats.
>From the Qt Installer you can install the conan(.exe) client
It uses conan setting files specific to your Qt installation
Profiles are installed to (per 6.x essentials binary package):
When you install these source packages via Qt Installer the sources are exported to conan cache specific to your Qt Installation
The conan tools and additional packages are under "Preview" category in the Qt 4.x Installer.
The build recipies of the additional packages rely on the presence of installed Qt 6.0 snapshot (Preview) binary package.
This is still in early phase so workarounds may be required and things need to be fixed but you can try it out now:
【 在 libgcc 的大作中提到: 】
Annual Report about the KDE Free Qt Foundation
Olaf Schmidt-Wischh?fer ojschmidt at kde.org
Fri Sep 4 20:17:31 BST 2020
Previous message (by thread): FOSDEM 2021
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dear KDE community,
please find below my annual report 2019/2020 about the KDE Free Qt Foundation.
It is for me and Martin Konold. We are representing KDE in the board of the
Best regards, Olaf
Goals of the foundation: ,,securing the availability of the Qt toolkit for the
development of Free Software and in particular for the development of KDE
The foundation has a legal Agreement with The Qt Company to ensure that Qt
stays Open Source.
Activity in 2019/2020:
* Negotiations about updating the Agreement with The Qt Company
* continue protecting Qt as an Open Source library
* allow The Qt Company to make the paid Qt version more attractive without
compromising Open Source
* update from X11 to Wayland without harming the business of The Qt
Company, e.g. “embedded” products
* Negotiations have been delayed by a number u-turns from The Qt Company.
* We repeatedly resisted pressure to accept far-reaching changes on short
notice “or else”.
* We are currently waiting for a signal from The Qt Company on how to
continue with the talks.
- Our motivation for the future is unchanged:
* find solutions that are good for all stakeholders (KDE, The Qt Company,
Qt contributers, Qt users)
* protect Open Source Qt
* help to keep the ecosystem of Qt business and Qt contributors healthy
* Resolving contradictions between the paid Qt licensing terms and the LGPL
- Qt customers were not allowed to use products “created with” Open Source
- In October 2019, we suggested changes to the paid licensing terms.
- By July 2020, these have been partially accepted by The Qt Company.
- It seems there is still a conflict between paid licensing terms and Open
- We believe it is in the best interest of The Qt Company to fully resolve
- Qt itself incorporates products based on Open Source Qt (example: Qt Web
Engine is based on a khtml derivative).
- Should the KDE Free Qt Foundation continue to pursue this topic? It is
only indirectly related to the legal Agreement with The Qt Company. It is in
scope of the stated foundation purpose.
Comments and questions are welcome on the (public) kde-community at kde.org
mailing list or at the (non-public) KDE AGM on Monday, 7 Sept 2020
【 在 hgoldfish 的大作中提到: 】