Does VCPKG_TARGET_TRIPLET affect the main project along side the dependencies.

[roastduck]

Dear team,

I intend to build my project with a proprietary compiler, so I create my own triplet overlay, and configure my project with VCPKG_TARGET_TRIPLET and VCPKG_OVERLAY_TRIPLETS. All the dependencies build fine. However, the main project that depends on the dependencies is still building with the default compiler. Is it by design? How should I configure my compiler for both the dependencies and the main project?

[Neumann-A]

Set VCPKG_HOST_TRIPLET....

[Neumann-A]

but my main project is incorrectly built for x86 (also from the x86 host).

You need to setup your toolchain for your project correctly. All vcpkg settings are just for within vcpkg.

[roastduck]

but my main project is incorrectly built for x86 (also from the x86 host).

You need to setup your toolchain for your project correctly. All vcpkg settings are just for within vcpkg.

But I need to set -DCMAKE_TOOLCHAIN_FILE=/path/to/vcpkg/scripts/buildsystems/vcpkg.cmake to use vcpkg, how should I also set my own toolchain then?

[Neumann-A]

-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=<your toolchain>

[roastduck]

I have figured out that I need to set VCPKG_CHAINLOAD_TOOLCHAIN_FILE BOTH by -DVCPKG_CHAINLOAD_TOOLCHAIN_FILE= AND by setting it in my triplet overlay. Is that by design?

[Neumann-A]

Yes. Maybe the triplet variable should have had a different name but conceptually they are the same.
The triplets determines stuff for inside vcpkg. What your project does is determined by you.