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

CI: All-Static builds (Linux/macOS/Win) #4025

Closed
ax3l opened this issue Feb 5, 2024 · 2 comments
Closed

CI: All-Static builds (Linux/macOS/Win) #4025

ax3l opened this issue Feb 5, 2024 · 2 comments
Assignees
Milestone

Comments

@ax3l
Copy link
Contributor

ax3l commented Feb 5, 2024

Downstream, it makes sense for some deployments (e.g., PyPA/pip of openPMD-api) to build an all-static ADIOS2 builds with all-static dependencies.

This often breaks in ADIOS2 #4019 #3898 #3716 #2747 #2454 #2316 #2576 #1810 ...

Could we add a CI entry for each Linux/macOS/Win that:

  • builds all ADIOS2 dependencies as static
  • builds ADIOS2 as static
  • does smoke tests?

Currently, we only have three static Linux builds in CI. I am not sure they also test dependencies like C-Blosc2 (static!).

For our use case, covering serial is sufficient.

Note: we definitely want to keep shared builds for the same combinations too (esp. Windows DLL exports are tricky and need coverage).

@pnorbert pnorbert self-assigned this Feb 5, 2024
@pnorbert pnorbert added this to the v2.10.0 milestone Feb 5, 2024
@eisenhauer
Copy link
Member

The windows static builds will require work on the thirdparty GTkorvo libraries. I've started that.

@vicentebolea
Copy link
Collaborator

I believe that his has been fixed in #4037 and #4041

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

No branches or pull requests

4 participants