Open greenozon opened 2 months ago
This project demonstrates the issue https://github.com/microsoft/vcpkg/issues/39832 (from where you came here, obviously) with the qtbase port in vcpkg, and thus it's meant to be run only in vcpkg's manifest mode.
This can be done by passing the vcpkg toolchain file to CMake like this, from the project's root dir:
mkdir build
cmake -S . -B build -DCMAKE_TOOLCHAIN_FILE=/path/to/vcpkg/scripts/buildsystems/vcpkg.cmake
thanks a lot! it builds lots of stuff, almost 10 minutes....
Yes, The base Qt package is huge already. Building all the Qt components easily takes 1.5hrs. vcpkg also builds it in Release and Debug variants, so it's being built twice. Luckily, vcpkg caches it locally, and as long as your vcpkg repo or toolchain don't change, you only need to build it once.
The actual issue happens right after vcpkg is done, when CMake tries to find/use the Qt6 package.
well, after initial cmake command above I was able to compile/link/run the test app what issue do you hit in your case?
It's documented in my vcpkg bug report linked above. Might possibly be fixed now, didn't try again for a few weeks since I've opened the report. Helped myself with a local overlay port that replaces the problematic path.
Hi! what is the correct way to install qt6 under Linux so that this test sample proj will find it?
Ubuntu 22.04: