Skip to content
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

Bump croaring to v2.1.2 #102

Merged
merged 4 commits into from
Jan 8, 2024
Merged

Conversation

SamHames
Copy link
Contributor

@SamHames SamHames commented Jan 3, 2024

Bumps croaring to the latest release amalgamation (v2.1.2, including bugfixes relating to shifts). This requires some changes in setup.py to get it to build correctly everywhere as the newer CRoaring versions now require atomic support.

Closes #104

Misc changes:

  • Bumps to the latest version of CIBuildWheel to build against release 3.12
  • Bumps testing matrix in github actions to run against release 3.12
  • Makes testing the CIBuildWheel actions a bit less frustrating by setting fail-fast=false - this just means failures on one platform wheel building don't cancel parallel platform jobs, but will prevent releasing to pypi.

I've confirmed that this builds wheels for all platforms too.

@SamHames SamHames changed the title WIP: Bump croaring to v2.1.0 Bump croaring to v2.1.1 Jan 4, 2024
CRoaring now requires atomic support (at least C11)
which is a little bit finicky across all platforms
to get the right flags through setuptools for both
CRoaring and Cython generated C++. This commit
splits out the CRoaring library into it's own section
separate to the Python extension to enable this.

Originally this was done for Windows as well, but
that lead to linker errors on Windows ARM wheel
builds...
3.12 is now officially released.

Also change the strategy for the CIBW job to not
fail-fast, so all platforms continue wheel building
even if one of them fails.
@SamHames SamHames changed the title Bump croaring to v2.1.1 Bump croaring to v2.1.2 Jan 4, 2024
@lemire
Copy link
Contributor

lemire commented Jan 5, 2024

the newer CRoaring versions now require atomic support.

I think that's not true because Visual Studio failed to provide atomic support with C11. And we support Visual Studio.

However, we do require C11.

@Ezibenroc
Copy link
Owner

Nice, good catch with this bug, thank you!

@Ezibenroc Ezibenroc merged commit 2786d16 into Ezibenroc:master Jan 8, 2024
18 checks passed
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.

Issues with shift
3 participants