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

Reduce Library options by implementing a way to capture use case needs. #5301

Open
byrnHDF opened this issue Feb 7, 2025 · 0 comments
Open
Labels
Component - Build CMake, Autotools Component - Documentation Doxygen, markdown, etc. Component - Misc Anything else (CODEOWNERS, etc.) Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Deprecation / Removal We strive for backward-compatibility, so it's worth noting this separately Type - Improvement Improvements that don't add a new feature or functionality Type - New Feature Add a new API call, functionality, or tool
Milestone

Comments

@byrnHDF
Copy link
Contributor

byrnHDF commented Feb 7, 2025

Currently, there is the cacheinit.cmake file that captures the option settings for HDF testing use case. This file is used in builds that report to CDash and create the "StdShar" use case by default (other usual builds combine overrides of options in this file). Another, possibility would be to create targeted CMakeUserPresets.json files for use cases, but presets do not report to CDash.

There are also some HDF5 options and code that could be replaced with the correct settings/code in these "Use Case" files. Relocating them out of the HDF5 library build code would be beneficial in that the number options is reduced and, documented correctly, provides templates for users as well as use cases for HDF testing.

Ideally, this should be targeted for the 2.0 release, given the scope of the work and changes.

@byrnHDF byrnHDF added Component - Build CMake, Autotools Component - Documentation Doxygen, markdown, etc. Component - Misc Anything else (CODEOWNERS, etc.) Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Deprecation / Removal We strive for backward-compatibility, so it's worth noting this separately Type - Improvement Improvements that don't add a new feature or functionality Type - New Feature Add a new API call, functionality, or tool labels Feb 7, 2025
@byrnHDF byrnHDF added this to the Release 2.0.0 milestone Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - Build CMake, Autotools Component - Documentation Doxygen, markdown, etc. Component - Misc Anything else (CODEOWNERS, etc.) Priority - 1. High 🔼 These are important issues that should be resolved in the next release Type - Deprecation / Removal We strive for backward-compatibility, so it's worth noting this separately Type - Improvement Improvements that don't add a new feature or functionality Type - New Feature Add a new API call, functionality, or tool
Projects
None yet
Development

No branches or pull requests

1 participant