Luca

@SamuelMarks closing stale issues. Feel free to continue discussion if needed.

@SamuelMarks you can use `run-vcpkg` with an explicit value for [`vcpkgDirectory`](https://github.com/lukka/run-vcpkg/blob/main/action.yml#L11) input that points to the file system location where you want vcpkg to be checked out. If it is...

@afinetooth it is now indeed working, without any change on [run-vcpkg](https://github.com/lukka/run-vcpkg) repository. For helping tracking down the issue, I enabled in this [PR](https://github.com/lukka/run-vcpkg/pull/113) two different changes: - using [parallels](https://github.com/marketplace/actions/coveralls-github-action#complete-parallel-job-example) with...

@jwillemsen I cant see the ticket. Is there anything that could be done on the run-vcpkg side to solve this issue?

@jwillemsen thanks for the heads up about this! I upvoted the issue, thanks for posting the link.

@Shatur95 yes, it would be possible, no ETA though. Instead of specifying a tag, or a commit id, the best practice is to [use vcpkg as a submodule](https://github.com/lukka/run-vcpkg/blob/main/README.md#use-vcpkg-as-a-submodule-of-your-repository), so that...

Please take a look to [run-vcpkg@v10](https://github.com/marketplace/actions/run-vcpkg) and see if suites your needs. Feel free to reopen this or a new ticket about any problem you may see.

@Shatur right, tags are not supported. Reopening this item.

@justusranvier hitting the `MAX_PATH` limitation is certainly a nightmare that forces unnecessary changes to workaround it. The most important thing is to _pin_ a specific version of `vcpkg`, so that...

@rhuijben this is a vcpkg issue, that you need to work around. Remember that `run-vcpkg` caches `vcpkg.exe` and all its built packages, so if you are continuously hitting that "broken"...