-
Notifications
You must be signed in to change notification settings - Fork 139
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
vcpkg port? #254
Comments
- Update the version info - Don't expose a private header directory as public - Publish an exported target With this, it's possible to just import the installed targets. I have a small overlay port for vcpkg on top of this that lets me import libucl, which is a first step towards fixing vstakhov#254.
I have this as an overlay port:
vcpkg_from_github(
OUT_SOURCE_PATH SOURCE_PATH
REPO vstakhov/libucl
REF 95df30cf3e35788c08be537a1623499c98415674
SHA512 8c61061d3fa02283f700ac6a5ddb035348c67ec4e45d30a47da945a39adffda5f3bc8db6fae35544185983e3204efd7bdef55b145d2a387a04d06aecca461ea3
HEAD_REF master
)
vcpkg_configure_cmake(
SOURCE_PATH ${SOURCE_PATH}
PREFER_NINJA
)
vcpkg_install_cmake()
vcpkg_fixup_cmake_targets(CONFIG_PATH share/ucl TARGET_PATH share/ucl)
file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")
file(INSTALL ${SOURCE_PATH}/COPYING DESTINATION ${CURRENT_PACKAGES_DIR}/share/libucl RENAME copyright)
With this, I am able to build and incorporate libucl into my project. This doesn't handle any of the optional bits (libcurl / libfetch integration, lua / python bindings). I am happy to submit this to vcpkg if you like, or you're welcome to use them as the starting point for a richer integration. |
Thank you very much for this work, David. I would suggest you to submit this as a starting point and then probably gather feedback from users (if any) for further improvements. I don't use vcpkg, so I cannot properly test it I'm afraid. |
It would be great to have libucl support in vcpkg.
The text was updated successfully, but these errors were encountered: