ScmRevGen: Don't generate Info.plist files directly #13210
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some generators (like
Unix Makefiles
andXcode
) copy an app'sInfo.plist
at configure time. This causes a problem when we need to generate theInfo.plist
at build time, like how we currently do it with ScmRevGen.Instead of generating the
Info.plist
directly in ScmRevGen, provide anInfo.plist
without any version information to CMake at configure time, have ScmRevGen generate a separate plist file with the version information at build time, and then merge the two together to create the finalInfo.plist
.Fixes https://bugs.dolphin-emu.org/issues/13669.
(This PR also includes a bonus fix for codesigning in Xcode.)