4be7cd09d6
If the project has a custom Info.plist assigned to QMAKE_INFO_PLIST, we should leave it as-is without scanning and replacing contents inside it. Since we always copy the file to the build folder at qmake time, any later attempts to modify the source file will not have any effect. A better solution is to just reference the custom plist directly from the Xcode, without modifying it. This change will also stop unixmake2 from assigning the default plist to QMAKE_INFO_PLIST, since we need to know in the xcode generator if the variable was set in the project or not. Task-number: QTBUG-38260 Change-Id: I3c488b2960170c544d94f9db89d3ca95ee290bdd Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@digia.com> |
||
---|---|---|
.. | ||
integrity | ||
mac | ||
unix | ||
win32 | ||
makefile.cpp | ||
makefile.h | ||
makefiledeps.cpp | ||
makefiledeps.h | ||
metamakefile.cpp | ||
metamakefile.h | ||
projectgenerator.cpp | ||
projectgenerator.h | ||
xmloutput.cpp | ||
xmloutput.h |