Skip to content

Conversation

fanquake
Copy link
Member

Pulls the few changes from upstream (last commit ~ 2 years ago).
Seems reasonable to do before making any other changes. i.e #7, or if we are going to make further changes to the CMake build system etc.

pwnall and others added 7 commits August 30, 2021 19:11
* Fix Windows CI build.

The Windows SDK versions present on our CI options (GitHub Actions
hosted runners, AppVeyor) have headers that cause compilation warnings
when included with MSVC operating in modern C modes (C11+).

This PR disables the compilation warning caused by the Windows SDK
headers, so we can get Windows feedback from CI. The warnings can be
re-enabled when the Windows SDK used by our CI is upgraded to a version
that doesn't trigger warnings.

* Switch CI to GitHub Actions.
The Windows SDK versions present on our CI options (GitHub Actions
hosted runners, AppVeyor) have headers that cause compilation warnings
when included with MSVC operating in modern C modes (C11+).

This PR disables the compilation warning caused by the Windows SDK
headers, so we can get Windows feedback from CI. The warnings can be
re-enabled when the Windows SDK used by our CI is upgraded to a version
that doesn't trigger warnings.
Copy link
Member

@willcl-ark willcl-ark left a comment

Choose a reason for hiding this comment

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

The CI + CMakeLists.txt as they stand here are not worth adding: https://github.com/willcl-ark/crc32c-subtree/actions/runs/10605521278/job/29394471127

But tests and benches can be relatively easily hacked(1) out(2) to get an array of simple build tests passing again: https://github.com/willcl-ark/crc32c-subtree/actions/runs/10605602819

(I assume this is preferable to merging 3rd party deps).

The rest is trivial enough.

@@ -1,7 +1,6 @@
# CRC32C

[![Build Status](https://travis-ci.org/google/crc32c.svg?branch=master)](https://travis-ci.org/google/crc32c)
[![Build Status](https://ci.appveyor.com/api/projects/status/moiq7331pett4xuj/branch/master?svg=true)](https://ci.appveyor.com/project/pwnall/crc32c)
[![Build Status](https://github.com/google/crc32c/actions/workflows/build.yml/badge.svg)](https://github.com/google/crc32c/actions/workflows/build.yml)
Copy link
Member

Choose a reason for hiding this comment

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

This isn't correct for us, but can be fixed later

@fanquake
Copy link
Member Author

The point is just to pull the upstream changes. Any other (relevant) changes could be done in a followup.

@willcl-ark
Copy link
Member

Yes I agree, in this case it looks fine to me. 👍🏼

Ripping out the third party stuff from the CMakLists and CI is easy enough to do later.

@fanquake fanquake merged commit efb8ea0 into bitcoin-core:bitcoin-fork Aug 30, 2024
@fanquake fanquake deleted the sync_to_upstream branch August 30, 2024 10:11
fanquake added a commit to fanquake/bitcoin that referenced this pull request Aug 7, 2025
efb8ea04e4 Merge bitcoin-core/crc32c-subtree#8: Sync to upstream
4a7a05c48d Merge remote-tracking branch 'google/main' into bitcoin-fork
21fc8ef304 Fix typo (bitcoin#59)
89f69843a1 Fix misspelled "Proccess" in comment
02e65f4fd3 Bump deps (bitcoin#56)
b9d6e825a1 Fix Windows CI build. (bitcoin#54)
bbbb93ab5d Switch CI to GitHub Actions (bitcoin#55)
d46cd17d70 Add clangd cache directory to .gitignore.

git-subtree-dir: src/crc32c
git-subtree-split: efb8ea04e4a5b6a18dc4bc1908fd1cb2dcefb585
fanquake added a commit to bitcoin/bitcoin that referenced this pull request Aug 7, 2025
9a5d297 Squashed 'src/crc32c/' changes from b60d2b7334..efb8ea04e4 (fanquake)

Pull request description:

  Sync the subtree with latest upstream. The changes here are a no-op, but pull them to fix the drive-by-typo-fixing: #33057.

  Includes bitcoin-core/crc32c-subtree#8.

ACKs for top commit:
  maflcko:
    lgtm ACK 8ef8dd6
  janb84:
    ACK 8ef8dd6

Tree-SHA512: b20a47514218206b934c4aa27ec667fb9b3ec7f7388a78725c52fc6e916358d2b9a2075a37808dbc2430b4c7816511ecf20e36bfe2fbd2d8a26bc8882a46d5e7
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.

5 participants