Skip to content

build: Introduce CMake-based build system #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

hebasto
Copy link
Member

@hebasto hebasto commented Oct 20, 2022

This PR introduces a new CMake-based build system, which can be reused in downstream projects, including Bitcoin Core.

Additionally, a GitHub Actions CI task for MSVC and clang-cl has been added, following this feedback.

Autotools vs CMake configuration option parity

Autotools CMake
--disable-ccache N/A
--enable-tests -DMINISKETCH_BUILD_TESTS
--enable-benchmark -DMINISKETCH_BUILD_BENCHMARK
--enable-fields=,-separated list -DMINISKETCH_FIELDS=;-separated list
-DMINISKETCH_INSTALL

Notes on the implementation

  1. The default CMAKE_BUILD_TYPE is left unset.

  2. CMake's per-configuration compiler flags are not modified. As a result, they may include -DNDEBUG.

  3. The target name test is reserved. Therefore, the testing binary has been renamed to test-noverify. Alternatively, following the naming used in the libsecp256k1 repo, the test binaries could be renamed as:

    • test --> noverify_tests
    • test-verify --> verify_tests

@hebasto
Copy link
Member Author

hebasto commented Oct 20, 2022

Chasing for Concept (N)ACKs...

@hebasto hebasto marked this pull request as ready for review October 23, 2022 08:02
@hebasto
Copy link
Member Author

hebasto commented Oct 23, 2022

The currently suggesting minimal CMake-based build system implementation is enough for:

add_subdirectory(minisketch EXCLUDE_FROM_ALL)
target_compile_definitions(minisketch
  PRIVATE
    DISABLE_DEFAULT_FIELDS
    ENABLE_FIELD_32
)

To became a full fledged one, the current minimal CMake-based build system requires some additional features:

  • more robustness (e.g., checking compiler/linker flags before applying them)
  • ability to install the built artifacts
  • ability to export the built artifacts and, probably, packaging of them
  • documentation

Although, those features are not required for this PR goal, i.e., providing a native Windows CI task.

@hebasto
Copy link
Member Author

hebasto commented Oct 31, 2022

Updated 5851544 -> d2408e0 (pr75.03 -> pr75.04, diff):

  • policy CMP0063 set explicitly to avoid CMake warnings
  • the default CMake build directory added to the .gitignore file

@theuni
Copy link
Contributor

theuni commented Mar 17, 2023

Imo this should be renamed "Add CMake buildsystem". I looked for this a while back and didn't find it because CMake isn't mentioned in the title.

Concept ACK. Will review next week.

@theuni
Copy link
Contributor

theuni commented Mar 31, 2023

@sipa Are you interested in CMake for this project?

@sipa
Copy link
Collaborator

sipa commented Mar 31, 2023

@theuni Yeah, will look soon.

@theuni
Copy link
Contributor

theuni commented Mar 31, 2023

@sipa No rush. I was just looking for a concept ACK.

I worked up a CMake impl as well before seeing this PR. I think we'd benefit from parts of each, so I'll get with @hebasto on creating a combined version for review.

@hebasto hebasto changed the title ci: Add "x86_64: Windows (VS 2022)" task build: Add CMake buildsystem Apr 16, 2023
@hebasto
Copy link
Member Author

hebasto commented Apr 16, 2023

Imo this should be renamed "Add CMake buildsystem".

Done.

@sipa
Copy link
Collaborator

sipa commented Apr 11, 2024

I'm happy to add a CMake build system for minisketch. I will need review from people more experienced with build systems, though.

@hebasto
Copy link
Member Author

hebasto commented Apr 11, 2024

I'm happy to add a CMake build system for minisketch. I will need review from people more experienced with build systems, though.

I'm going to update this PR shortly.

@hebasto hebasto force-pushed the 221019-ci-msvc branch 2 times, most recently from 66b4133 to b486457 Compare April 16, 2024 16:44
@hebasto
Copy link
Member Author

hebasto commented Apr 16, 2024

Reworked.

The PR description has been updated.

The approach from hebasto/bitcoin#93 was used for printing summary.

endif()

if(MINGW)
add_link_options(-static)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should port this functionality. Instead we should use the CMake shared/static selection machinery.

Copy link
Member Author

@hebasto hebasto Apr 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This affects only benchmark/test binaries and allows to run them on the build system via Wine when building either a static library or a shared one.

UPD. It also links libstdc++-6 to libminisketch.dll statically when cross-compiling for Windows and -DBUILD_SHARED_LIBS=YES is provided.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider

cmake -B build \
  -DCMAKE_BUILD_TYPE=Release \
  -DCMAKE_SYSTEM_NAME=Windows \
  -DCMAKE_CXX_COMPILER=x86_64-w64-mingw32-g++-posix
cmake --build build --target test
wine ./build/src/test.exe

or

cmake -B build \
  -DCMAKE_BUILD_TYPE=Release \
  -DCMAKE_SYSTEM_NAME=Windows \
  -DCMAKE_CXX_COMPILER=x86_64-w64-mingw32-g++-posix \
  -DBUILD_SHARED_LIBS=YES
cmake --build build --target test
wine ./build/src/test.exe

)

if(DEFINED CMAKE_CXX_STANDARD)
if(CMAKE_CXX_STANDARD EQUAL 98 OR CMAKE_CXX_STANDARD LESS 11)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hah! Stupid CMake :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Y2K problem :)

@hebasto
Copy link
Member Author

hebasto commented Apr 26, 2024

Addressed @theuni's comments.

@hebasto hebasto marked this pull request as draft March 5, 2025 14:14
@sipa
Copy link
Collaborator

sipa commented May 13, 2025

What is the status here?

@hebasto
Copy link
Member Author

hebasto commented May 13, 2025

What is the status here?

I'll push an update shortly.

@hebasto hebasto marked this pull request as ready for review June 1, 2025 01:09
@hebasto hebasto force-pushed the 221019-ci-msvc branch 2 times, most recently from 6d4c1cf to 43bbb56 Compare June 1, 2025 01:24
@hebasto hebasto changed the title build: Add CMake buildsystem build: Introduce CMake-based buildsystem Jun 1, 2025
@hebasto hebasto changed the title build: Introduce CMake-based buildsystem build: Introduce CMake-based build system Jun 1, 2025
@hebasto
Copy link
Member Author

hebasto commented Jun 1, 2025

Rebased.

PR description has been updated:

a GitHub Actions CI task for MSVC and clang-cl has been added

@sipa

Could you please enable Actions in this repository?

@@ -0,0 +1,116 @@
cmake_minimum_required(VERSION 3.22)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cmake_minimum_required() command does two things:

  1. Sets the minimum required version of CMake for the project.
  2. Sets the policy settings.

Rationale for point 1:

  • Minimum required version 3.22 allows to build on Ubuntu 22.04 LTS.
  • Same as in Bitcoin Core.

Rationale for point 2:

  • From Professional CMake: A Practical Guide, 21st Edition, Section 13.1:

    This gives projects confidence that developers should be able to update to any newer version of CMake at their convenience, and the project will still build as it did before.

Some other developers, namely @ryanofsky and @purpleKarrot, disagree.
See: bitcoin-core/libmultiprocess#163.

# ============================================================
# Project Initialization
# ============================================================
enable_testing()
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this is superior to include(CTest), as the latter has a few drawbacks.

Some other developers, namely @purpleKarrot, disagree.
See: bitcoin-core/libmultiprocess#145

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants