3party/vcpkg
0
0
Fork 0
mirror of https://github.com/microsoft/vcpkg.git synced 2024-12-27 02:11:58 +08:00
Code Issues Projects Releases Wiki Activity
vcpkg/ports/bddisasm/portfile.cmake

30 lines
912 B
CMake
Raw Permalink Normal View History

[bddisasm] new port (#18046) * Add bddisasm port Currently fetching bddisasm from my fork of the project * bddisasm: Build with BDD_INCLUDE_TOOL=OFF * bddisasm: Use PREFER_NINJA * bddisasm: Update REF * bddisasm: Don't use vcpkg_install_msbuild * bddisasm: Switch to release 1.32.1 from the bitdefender repo * Add the result of ./vcpkg x-add-version --all * Replace the control file with a manifest Converted with ./vcpkg format-manifest * Add more details to bddisasm/vcpkg.json Added port-version, license, homepage, documentation, and port mantainers * Fix bddisasm/vcpkg.json * Fix the version file * List arm as not supported * Update version file * Fail install on arm * Use the new vcpkg_cmake_* functions * Remove the LICENSE file * Fix version * Update version file * build only static library bddisasm only supports being built as a static library, so say that in the portfile Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
2021-06-03 23:13:15 +03:00
vcpkg_check_linkage(ONLY_STATIC_LIBRARY)
vcpkg_from_github(
OUT_SOURCE_PATH SOURCE_PATH
REPO bitdefender/bddisasm
[bddisasm] Update to 2.1.0 (#36917) ## Checklist - [x] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md). - [x] SHA512s are updated for each updated download. - [x] The "supports" clause reflects platforms that may be fixed by this new version. - [ ] ~Any fixed [CI baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt) entries are removed from that file.~ - [ ] ~Any patches that are no longer applied are deleted from the port's directory.~ - [x] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result. - [x] Only one version is added to each modified port's versions file. I'm not entirely sure that I did the right thing. Previous versions were having troubles building on arm, so they specified `"supports": "!arm"` in `vcpkg.json`. These issues should be fixed now, although I had minimal access to ARM devices/cross compilation tools to properly test this. Should I add an explicit list of supported platforms instead?
2024-02-27 10:27:30 +02:00
REF "v${VERSION}"
[bddisasm] Bump to 2.2.0 (#42890)
2024-12-24 01:37:50 +08:00
SHA512 5c1b8b8b9a29db76ce6197674e662fdc526e89372a84f7fac8e74cf4cc53bfab8d55c096cdb3f344fcfaa6a4d54a5bef79e8f1cf9131e497636072523b2cf3ec
[bddisasm] new port (#18046) * Add bddisasm port Currently fetching bddisasm from my fork of the project * bddisasm: Build with BDD_INCLUDE_TOOL=OFF * bddisasm: Use PREFER_NINJA * bddisasm: Update REF * bddisasm: Don't use vcpkg_install_msbuild * bddisasm: Switch to release 1.32.1 from the bitdefender repo * Add the result of ./vcpkg x-add-version --all * Replace the control file with a manifest Converted with ./vcpkg format-manifest * Add more details to bddisasm/vcpkg.json Added port-version, license, homepage, documentation, and port mantainers * Fix bddisasm/vcpkg.json * Fix the version file * List arm as not supported * Update version file * Fail install on arm * Use the new vcpkg_cmake_* functions * Remove the LICENSE file * Fix version * Update version file * build only static library bddisasm only supports being built as a static library, so say that in the portfile Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
2021-06-03 23:13:15 +03:00
HEAD_REF master
)
vcpkg_cmake_configure(
SOURCE_PATH ${SOURCE_PATH}
OPTIONS
-DBDD_INCLUDE_TOOL=OFF
)
vcpkg_cmake_install()
[bddisasm] Update to 2.1.4 (#38753) Update `bddisasm` to the latest version 2.1.4. - [x] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md). - [x] SHA512s are updated for each updated download. - [ ] ~The "supports" clause reflects platforms that may be fixed by this new version.~ - [ ] ~Any fixed [CI baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt) entries are removed from that file.~ - [ ] ~Any patches that are no longer applied are deleted from the port's directory.~ - [x] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result. - [x] Only one version is added to each modified port's versions file.
2024-05-17 09:53:42 +08:00
vcpkg_install_copyright(FILE_LIST "${SOURCE_PATH}/LICENSE")
[bddisasm] new port (#18046) * Add bddisasm port Currently fetching bddisasm from my fork of the project * bddisasm: Build with BDD_INCLUDE_TOOL=OFF * bddisasm: Use PREFER_NINJA * bddisasm: Update REF * bddisasm: Don't use vcpkg_install_msbuild * bddisasm: Switch to release 1.32.1 from the bitdefender repo * Add the result of ./vcpkg x-add-version --all * Replace the control file with a manifest Converted with ./vcpkg format-manifest * Add more details to bddisasm/vcpkg.json Added port-version, license, homepage, documentation, and port mantainers * Fix bddisasm/vcpkg.json * Fix the version file * List arm as not supported * Update version file * Fail install on arm * Use the new vcpkg_cmake_* functions * Remove the LICENSE file * Fix version * Update version file * build only static library bddisasm only supports being built as a static library, so say that in the portfile Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
2021-06-03 23:13:15 +03:00
vcpkg_cmake_config_fixup(CONFIG_PATH lib/cmake/bddisasm)
file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")
file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/share")
file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/bin" "${CURRENT_PACKAGES_DIR}/debug/bin")
[bddisasm] Update to 1.34.7 (#21130) * Add bddisasm port Currently fetching bddisasm from my fork of the project * bddisasm: Build with BDD_INCLUDE_TOOL=OFF * bddisasm: Use PREFER_NINJA * bddisasm: Update REF * bddisasm: Don't use vcpkg_install_msbuild * bddisasm: Switch to release 1.32.1 from the bitdefender repo * Add the result of ./vcpkg x-add-version --all * Replace the control file with a manifest Converted with ./vcpkg format-manifest * Add more details to bddisasm/vcpkg.json Added port-version, license, homepage, documentation, and port mantainers * Fix bddisasm/vcpkg.json * Fix the version file * List arm as not supported * Update version file * Fail install on arm * Use the new vcpkg_cmake_* functions * Remove the LICENSE file * Fix version * Update version file * build only static library bddisasm only supports being built as a static library, so say that in the portfile * bddisasm: Update port to version 1.33.0 * bddisasm: Update port to version 1.34.2 * bddisasm: Update port to version 1.34.7 * bddisasm: Set `port-version` to 1 * Update ports/bddisasm/vcpkg.json Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com> * Run `vcpkg x-add-version --all` Co-authored-by: nicole mazzuca <mazzucan@outlook.com> Co-authored-by: JonLiu1993 <63675417+JonLiu1993@users.noreply.github.com>
2021-11-04 19:48:06 +02:00
vcpkg_fixup_pkgconfig()
[bddisasm] Update to 2.1.0 (#36917) ## Checklist - [x] Changes comply with the [maintainer guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md). - [x] SHA512s are updated for each updated download. - [x] The "supports" clause reflects platforms that may be fixed by this new version. - [ ] ~Any fixed [CI baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt) entries are removed from that file.~ - [ ] ~Any patches that are no longer applied are deleted from the port's directory.~ - [x] The version database is fixed by rerunning `./vcpkg x-add-version --all` and committing the result. - [x] Only one version is added to each modified port's versions file. I'm not entirely sure that I did the right thing. Previous versions were having troubles building on arm, so they specified `"supports": "!arm"` in `vcpkg.json`. These issues should be fixed now, although I had minimal access to ARM devices/cross compilation tools to properly test this. Should I add an explicit list of supported platforms instead?
2024-02-27 10:27:30 +02:00
file(INSTALL "${CMAKE_CURRENT_LIST_DIR}/usage" DESTINATION "${CURRENT_PACKAGES_DIR}/share/${PORT}")
Reference in New Issue Copy Permalink