Can be used to reduce the number of build actions that will be run in parallel by ParallelExecutor or TaskExecutor.
Example use, in MyProject.Target.cs:
public class MyProjectTarget : TargetRules
{
public MyProjectTarget(TargetInfo Target) : base(Target)
{
Type = TargetType.Game;
DefaultBuildSettings = BuildSettingsVersion.V2;
ExtraModuleNames.AddRange( new string[] { "MyProject" } );
MemoryPerActionGB = 4;
}
}
#jira none
[CL 17546182 by jonathan adamczewski in ue5-main branch]
TargetRules.File may be null in the TargetRules() constructor when run from AutomationTool.ProjectUtils.CompileAndLoadTargetsAssembly()
#jira none
#rb none
[CL 17379113 by jonathan adamczewski in ue5-main branch]
Make ConfigValueTracker immutable.
Propagate some nullability in and around TargetRules.
#jira none
#rb none
[CL 17377821 by jonathan adamczewski in ue5-main branch]
Frosty and Fortnite default to OFF.
Preflight validation runs: 611c2b645e73720001a4ccf3, 611c318caabad10001091e20,611c2ba99db7df000111041b
#rb chad.garyet
#jira UE-121664
#preflight 611d33b23a81b00001365b33
[CL 17218586 by Andrew Davidson in ue5-main branch]
Setting CustomConfig=Foo in a Target.cs file will cause it to overlay config files from Project/Config/Custom/Foo on top of the defaults, allowing easy override of things like OSS settings to support multiple stores
In development, -CustomConfig=foo can be specified in both C++ and C# to enable the same functionality, which can be used to select between multiple different stage/deploy configurations in a build script
#rb josh.adams, ben.marsh
[CL 17017130 by ben zeigler in ue5-main branch]
UnrealBuild -> Unreal for EngineDirectory, RootDirectory, IsEngineInstalled, UnrealBuildToolPath
Remove CommandUtils EngineDirectory, RootDirectory, IsEngineInstalled - use equvalents from UnrealBuildBase.Unreal
#jira none
[CL 16648181 by jonathan adamczewski in ue5-main 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
[CL 16607440 by jonathan adamczewski in ue5-main branch]
