BUG: Fix Xcode per-config bundle name in Info.plist
- The Xcode generator creates one Info.plist input file which is converted at build time by Xcode and placed in the final bundle. - The <CONFIG>_OUTPUT_NAME target property can place different content for the exe name in Info.plist on a per-configuration basis. - Instead of generating a per-config Info.plist input file just let Xcode put the name in at build time using the $(EXECUTABLE_NAME) var.
This commit is contained in:
parent
7950b99d9d
commit
264af17bfc
|
@ -1480,8 +1480,12 @@ void cmGlobalXCodeGenerator::CreateBuildSettings(cmTarget& target,
|
||||||
plist += "/";
|
plist += "/";
|
||||||
plist += target.GetName();
|
plist += target.GetName();
|
||||||
plist += "Info.plist";
|
plist += "Info.plist";
|
||||||
|
// Xcode will create the final version of Info.plist at build time,
|
||||||
|
// so let it replace the executable name. This avoids creating
|
||||||
|
// a per-configuration Info.plist file.
|
||||||
this->CurrentLocalGenerator
|
this->CurrentLocalGenerator
|
||||||
->GenerateAppleInfoPList(&target, productName.c_str(), plist.c_str());
|
->GenerateAppleInfoPList(&target, "$(EXECUTABLE_NAME)",
|
||||||
|
plist.c_str());
|
||||||
std::string path =
|
std::string path =
|
||||||
this->ConvertToRelativeForXCode(plist.c_str());
|
this->ConvertToRelativeForXCode(plist.c_str());
|
||||||
buildSettings->AddAttribute("INFOPLIST_FILE",
|
buildSettings->AddAttribute("INFOPLIST_FILE",
|
||||||
|
|
Loading…
Reference in New Issue