| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Ic570eba1f84fd82fec9676a03ed3bf01e14eca80
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ib2a60c10bcf482b92d5cfa903ba4f42f3c122208
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I7f90db77192d65900fe3c3a601b6240a225dcc83
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I15f059db705b60938c71963d3910ed36e2d078bb
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Location keys are meant to be used as regular expression.
The . need to be appear as `\.` in the regular expression.
The JSON parser interprets the `\`, hence the `\\.`.
Pick-to: 6.7
Task-number: QTBUG-121039
Change-Id: I959dffc86a4786ef90a400a80540353c4f7e7f3b
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
|
|
|
|
|
| |
Change-Id: Ie01ce1f74ebeb0cd430591b34cc836af1989e532
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ib694ceb95a1d34bedea6687596ed1b5e1978de54
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I218ae131eb84157c9dbec4aeaccf590e4605821a
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The license test in qtqa reads this file
in order to check the validity of the license used.
This file reproduce the QUIP-18 [1] rules, with some exceptions.
Each entry in the file corresponds to a set of licensing rules.
A set of licensing rules can depend on the file ending,
registered in "file_pattern_ending". The last entry in the
file has no "file_pattern_ending", it sets the rules for the
files whose licensing does not depend on their ending.
The license to be used depends on the location
of the file within the Qt module repository.
Let's call this "<true_location>".
The "<true_location>" can also correspond to a file name,
offering flexibility for exceptions to the rule.
The "<true_location>" are registered in "location".
For each "<true_location>" there is a
"file type" entry and a "spdx" entry.
The "spdx" entry gives the rule:
the expected license tag(s) in SPDX format
for the file ending (if applicable) and "<true_location>".
The "file type" informs on the QUIP-18 type
the tested file corresponds to. It is purely informational
for the reader.
The set of rules are tested in order of appearance
in the json file. For this reason, a more constraining
ending (like "special.txt") needs to appear in
a "file_pattern_ending" located before
the "file_pattern_ending" of a less constraining ending (like ".txt").
Also, a file ending cannot be present in two "file_pattern_ending".
"file_pattern_ending" and "spdx" should list strings.
"<true_location>" can be regular expressions.
During the test the deeper "<true_location>" are
checked first. The order is which they appear in the json file
does not matter.
To test this file, run
QT_MODULE_TO_TEST=../qtconnectivity perl tests/prebuild/license/tst_licenses.pl
[1]: https://contribute.qt-project.org/quips/18
Pick-to: 6.7
Task-number: QTBUG-121039
Change-Id: Ied33a72b1563966b13a90e3bf4955d6f58cde7e5
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to QUIP-18 [1], all build system
files should be BSD-3-Clause
[1]: https://contribute.qt-project.org/quips/18
Pick-to: 6.7
Task-number: QTBUG-121787
Change-Id: I70ac22ec6c8ec1e0917e2c24c91ec2046d3ca822
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to QUIP-18 [1], all examples and snippets
files should be
LicenseRef-Qt-Commercial OR BSD-3-Clause
[1]: https://contribute.qt-project.org/quips/18
Pick-to: 6.7
Task-number: QTBUG-121787
Change-Id: I9a8fdb5308396e63785486291c4dc41cd59c1fe4
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to QUIP-18 [1], all test files should be
LicenseRef-Qt-Commercial OR GPL-3.0-only
[1]: https://contribute.qt-project.org/quips/18
Pick-to: 6.7
Task-number: QTBUG-121787
Change-Id: I2ac6d02f9781843d7e7d43dcb20040cee2185386
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to QUIP-18 [1], all tools file should be
LicenseRef-Qt-Commercial OR GPL-3.0-only WITH Qt-GPL-exception-1.0
[1]: https://contribute.qt-project.org/quips/18
Pick-to: 6.7
Task-number: QTBUG-121787
Change-Id: I42358fbbb1c9dafdce023d69616e47546e434769
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
|
|
|
|
| |
Change-Id: If99887bc714088d05cbf8d80d195fe64de019658
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently targetLost is used before reportError. So the QNearFieldTarget
will be deleted by the user and the slot connected to the error signal
will never be called. In addition reportError use a QueuedConnection so
we need to do that for targetLost too and change the order.
Because targetLost is always used after invalidate
we can add emitting the signal to invalidate.
Pick-to: 6.7
Change-Id: I070f6bb705ccff0feacac7f58264ff6ea238bc89
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>
|
|
|
|
|
| |
Change-Id: I7337d736e2f9b2e4c371df4d8ed0e0f3f635637c
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I870d5a159154e60905876c88599c6aa269105512
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I3f4fed2062095321271cf14ee562cc0e31a39544
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Bluetooth profile UUID is registered on DBus the whole time while
the device is connected, this prevent new connection from happening,
which also need to register to the same UUID on DBus.
The change is to unregister Bluetooth profile UUID after connection, as
it's no longer needed for the current connected device.
This will allow new devices that trying to connect to register the same
Bluetooth profile UUID On DBus.
[ChangeLog][QtBluetooth][Linux/BlueZ] Unregister Bluetooth profile UUID after connection,
so it can be registered for connecting to new devices.
Fixes: QTBUG-82413
Change-Id: I0e0b4cd303b32213725638efb323e6d00cb7b9e5
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ie419493ac1dea1d30923adda6d00fb926b468bfc
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I4d71f0102348ba7cbf7373843bcbeda14c26c8f4
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I80568e67eb3c7e9d5419dd82cf19310186257697
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I93a3fd45314c7fa5379ad6ca2c2cf26743ec10cd
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I201455c10bf5b01b2307500e1c74bb6f21c0c9c8
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ic103ba24c4f71de3dd5c9aa24364efcaff8b3d58
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iecc79651604e3d5c6746144dd6947ed6100a792e
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ie12b46f5f8628cc9d36aa28f259a36a441720d20
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
| |
This signal was removed in Qt 6.
Fixes: QTBUG-97943
Change-Id: I46d14c19c3e562f6056cb508a1aea60b0db5f56d
Reviewed-by: Ievgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
The ACR122U device used for testing does not work in
"Dual" mode.
Task-number: QTBUG-97943
Change-Id: Ib36e403d426aa8f9187765810eab7f5d5c86bb04
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
Reviewed-by: Andreas Hartmetz <ahartmetz@gmail.com>
|
|
|
|
|
|
| |
Task-number: QTBUG-97943
Change-Id: I7887daf6105ee51bc9b7dd7e57ec4db016554245
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 4282160a843a01457d71c995d870ab447ada655d.
Adapt to changes in QtNfc:
- omit .pri and .pro files from the qmake build system
- add re-added source files to CMake build system
- omit documentation about message handlers (no place for it)
- adjust documentation elsewhere to match current practices
- remove autogenerated DBus interfaces, generate them at compile
time instead
- remove unused neard DBus interface XML files
- adjust code to current QtNfc API
- add the "we mean it" comment to just re-added private headers
- replace old license headers with equivalent SPDX license headers
If the PCSClite dependencies are found, the PCSClite backend needs
to be explicitly disabled to allow enabling the neard backend.
That means that the status quo regarding which backends are built
is largely maintained.
Compiling, not to mention runtime selection or simultaneous use,
of more than one backend continues to be unsupported, as it has
always been. It seems like neard is ~only used on embedded
systems, where a custom Qt build is par for the course. Debian
last shipped neard in Buster, currently oldoldstable. Ubuntu last
shipped it... at a time that is not covered anymore in its package
search. Most other large distributions do package neard, though.
I found the following that do: Suse, Fedora, Arch, Gentoo, Yocto.
Task-number: QTBUG-97943
Change-Id: I1b4541c49bb5855800fd949bdc20e200967e58b5
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I671ad21d3cfbd11f9c9261c1d1679673b0a0f8e8
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I484f9c50f49145155e8c357e91c6f058be0991ec
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ic30b4ddf8f3307bc966c739ef5c08031e7aea85d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I2d13250f12a10200533d039606037f6486d03be2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I78de6c1c46a06e78859149cedaf2a4ab744bfccd
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ifb633a1910e73e3819b0289e430fef8de5b32e12
Reviewed-by: Ievgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io>
|
|
|
|
|
| |
Change-Id: I246ce76d1afa70ed38b83fa131ddb22c2cae61d2
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
| |
Pick-to: 6.6 6.7
Task-number: QTBUG-113277
Change-Id: I4885e6df894e24c2fdacccc4e58530ee9b190968
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
| |
Change-Id: I9350b1df52326f259f12a2bc8a2352057a06f9d7
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: If4a0041c56c6eb820a607f48aa77b48d73672e0d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-117983
Change-Id: Ieaa116a12604bc5e660f96b873f8354f70b7a7c6
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
| |
Task-number: QTBUG-117983
Change-Id: Id155b4277dd7a40d5d0c9ecf96288de91871d37b
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
|
| |
Pick-to: 6.6 6.7
Change-Id: I784aea736d77df873289141535dcbe20f7c0d131
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
| |
Change-Id: I3638a00bebf8d5716fc8b2713b52a2a15f794262
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
| |
These are the names also given in the online documentation,
so let's use them in the examples.
Pick-to: 6.7
Change-Id: Ia10af880a0f2495094a5eb626b568da670e2848d
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Linkify Qt Bluetooth, and add tags.
QtBluetooth will create a link to https://doc.qt.io/qt-6/qtbluetooth-module.html
Pick-to: 6.6 6.7
Change-Id: I9da8bda1591fae26fbe0bde7ac86371af4b9e71c
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
|
| |
Pick-to: 6.7
Change-Id: I5805c3b8acd59826b5b3e8dc304d1b57f1b72df6
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
| |
Change-Id: Ib0092969ce426ab2ae780666ade6cec364a610f4
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The read operation can be cancelled, or might fail for some reason.
In this case, the user does not expect the existing entries to be
deleted, so do not clear the message before reading.
If the read is successful, the existing message is replaced by the
new one, so no action is required here.
Update the example documentation to clarify this behavior.
Amends 115b4d947adf90a706f76de831f34960e3c62a9c.
Fixes: QTBUG-120410
Pick-to: 6.7 6.6 6.5
Change-Id: Ibaf00fb3c661abcc39b5d758e57ee5a837c0e270
Reviewed-by: Ievgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io>
|