Note: not talking about the cache of the artifacts generated by vcpkg's Binary Caching, but the cache of vcpkg's executable and its data files (e.g. ports file), which is useful to save the time it takes to build vcpkg from its repo.
Since run-vcpkg@v11 the cache of vcpkg exe+data is off by default since the executable of vcpkg is already delivered as a prebuilt file upon bootstrapping vcpkg. This is not true for ARM (not yet), hence it may make sense to turn ON the vcpkg executable cache only when the host of the GH runner is ARM/ARM64.
Note: not talking about the cache of the artifacts generated by vcpkg's Binary Caching, but the cache of vcpkg's executable and its data files (e.g. ports file), which is useful to save the time it takes to build vcpkg from its repo.
Since
run-vcpkg@v11the cache of vcpkg exe+data is off by default since the executable of vcpkg is already delivered as a prebuilt file upon bootstrapping vcpkg. This is not true for ARM (not yet), hence it may make sense to turn ON the vcpkg executable cache only when the host of the GH runner is ARM/ARM64.