diff options
| author | Alexey Edelev <alexey.edelev@qt.io> | 2024-06-13 15:06:09 +0200 |
|---|---|---|
| committer | Alexey Edelev <alexey.edelev@qt.io> | 2024-06-14 13:17:38 +0200 |
| commit | 57acebeac848d4182a3f994b4326b41108cae4ec (patch) | |
| tree | f33cb73784f9d85a857aac439b4dcfd3e37f9541 /src/network/access/qnetworkrequest.cpp | |
| parent | e3bfc1a2ef3732b158d8297a9b8b3c18766827f9 (diff) | |
Allow using VCPKG for standalone Qt repos
Add the QT_USE_VCPKG variable and the VCPKG_ROOT environment variable
handling to the Qt toolchain file.
The below rules applicable when configuring Qt project or Qt repository
using the qt.toolchain.cmake file:
If qtbase(or top-level qt) was initialy configured with vcpkg the new
code path will be ignored, if the QT_CHAINLOAD_TOOLCHAIN_FILE matches
the path to the vcpkg toolchain file.
If qtbase(or top-level qt) was configured with some other toolchain
file provided it will be chainloaded next to the vcpkg one using
VCPKG_CHAINLOAD_TOOLCHAIN_FILE variable, and the vcpkg toolchain file
will be chainloaded by Qt toolchain using QT_CHAINLOAD_TOOLCHAIN_FILE
code path.
If qtbase(or top-level qt) was configured without extra toolchain file
specified, the vcpkg toolchain file will be chainloaded by Qt toolchain
using QT_CHAINLOAD_TOOLCHAIN_FILE code path.
So the generic toolchain file load sequence can be described as
following:
qt.toolchain.cmake[->vcpkg.cmake][->customtoolchain.cmake]
The QT_USE_VCPKG value is inherited from qtbase(or top-level qt) build
by default.
We also preserve the VCPKG_TARGET_TRIPLET, but allow using the one that
is specified by user.
Change-Id: I85c8ed4e9abd658609ac6ea71393dd23a9bc1688
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Diffstat (limited to 'src/network/access/qnetworkrequest.cpp')
0 files changed, 0 insertions, 0 deletions
