mirror/vcpkg
1
0
Fork 0
mirror of https://github.com/microsoft/vcpkg.git synced 2024-11-30 14:26:03 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
81fbbf8d96
vcpkg/ports/sol2/portfile.cmake

30 lines
811 B
CMake
Raw Normal View History

[sol2] rename port sol to sol2 and fix the full port (#3766) * [sol2] rename port sol to sol2 and fix the full port * [sol2] Simplification and cleanup. Don't remove upstream's include directory.
2018-06-26 12:43:00 +08:00
include(vcpkg_common_functions)
vcpkg_from_github(
OUT_SOURCE_PATH SOURCE_PATH
REPO ThePhD/sol2
[sol2] Update library to 3.0.3 (#7804)
2019-08-21 22:55:19 +08:00
REF v3.0.3
SHA512 8c8f36eaedb76863106ecd24543b82c76a2fac15e86bfaf0e724b726e89d4238adf9eea8abefe0add5ee17e45b1a73ee24496f691b79c15dca85e2cfde8762b4
[sol2] rename port sol to sol2 and fix the full port (#3766) * [sol2] rename port sol to sol2 and fix the full port * [sol2] Simplification and cleanup. Don't remove upstream's include directory.
2018-06-26 12:43:00 +08:00
HEAD_REF develop
[sol2]Disable export namespace to fix usage issue. (#8243) * [sol2]Disable export namespace to fix usage issue. * [sol2]Re-fix namespace issue.
2019-09-26 20:43:46 +08:00
PATCHES fix-namespace.patch
[sol2] rename port sol to sol2 and fix the full port (#3766) * [sol2] rename port sol to sol2 and fix the full port * [sol2] Simplification and cleanup. Don't remove upstream's include directory.
2018-06-26 12:43:00 +08:00
)
vcpkg_configure_cmake(
SOURCE_PATH ${SOURCE_PATH}
PREFER_NINJA
)
vcpkg_install_cmake()
vcpkg_fixup_cmake_targets(CONFIG_PATH lib/cmake/sol2)
[sol2] Use the single header release (#8776) * [sol2] Use the single header release Using the single header release of the library is easier, faster to 'build', and is recommended by the documentation. It also fix the duplicated include folder issue of the previous port : <sol/sol/sol.hpp> can now be replaced with <sol/sol.hpp> as it should be. Is there any drawback about using the single header release that I am not seing? * [sol2] Re-enable cmake config files export * [sol2] Fix duplicated line
2019-10-31 09:13:43 +08:00
file(
REMOVE_RECURSE
${CURRENT_PACKAGES_DIR}/debug
${CURRENT_PACKAGES_DIR}/lib
${CURRENT_PACKAGES_DIR}/include
)
file(INSTALL ${SOURCE_PATH}/single/include/sol DESTINATION ${CURRENT_PACKAGES_DIR}/include/)
[sol2] rename port sol to sol2 and fix the full port (#3766) * [sol2] rename port sol to sol2 and fix the full port * [sol2] Simplification and cleanup. Don't remove upstream's include directory.
2018-06-26 12:43:00 +08:00
[sol2] Use the single header release (#8776) * [sol2] Use the single header release Using the single header release of the library is easier, faster to 'build', and is recommended by the documentation. It also fix the duplicated include folder issue of the previous port : <sol/sol/sol.hpp> can now be replaced with <sol/sol.hpp> as it should be. Is there any drawback about using the single header release that I am not seing? * [sol2] Re-enable cmake config files export * [sol2] Fix duplicated line
2019-10-31 09:13:43 +08:00
file(INSTALL ${SOURCE_PATH}/LICENSE.txt DESTINATION ${CURRENT_PACKAGES_DIR}/share/${PORT} RENAME copyright)
Reference in New Issue Copy Permalink