-
Notifications
You must be signed in to change notification settings - Fork 6.1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Can we ask VCPKG to build cmake instead of downloading it? #4501
Comments
Any answer from the community? |
Any update on this? Another option is to download a cmake statically compiled. |
I compiled cmake from source code on alpine:
And replaced that folder by the one downloaded by vcpkg, I also installed libc6-compat for the ninja binary to work:
And then vcpkg compiles! The problem now it's that when I run it I get this:
I tried
Maybe it's because some errors with libc6-compat? |
Thank you for having run the experiment. It is also sad to do not have any feedback from the VCPKG team (@grdowns)... |
What I would do it's to generate a statically linked cmake instead of downloading the release version from here: Btw the error happened because I compiled cmake without openssl, I modify the compilation to use curl for the cmake downloads (I couldn't figure out how to add the openssl support to cmake). So the steps are the following:
And then you can compile a library (specifying the arch
|
Thank you @0ca for the demo. Appreciated. |
Building cmake from source takes some time (iirc around 5 mins). In theory with alpine and musl you can build a static binary that can run in any linux with the same architecture. But yeah, if you want also to support different architectures the way to go is to compile cmake from source code. I wonder why vcpkg decided to used precompiled binaries instead of installing dependencies with a package manager like |
Hi there, I found a way to make it work. It's not documented and I had to find it checking on the source code but it works like a charm and it's simple and "officially supported":
You can export I think this will be enough to close the issue. Hope that helps Cheers |
Thanks, that's great. So we need first to setup cmake and then use the hidden option. Am I right? |
Yes,
But you can just install it doing
`pkg add cmake.`
Easy and fast :)
…On Tue, Jul 2, 2019, 7:07 PM Pierre Moulon ***@***.***> wrote:
Thanks, that's great. So we need first to setup cmake and then use the
hidden option. Am I right?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4501?email_source=notifications&email_token=ABHT3KDQYZVBOCMRSOO4IADP5QCWXA5CNFSM4F55Q5H2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDBJGY#issuecomment-507909275>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABHT3KEGIA2XWSGT7VTSXHDP5QCWXANCNFSM4F55Q5HQ>
.
|
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I'm trying to run VCPKG under an alpine docker image.
I got error like
In order to avoid to use the default download location, I would like to tell VCPKG to just build cmake and use it. Can we do that?
The text was updated successfully, but these errors were encountered: