The command name add_custom_target on Visual Studio generators will never be printed in the build logs, even with the highest verbosity settings. This makes it impossible to check the build logs to see if commands ran.

A similar issue theoretically exists for add_custom_command, but this can be worked around.

Workaround: Avoid running commands in add_custom_target. Instead, generate a file and use add_custom_command instead.