mirror/vcpkg
1
0
Fork 0
mirror of https://github.com/microsoft/vcpkg.git synced 2024-11-28 03:59:02 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
e0c3408c77
vcpkg/ports/capstone/portfile.cmake

53 lines
1.8 KiB
CMake
Raw Normal View History

Adding Capstone port
2017-10-24 01:06:32 +08:00
vcpkg_from_github(
OUT_SOURCE_PATH SOURCE_PATH
[capstone] update to 5.0.0-rc2 (#23979) * [capstone] update to 5.0.0 alpha * [triton] upgrade to support capstone 5 * [triton] fix incorrect library linkage * [triton] bump port version * [capstone] Silence CRT Secure Function warning * [capstone] update to 5.0.0-rc2 Co-authored-by: MACHIZAUD Andréa <andrea.machizaud@adobe.com>
2022-04-09 06:32:16 +08:00
REPO "capstone-engine/capstone"
[tracy] Add Tracy `profiler` and `capture` tools using project files (#24091) * [tracy] Add Tracy `profiler` and `capture` tools * [tracy] Linux supports * [capstone] fix non-installed pkg-config * [tracy] supports for capstone (including pkgconfig support) * [tracy] Add license * [tracy] fix OSX * [tracy] tools cannot be built on x86 Windows * [tracy] do not build tools by default * [tracy] Fix case * [tracy] fix vcpkg copyright location convention * Apply suggestions from code review Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com> * Finish code for code review suggestions * Use `vcpkg_build_make` instead of `vcpkg_execute_build_process` * Apply suggestions from code review Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com> * Workaround Windows cl complaint about `nodiscard` * Use tools bundle rather than individual tools in features * [capstone] Upgrade port after capstone-engine/capstone#1870 merge Co-authored-by: MACHIZAUD Andréa <andrea.machizaud@adobe.com> Co-authored-by: Jack·Boos·Yu <47264268+JackBoosY@users.noreply.github.com>
2022-04-21 05:51:12 +08:00
REF 000561b4f74dc15bda9af9544fe714efda7a6e13 # 5.0.0-rc2
SHA512 66b09a7d2fda297836bbedaeece71dcfe39bdbd633d9b6ecb68ee2e5aa094b697226136ab172cdc4550e8b2ef1448d001c8ee4e0d456c6d277afe0b3d1aab5a1
[capstone] update to 5.0.0-rc2 (#23979) * [capstone] update to 5.0.0 alpha * [triton] upgrade to support capstone 5 * [triton] fix incorrect library linkage * [triton] bump port version * [capstone] Silence CRT Secure Function warning * [capstone] update to 5.0.0-rc2 Co-authored-by: MACHIZAUD Andréa <andrea.machizaud@adobe.com>
2022-04-09 06:32:16 +08:00
HEAD_REF next
PATCHES
001-silence-windows-crt-secure-warnings.patch
Adding Capstone port
2017-10-24 01:06:32 +08:00
)
[capstone] Use static runtime if capstone wants to be statically linked (#23122) * Use static runtime if capstone wants to be statically linked This makes more sense than using the shared runtime if building a static version * increase port-version * Update version database * select CRT as new feature * don't use upercase in feature name * format json * run x-add-version * remove extra space Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> * run x-add-version * Modernize the port file.cmake * update version * checking feature per OS * update versioning * remove check for static CRT on windows so it doesn't conflict with other ports (Triton) * update versioning * use VCPKG_CRT_LINKAGE instead of feature for CRT * update versioning Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> Co-authored-by: Jonliu1993 <13720414433@163.com>
2022-02-23 06:08:20 +08:00
string(COMPARE EQUAL "${VCPKG_CRT_LINKAGE}" "static" STATIC_CRT)
[capstone] Update Capstone to v4.0.1-49-ge3d5a594 (#5546) * Update Capstone to v4.0.1-49-ge3d5a594 * Use full SHA hash for ref * Build Capstone with dynamic runtime * Update Capstone to 4.0.1-57-g120373dc * Fix wrong description for osxkernel feature
2019-03-15 14:14:05 +08:00
[Many ports] fix invalid character in feature name (#12306)
2020-07-09 05:02:34 +08:00
vcpkg_check_features(OUT_FEATURE_OPTIONS FEATURE_OPTIONS
[rollup] Rollup PR 2021-07-16 (#19001) * [rollup:2021-07-16 1/7] PR #18201 (@JackBoosY) [vcpkg-cmake] Add check for unused cmake variables * [rollup:2021-07-16 2/7] PR #18397 (@strega-nil) [vcpkg_list] add new function * [rollup:2021-07-16 3/7] PR #18782 (@strega-nil) [scripts-audit] vcpkg_build_ninja * [rollup:2021-07-16 4/7] PR #18784 (@strega-nil) [scripts-audit] vcpkg_minimum_required * [rollup:2021-07-16 5/7] PR #18785 (@strega-nil) [scripts-audit] vcpkg_replace_string * [rollup:2021-07-16 6/7] PR #18786 (@strega-nil) [scripts-audit] windows scripts * [rollup:2021-07-16 7/7] PR #18945 (@strega-nil) [many ports] remove deprecated vcpkg_check_features call [1/5] Co-authored-by: nicole mazzuca <mazzucan@outlook.com> Co-authored-by: PhoebeHui <20694052+PhoebeHui@users.noreply.github.com>
2021-07-21 01:24:58 +08:00
FEATURES
"arm" CAPSTONE_ARM_SUPPORT
"arm64" CAPSTONE_ARM64_SUPPORT
"evm" CAPSTONE_EVM_SUPPORT
"m680x" CAPSTONE_M680X_SUPPORT
"m68k" CAPSTONE_M68K_SUPPORT
"mips" CAPSTONE_MIPS_SUPPORT
"osxkernel" CAPSTONE_OSXKERNEL_SUPPORT
"ppc" CAPSTONE_PPC_SUPPORT
"sparc" CAPSTONE_SPARC_SUPPORT
"sysz" CAPSTONE_SYSZ_SUPPORT
"tms320c64x" CAPSTONE_TMS320C64X_SUPPORT
"x86" CAPSTONE_X86_SUPPORT
"x86-reduce" CAPSTONE_X86_REDUCE
"xcore" CAPSTONE_XCORE_SUPPORT
"diet" CAPSTONE_BUILD_DIET
[Many ports] fix invalid character in feature name (#12306)
2020-07-09 05:02:34 +08:00
)
[capstone] Add version. Support shared builds
2017-10-26 07:51:18 +08:00
[capstone] Use static runtime if capstone wants to be statically linked (#23122) * Use static runtime if capstone wants to be statically linked This makes more sense than using the shared runtime if building a static version * increase port-version * Update version database * select CRT as new feature * don't use upercase in feature name * format json * run x-add-version * remove extra space Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> * run x-add-version * Modernize the port file.cmake * update version * checking feature per OS * update versioning * remove check for static CRT on windows so it doesn't conflict with other ports (Triton) * update versioning * use VCPKG_CRT_LINKAGE instead of feature for CRT * update versioning Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> Co-authored-by: Jonliu1993 <13720414433@163.com>
2022-02-23 06:08:20 +08:00
if ("osxkernel" IN_LIST FEATURES AND NOT VCPKG_TARGET_IS_OSX)
message(FATAL_ERROR "Feature 'osxkernel' only supported in OSX")
endif()
vcpkg_cmake_configure(
SOURCE_PATH "${SOURCE_PATH}"
Adding Capstone port
2017-10-24 01:06:32 +08:00
OPTIONS
-DCAPSTONE_BUILD_TESTS=OFF
[capstone] Update Capstone to v4.0.1-49-ge3d5a594 (#5546) * Update Capstone to v4.0.1-49-ge3d5a594 * Use full SHA hash for ref * Build Capstone with dynamic runtime * Update Capstone to 4.0.1-57-g120373dc * Fix wrong description for osxkernel feature
2019-03-15 14:14:05 +08:00
-DCAPSTONE_BUILD_CSTOOL=OFF
[capstone] Use static runtime if capstone wants to be statically linked (#23122) * Use static runtime if capstone wants to be statically linked This makes more sense than using the shared runtime if building a static version * increase port-version * Update version database * select CRT as new feature * don't use upercase in feature name * format json * run x-add-version * remove extra space Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> * run x-add-version * Modernize the port file.cmake * update version * checking feature per OS * update versioning * remove check for static CRT on windows so it doesn't conflict with other ports (Triton) * update versioning * use VCPKG_CRT_LINKAGE instead of feature for CRT * update versioning Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> Co-authored-by: Jonliu1993 <13720414433@163.com>
2022-02-23 06:08:20 +08:00
-DCAPSTONE_BUILD_STATIC_RUNTIME=${STATIC_CRT}
[Many ports] fix invalid character in feature name (#12306)
2020-07-09 05:02:34 +08:00
${FEATURE_OPTIONS}
Adding Capstone port
2017-10-24 01:06:32 +08:00
)
[capstone] Use static runtime if capstone wants to be statically linked (#23122) * Use static runtime if capstone wants to be statically linked This makes more sense than using the shared runtime if building a static version * increase port-version * Update version database * select CRT as new feature * don't use upercase in feature name * format json * run x-add-version * remove extra space Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> * run x-add-version * Modernize the port file.cmake * update version * checking feature per OS * update versioning * remove check for static CRT on windows so it doesn't conflict with other ports (Triton) * update versioning * use VCPKG_CRT_LINKAGE instead of feature for CRT * update versioning Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> Co-authored-by: Jonliu1993 <13720414433@163.com>
2022-02-23 06:08:20 +08:00
vcpkg_cmake_install()
[capstone] Add version. Support shared builds
2017-10-26 07:51:18 +08:00
vcpkg_copy_pdbs()
[capstone] update to 5.0.0-rc2 (#23979) * [capstone] update to 5.0.0 alpha * [triton] upgrade to support capstone 5 * [triton] fix incorrect library linkage * [triton] bump port version * [capstone] Silence CRT Secure Function warning * [capstone] update to 5.0.0-rc2 Co-authored-by: MACHIZAUD Andréa <andrea.machizaud@adobe.com>
2022-04-09 06:32:16 +08:00
vcpkg_cmake_config_fixup(CONFIG_PATH lib/cmake/${PORT})
vcpkg_fixup_pkgconfig()
Adding Capstone port
2017-10-24 01:06:32 +08:00
[capstone] Use static runtime if capstone wants to be statically linked (#23122) * Use static runtime if capstone wants to be statically linked This makes more sense than using the shared runtime if building a static version * increase port-version * Update version database * select CRT as new feature * don't use upercase in feature name * format json * run x-add-version * remove extra space Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> * run x-add-version * Modernize the port file.cmake * update version * checking feature per OS * update versioning * remove check for static CRT on windows so it doesn't conflict with other ports (Triton) * update versioning * use VCPKG_CRT_LINKAGE instead of feature for CRT * update versioning Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> Co-authored-by: Jonliu1993 <13720414433@163.com>
2022-02-23 06:08:20 +08:00
file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")
Adding Capstone port
2017-10-24 01:06:32 +08:00
[capstone] Use static runtime if capstone wants to be statically linked (#23122) * Use static runtime if capstone wants to be statically linked This makes more sense than using the shared runtime if building a static version * increase port-version * Update version database * select CRT as new feature * don't use upercase in feature name * format json * run x-add-version * remove extra space Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> * run x-add-version * Modernize the port file.cmake * update version * checking feature per OS * update versioning * remove check for static CRT on windows so it doesn't conflict with other ports (Triton) * update versioning * use VCPKG_CRT_LINKAGE instead of feature for CRT * update versioning Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> Co-authored-by: Jonliu1993 <13720414433@163.com>
2022-02-23 06:08:20 +08:00
file(INSTALL "${SOURCE_PATH}/LICENSE.TXT" DESTINATION "${CURRENT_PACKAGES_DIR}/share/${PORT}" RENAME copyright)
Reference in New Issue Copy Permalink