This is to support cases where there may be more than one UnrealTargetPlatform requiring the same VS Solution Platform. Without a distinct separation these platforms will overwrite each other's properties.
#jira UE-129637
#rnx
#rb Eric.McDaniel
#preflight 61e13f41341d372424fda39b
#ROBOMERGE-AUTHOR: david.harvey
#ROBOMERGE-SOURCE: CL 18615646 in //UE5/Release-5.0/... via CL 18615669 via CL 18615678
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v899-18417669)
[CL 18615693 by david harvey in ue5-main branch]
Variable, function and class renames only. XML-facing variables included deprecated support for the old names.
Renaming of the MasterProjectName.txt file will be handled in a subsequent change.
#jira none
#preflight 61d8a162ec35d1b940f74818
#ROBOMERGE-AUTHOR: jonathan.adamczewski
#ROBOMERGE-SOURCE: CL 18550269 in //UE5/Release-5.0/... via CL 18550308
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v899-18417669)
[CL 18550325 by jonathan adamczewski in ue5-release-engine-test branch]
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 18407429 via CL 18407445 via CL 18434902 via CL 18437289
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v897-18405271)
[CL 18437344 by rex hill in ue5-release-engine-test branch]
#rb dave.belanger
[FYI] Jonathan.Adamczewski
#preflight 61b0cdbf7177ccd1a12fe73e
#ROBOMERGE-OWNER: rex.hill
#ROBOMERGE-AUTHOR: rex.hill
#ROBOMERGE-SOURCE: CL 18406142 via CL 18406661 via CL 18407277 via CL 18407281 via CL 18434891 via CL 18437287
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v897-18405271)
[CL 18437342 by rex hill in ue5-release-engine-test branch]
Make ConfigValueTracker immutable.
Propagate some nullability in and around TargetRules.
#jira none
#rb none
#ROBOMERGE-SOURCE: CL 17377821 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v865-17346139)
[CL 17377828 by jonathan adamczewski in ue5-release-engine-test branch]
#ROBOMERGE-SOURCE: CL 16894546 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v836-16769935)
[CL 16894553 by ben marsh in ue5-release-engine-test branch]
#ROBOMERGE-SOURCE: CL 16883248 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v836-16769935)
[CL 16883253 by ben marsh in ue5-release-engine-test branch]
#ROBOMERGE-SOURCE: CL 16642197 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v833-16641396)
[CL 16642206 by jonathan adamczewski in ue5-release-engine-test branch]
RootDirectory, EngineDirectory, UnrealBuildToolPath are now found in BuildUtilities' UnrealBuild namesapce.
The way these are computed has changed. Previously, it was assumed that the application is UnrealBuildTool, and paths were constructed relative to that assembly.
Now, the assumption is that the process is located under a "Engine/Build/DotNET" sub-path and paths are constructed relative to that.
#jira none
#ROBOMERGE-SOURCE: CL 16607440 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v828-16531559)
[CL 16607455 by jonathan adamczewski in ue5-release-engine-test branch]
Default is still VS2019, running `GenerateProjectFiles.bat -2022` will create a solution and projects that pass -2022 to UnrealBuild tool when compiling from Visual Studio to force it to use the 2022 toolchain.
Please note, as the defaults are unchanged building from UnrealGameSync will still compile with VS2019 so I would disable that build if testing VS2022.
None of this is necessary to use VS2022, it can open VS2019 solutions and will use the Vs2019 toolchain to build.
#rb Ben.Marsh
#pf 60aebccd7d4b9f0001197729
[CL 16478477 by Joe Kirchoff in ue5-main branch]
