-
Notifications
You must be signed in to change notification settings - Fork 25
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
ecbuild_print_summary reports options according to last project only #65
Comments
After a brief investigation, this is apparently one of the shortcomings of CMake ecBuild builds the summary information incrementally, and cannot a priori determine to which group ( One viable solution could be to let CMake do the usual grouping, while simply including a "marker" to identify if for some projects the feature has been used differently. This would result is having summaries like follows.
A more radical approach would be to force a feature to be grouped as @wdeconinck , @tlmquintino , what do you think would be the approach to follow here? |
- Add enabled/disabled features marker in project summary - Force once enabled features to be displayed as enabled, regardless of of any disabled use Re Github #65
- Add enabled/disabled features marker in project summary - Force once enabled features to be displayed as enabled, regardless of of any disabled use Re Github #65
- Add enabled/disabled features marker in project summary - Force once enabled features to be displayed as enabled, regardless of of any disabled use Re Github #65
- Add enabled/disabled features marker in project summary - Force once enabled features to be displayed as enabled, regardless of of any disabled use Re Github #65
- Add enabled/disabled features marker in project summary - Force once enabled features to be displayed as enabled, regardless of of any disabled use Re Github #65
@reuterbal this should now have been added to the develop branch and will be released in the coming week |
* gh/release/3.9.0: Version 3.9.0 Add downstream ci (#72) Fix ecbuild_disable_unused_feature Add workflow to check release version is correct (#54) Add ecbuild_override_compiler_flags macro Add utility to initialise overrideable compiler flags Add utility to purge compiler flags for a given language Add tests according to Github issue #65 Enable distinction between enabled/disabled features Update ci action to v2 (#68) Stricter match condition for _fail strings (#64) CPP out LOC calls for NAG.
What happened?
When a build is composed of multiple projects, e.g., as is the case with ecbundle, and more than one project uses an
ecbuild_add_option
with the same feature name, then the option can be toggled individually by setting<PROJ>_ENABLE_<FEATURE>
. However,ecbuild_print_summary
will report the status of these options according to the value of the last project, even if it is different for other projects.What are the steps to reproduce the bug?
Reproducer
CMakeLists.txt
:Dependent on setting the value of the variables
ENABLE_MYFEATURE
,PROJA_ENABLE_MYFEATURE
orPROJB_ENABLE_MYFEATURE
we would expect the option to be enabled for one or the other or both.The output is correct if both options have the same value, e.g.:
But is wrong when they have a different value, e.g., in the following example proja has the option disabled:
Or the other way round:
Version
3.8.3
Platform (OS and architecture)
Atos AC
Relevant log output
No response
Accompanying data
No response
Organisation
ECMWF
The text was updated successfully, but these errors were encountered: