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

30 lines
803 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
vcpkg_from_github(
OUT_SOURCE_PATH SOURCE_PATH
REPO ThePhD/sol2
[sol2] Update to 3.2.2 (#13876) https://github.com/ThePhD/sol2/releases/tag/v3.2.2 Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
2020-10-07 00:24:25 +08:00
REF v3.2.2
SHA512 e5a739b37aea7150f141f6a003c2689dd33155feed5bb3cf2569abbfe9f0062eacdaaf346be523d627f0e491b35e68822c80e1117fa09ece8c9d8d5af09fdbec
[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)
[many ports] call vcpkg_fixup_pkgconfig() (#20953) * [many ports] call vcpkg_fixup_pkgconfig() The ports generate pc files, but don't call vcpkg_fixup_pkgconfig() so that there are absolute paths in the pc files * Update port-version for armadillo and polyclipping. * Update version database. Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
2021-10-28 06:19:28 +08:00
vcpkg_fixup_pkgconfig()
Reference in New Issue Copy Permalink