Add config_summary to Spiner. - #103
Conversation
|
I ran into this issue elsewhere (for example lanl/ports-of-call#65), and the issue is probably that we need to export the version flag to the parent scope. But I may have to play with things a bit to get |
|
@BrendanKKrueger I'm sorry to have neglected this so long. This would be great to include. Is it ready to go? |
Diego and I have made some changes since this branch was last updated. I don't recall the details, but updating to match the latest version in Nautilus (Singe, Nautilus, and SuNRe generally are consistent with each other).
|
@Yurlungur currently you get the following: Would you like this to be tweaked or modified or expanded in any way to be more useful for Spiner's specific settings? |
It looks to me like you already include all the options in the build? So that looks good to me. I also don't want to let the perfect be the enemy of the good. |
PR Summary
As with Ports-of-Call:
config_summarystuff is something we put together for Singe because we've found it useful in other projects. If you're not interested in adding this to Spiner, feel free to close this MR.config_summaryand may not be set up the way you like. Feel free to tweak it or ask me to adjust things.I'm not positive, but it seems like
spiner_content_declaremay not be setting up the<packagename>_VERSIONvariables, which causes the output fromconfig_summaryto look weird. This may suggest I need to fixconfig_summary, someone needs to fixspiner_content_declare, or Spiner just shouldn't mix the two together.Example screenshot of

config_summaryoutput:PR Checklist