The mechanism for executing commands that have a configuration specific output is complicated and bug-prone. Especcially the escaping of special characters is hard to get right. The mechanism was implemented as a workaround for the problem that add_custom_command() does not support generator expressions in its OUTPUT argument.
Maybe we can use mitigate the problem by.
Wrapping command lists with generator expressions. ; in generator expressions has become possible i think.
Executing multiple commands instead of one with many arguments, to get rid of argument file mechanism.
If cmake should implement generator expressions in OUTPUT we may able to get rid of this completely.
The mechanism for executing commands that have a configuration specific output is complicated and bug-prone. Especcially the escaping of special characters is hard to get right. The mechanism was implemented as a workaround for the problem that
add_custom_command()does not support generator expressions in itsOUTPUTargument. Maybe we can use mitigate the problem by.;in generator expressions has become possible i think.If cmake should implement generator expressions in
OUTPUTwe may able to get rid of this completely.