Add messaging when generating if the default solution must be downgraded to VS2019 due to a platform that does not support VS2022
Unban 17.3-14.33
#rb Francis.Hurteau
#rb Josh.Adams
#preflight 63080ed91670d55ad5de0945
#preflight 630fb22c660db81edbbe7d12
[CL 21728329 by Joe Kirchoff in ue5-main branch]
#fyi Joe.Kirchoff
#rnx
Original CL Desc
-----------------------------------------------------------------
UnrealBuildTool: Ignore VCProjectFileSettings.MaxSharedIncludePaths for VS2022
#rnx
#rb none
#preflight 62b62e6fa072cea0b5989414
#preflight 62b9b58bba62f4498a3209c2
[CL 20830204 by Tim Smith in ue5-main branch]
- Don't make solution folders if there are no projects anywhere in them
- Fixed MemProfiler2.csproj to open on VSMac (although now with the above it is skipped anyway because it requires windows - but if we make it not require windows, we'd need this fix to match what UBT does)
#jira none
#rb tim.smith
#preflight 6255a8bfcd5ed4dd091a8ece
[CL 19725910 by Josh Adams in ue5-main branch]
-The build machine was trying to use a locally installed toolchain that did not have the arm64 toolchain installed.
-We now identify toolchains with arm64 support and select from only those for arm64 builds.
#rb Joe.Kirchoff, Josh.Adams
#jira UE-136919
#preflight
#ROBOMERGE-AUTHOR: jeff.fisher
#ROBOMERGE-SOURCE: CL 18665835 in //UE5/Release-5.0/... via CL 18665840 via CL 18665864
#ROBOMERGE-BOT: UE5 (Release-Engine-Test -> Main) (v901-18665521)
[CL 18665888 by jeff fisher 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]
#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]
This represents UE4/Main @17911760, Release-5.0 @17915875 and Dev-PerfTest @17914035
[CL 17918595 by aurel cordonnier 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]
