We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
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.
serial
Note: we definitely want to keep shared builds for the same combinations too (esp. Windows DLL exports are tricky and need coverage).
The text was updated successfully, but these errors were encountered:
The windows static builds will require work on the thirdparty GTkorvo libraries. I've started that.
Sorry, something went wrong.
I believe that his has been fixed in #4037 and #4041
pnorbert
No branches or pull requests
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:
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).
The text was updated successfully, but these errors were encountered: