-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update/Add vcpkg - Please bring vcpkg back to MacOS runner images #11579
Comments
Hi @DSMitten , We will look into the your feature request and keep you posted with updates. |
Hi @DSMitten, ![]() ![]() |
But why can it be included on all the other operating systems? How was it not too large for macos 13, but it is too large for macos 15? Do your macos 15 machines have smaller hard drives than the macos 13 drives did? I don't understand. We could install vcpkg, yes. We could also install npm, but we expect it to be on the machine image. Can you help clarify why vcpkg is treated differently on this version of mac than it was on earlier versions and other operating systems? |
For iOS 18.3.1 on iPhone not MAC |
I understand. Thank you for the notification 😊Sent from my iPhoneOn Feb 20, 2025, at 4:25 PM, Scott Mitten ***@***.***> wrote:
But why can it be included on all the other operating systems? How was it not too large for macos 13, but it is too large for macos 15? Do your macos 15 machines have smaller hard drives than the macos 13 drives did? I don't understand.
We could install vcpkg, yes. We could also install npm, but we expect it to be on the machine image. Can you help clarify why vcpkg is treated differently on this version of mac than it was on earlier versions and other operating systems?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
DSMitten left a comment (actions/runner-images#11579)
But why can it be included on all the other operating systems? How was it not too large for macos 13, but it is too large for macos 15? Do your macos 15 machines have smaller hard drives than the macos 13 drives did? I don't understand.
We could install vcpkg, yes. We could also install npm, but we expect it to be on the machine image. Can you help clarify why vcpkg is treated differently on this version of mac than it was on earlier versions and other operating systems?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Tool name
vcpkg
Tool license
n/a
Add or update?
Desired version
latest
Approximate size
No response
Brief description of tool
Runner images support C++ development, with all major compilers (AppleClang, GCC, LLVM clang) installed on the machine.
However, C++ development requires the ability to download and use public dependencies. The most popular package managers for C++ today are vcpkg and conan. My team uses vcpkg for our external dependencies, and we are able to build with it on Windows, Linux and MacOS 13, useing the
VCPKG_INSTALLATION_ROOT
environment variable to locate it.We are attempting to move to MacOS 15, and our build pipelines don't work because of this missing dependency.
It looks like it was removed a year ago from MacOS 14 images, and so we are going to have to write special code to install it on Mac build machines, which will add time to every build, and another step that can fail.
Not having vcpkg for C++ development is like not having npm for TypeScript development. It is an essential component, and it doesn't make sense to support C++ development on Mac but not support package management on Mac.
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
Platforms where you need the tool
Runner images where you need the tool
Can this tool be installed during the build?
`git clone -C <directory> https://github.com/microsoft/vcpkg`
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: