#1510 Rename dunecontrol commands "make" and "all"
|Reported by||Christoph Grüninger (email@example.com)|
|Reported at||Oct 8, 2014 10:06|
|Version||Git (pre2.4) [autotools]|
|Operating System||Unspecified / All|
|Last edited by||Christoph Grüninger (firstname.lastname@example.org)|
|Last edited at||Jul 27, 2015 07:11|
|Closed by||Christoph Grüninger (email@example.com)|
|Closed at||Jul 27, 2015 07:11|
|Closed in version||Unknown|
|Comment||Maybe we want to do this in the future. Currently we hope to get rid of dunecontrol within the next release cycle.|
Whenever I explain dunecontrol to people, who have never written their own make files, they have difficulties to grasp the meaning of the command names.
I propose to introduce new command names for Dune 2.4 and remove the old ones together with autotools after Dune 2.4.
"autogen" is a technical term from autotools. It will vanish anyway as CMake does not require it.
"configure" seems fine to me, CMake calls it the same.
"make" is only obvious if you have ever used make. For clarification and because other build tools are possible with CMake, I propose "build" as a substitute.
"all" is a usual make target name. But it is often confused with building all modules. Unfortunately there is no catchy name. Proposals are "full", "complete", "entire", "whole". Or we stick to "all" but take it as a default in the case no argument is given.
What do you think?