- A new property on TargetRules allows a target to define any number of plugins that are allowed to be depended upon, even though a plugin may not explicitly state their dependency in the plugin descriptor
- This is useful for some projects where the inclusion of a plugin can only be made as part of a Target.cs file or Build.cs file
#rb Ben.Marsh
#preflight 61969a693139325be1735ace
#ROBOMERGE-AUTHOR: andrew.rodham
#ROBOMERGE-SOURCE: CL 18242765 via CL 18244980 via CL 18245064 via CL 18245123 via CL 18246341 via CL 18246380
#ROBOMERGE-BOT: STARSHIP (Release-Engine-Staging -> Release-Engine-Test) (v895-18170469)
[CL 18246401 by andrew rodham in ue5-release-engine-test branch]
This represents UE4/Main @18073326, Release-5.0 @18081140 and Dev-PerfTest @18045971
[CL 18081471 by aurel cordonnier in ue5-release-engine-test branch]
This represents UE4/Main @17774255, Release-5.0 @17791557 and Dev-PerfTest @17789485
[CL 17794212 by aurel cordonnier in ue5-release-engine-test branch]
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
#ROBOMERGE-AUTHOR: jonathan.adamczewski
#ROBOMERGE-SOURCE: CL 17546182 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v870-17433530)
[CL 17546186 by jonathan adamczewski in ue5-release-engine-test branch]
#ROBOMERGE-SOURCE: CL 17394491 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v865-17346139)
[CL 17394493 by ben marsh in ue5-release-engine-test branch]
TargetRules.File may be null in the TargetRules() constructor when run from AutomationTool.ProjectUtils.CompileAndLoadTargetsAssembly()
#jira none
#rb none
#ROBOMERGE-SOURCE: CL 17379113 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v865-17346139)
[CL 17379133 by jonathan adamczewski 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]
#rb helge.mathee
#jira na
#ROBOMERGE-SOURCE: CL 17234270 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v855-17104924)
[CL 17234282 by sara schvartzman in ue5-release-engine-test branch]
#ROBOMERGE-SOURCE: CL 17205235 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v855-17104924)
[CL 17205246 by andrew davidson in ue5-release-engine-test 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
#ROBOMERGE-SOURCE: CL 17017130 in //UE5/Main/...
#ROBOMERGE-BOT: STARSHIP (Main -> Release-Engine-Test) (v839-17012307)
[CL 17017144 by ben zeigler in ue5-release-engine-test branch]
