Change default triplet about vcpkg HOT 14 CLOSED

The Question about the individual configuration aside: Shouldn't the default be x64 anyway?

from vcpkg.

Sooner or later the need for a config file will arise. Why wait?

from vcpkg.

@9prady9 you can set environment variable VCPKG_DEFAULT_TRIPLET https://vcpkg.readthedocs.io/en/latest/users/triplets/#additional-remarks

from vcpkg.

@MikeGitb The reason to use x86-windows as the default triplet is to make the new user experience as absolutely streamlined as possible: Visual Studio defaults to x86 for new projects and remembering to change the architecture is one of those tiny details that's easy to overlook even for experts.

@Kwizatz You're absolutely right, we will certainly need a config file eventually. However, I'd like to accumulate as many concrete use cases as reasonable first to make sure we can make solid design decisions (for example, should the setting be per-repository or user-wide? It's easy to say both, but I'd like to hear of the need in practice before jumping to the most complex option).

Additionally, I've heard asks offline for a triplet environment variable as well, so that's the motive for proposing it above.

from vcpkg.

Would an environment variable work?

Something like VCPKG_DEFAULT_TRIPLET or VCPKG_TRIPLET?

from vcpkg.

Right, and imho the default in VS is wrong too ;)
But I see your point.

from vcpkg.

If you install everything at once, you can use --triplet x64-windows to save yourself some typing.

from vcpkg.

I think an environment variable would be great.

from vcpkg.

Having a way to atleast switch the default triplet helps, especially in docker and/or ci environments.

from vcpkg.

thank you @KindDragon

from vcpkg.

@albertziegenhagel @9prady9 @Telokis

where will I set VCPKG_DEFAULT_TRIPLET or use --triplet x64-windows? would you tell me please?

from vcpkg.

One way is to set it as a windows environment variable.

from vcpkg.

@drescherjm

One way is to set it as a windows environment variable.

Thank you very much for your comment. How can I use --triplet x64-windows? it will be look like this:
./vcpkg.exe --triplet x64-windows install cgal
or in a different way

from vcpkg.

The reason to use x86-windows as the default triplet is to make the new user experience as absolutely streamlined as possible: Visual Studio defaults to x86 for new projects

Not on my system. At least, not with CMake:

PS C:\Users\Tim\Realsense\realsense_recorder> cmake -B build -S . -DCMAKE_TOOLCHAIN_FILE=C:/Users/Tim/local/vcpkg/scripts/buildsystems/vcpkg.cmake
-- Building for: Visual Studio 16 2019
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19042.
-- The CXX compiler identification is MSVC 19.28.29913.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features - done
CMake Error at C:/Users/Tim/local/vcpkg/scripts/buildsystems/vcpkg.cmake:794 (_find_package):
  Could not find a package configuration file provided by "realsense2" with
  any of the following names:

    realsense2Config.cmake
    realsense2-config.cmake

Has that changed?

from vcpkg.