Switch to static linking and migrate Windows CI to MinGW #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Simplify the build process by statically linking `libbitcoinkernel` to produces more self-contained binaries with fewer moving parts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Simplify the build process by statically linking
libbitcoinkernelto produce more self-contained binaries with fewer moving parts. This requires migrating Windows CI from MSVC to MinGW/GCC:Previously, dynamic linking worked with MSVC because the C API provided a stable ABI boundary between compilers. However, static linking requires ABI compatibility between the library compiler and CGo's GCC toolchain on Windows, which MSVC does not provide. MinGW uses GCC, matching CGo's compiler and enabling static linking.