CPack #33455

pull purpleKarrot wants to merge 4 commits into bitcoin:master from purpleKarrot:cpack changing 7 files +37 −257
  1. purpleKarrot commented at 2:28 pm on September 22, 2025: contributor

    The goal is to build all packages (both archives and installers) from a single configuration in CMake.

    Packaging Instruction

    Get a list of supported CPack generators for your platform with:

    0cpack --help
    

    Run cpack from the build directory after a successful build to select multiple package generators:

    0cmake --build .
    1cpack -G '7Z;NSIS64'
    

    Or build the package and/or package_source targets:

    0cmake --build . --target package
    1cmake --build . --target package_source
    

    TODO:

    • Windows start menu entries
    • Option to launch after install
    • Component descriptions / dependencies / groups
    • Auxiliary files (readme, config)
  2. cmake: Make sure that install components are c identifiers 5359386ca9
  3. cmake: Use CPack to build Windows installer 16fe6f253b
  4. DrahtBot commented at 2:28 pm on September 22, 2025: contributor

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    Code Coverage & Benchmarks

    For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/33455.

    Reviews

    See the guideline for information on the review process. A summary of reviews will appear here.

    Conflicts

    Reviewers, this pull request conflicts with the following ones:

    • #33247 (build: Remove CMAKE_SKIP_BUILD_RPATH and SKIP_BUILD_RPATH settings by 151henry151)
    • #31974 (Drop testnet3 by Sjors)
    • #30595 (kernel: Introduce initial C header API by TheCharlatan)

    If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

  5. cmake: set CPACK_SOURCE_IGNORE_FILES fb1da00f04
  6. ci: set GOAL to `package` for Windows fe2dd036f4
  7. hebasto commented at 1:05 pm on September 23, 2025: member

    Run cpack from the build directory after a successful build to select multiple package generators:

    0cmake --build .
    1cpack -G '7Z;NSIS64'
    

    Or build the package and/or package_source targets:

    0cmake --build . --target package
    1cmake --build . --target package_source
    

    Is the reproducibility of these commands guaranteed, or can it be enforced somehow?

    TODO:

    • Windows start menu entries

    • Option to launch after install

    • Component descriptions / dependencies / groups

    • Auxiliary files (readme, config)

    Adjust the Guix build script as well?


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-09-26 15:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me