clm merge requestshttps://gitlab.science.ru.nl/clean-and-itasks/clm/-/merge_requests2021-05-03T15:43:24+02:00https://gitlab.science.ru.nl/clean-and-itasks/clm/-/merge_requests/19Distinguish different compilation options in help and manpage2021-05-03T15:43:24+02:00Camil StapsDistinguish different compilation options in help and manpageWhen moving the documentation for `-ou`, `-fusion`, and `-generic_fusion` from project options to main module options I noticed that there were some other things out of place. I have tried to clarify this by distinguishing three differen...When moving the documentation for `-ou`, `-fusion`, and `-generic_fusion` from project options to main module options I noticed that there were some other things out of place. I have tried to clarify this by distinguishing three different kinds of compilation options:
- 'Compilation options' which are used whenever a module is recompiled but never trigger recompilation
- 'Project options' which are used whenever a module is recompiled *and* trigger recompilation of any module
- 'Main module options' which are used for the main module only and only trigger recompilation of that module
I have restructured the help and manpage to use this order, with more general options first, as well. And the 'Making a Clean project' section now explicitly refers to the different types of options.
I would expect that some options which are from my reading of the source code belong to the compilation options should actually belong to the main module options: `-ci`, `-desc`, and `-exl`. Should `generate_code_for_project_node` be changed for this?John van GroningenJohn van Groningen