Order of named options to file(CONFIGURE) should not be fixed
The new file(CONFIGURE)
subcommand added in !4436 (merged) requires mandatory CONTENT
and OUTPUT
options. The current implementation requires that they be specified in a specific order, i.e. in exactly the following form:
file(CONFIGURE OUTPUT someFile CONTENT someString ...)
Because OUTPUT
and CONTENT
are named options, it should be possible to specify them in any order. This is more noticeable when you compare the forms of closely related commands where named arguments are not used but the required order is reversed:
configure_file(inputFile outputFile ...)
string(CONFIGURE inputString outputVar ...)
The implementation of file(CONFIGURE)
should be modified to use correct named argument processing and allow arbitrary order.