-
Notifications
You must be signed in to change notification settings - Fork 651
Consider distribution of the library using vcpkg #269
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
Comments
Thanks for your interest in Beast! I tried going through the steps for vcpkg but it was a bit too complex for me. But if you'd like to package it up (or anyone else who wants to volunteer) I would be very appreciative! |
I can look into that and package it. I would than need the url for certain stable version of the package. It should not point to master probably. |
Hmm... well, Beast is still in beta. There's a little more interface work to do before I can consider calling a 1.0 version. Specifically this: https://github.com/vinniefalco/Beast/issues/154 |
Well there are other betas in vcpkg. I don't see it as a problem. |
Oh! Okay, well when b29 passes review I will create a tag for v1.0.0-b29 and we can use that. Thanks! |
Awesome :-) |
I've created a new tag, its called v1.0.0-b30 if you would like to try setting up the package! If you need to add files to the repository just submit a pull request. Thanks! The tagged branch: |
Hi, I'll look into that. |
I just created a pull request for Microsoft. |
@jhruby You did such a wonderful job on this could you possibly be interested in doing the same for NuDB? Its quite similar to Beast in structure: https://github.com/vinniefalco/NuDB |
Sure I can do it :) |
Cool! I pushed a tag for Here's the relevant issue, thanks for volunteering |
This looks like it's done, thanks! |
Hi,
It would be very cool to see your library distributed through vcpkg channel.
Jan
The text was updated successfully, but these errors were encountered: