Changes to make new Clang in Xcode 11 beta compile the engine witout warnings
#jira UE-77043
#ROBOMERGE-OWNER: michael.trepka
#ROBOMERGE-AUTHOR: michael.trepka
#ROBOMERGE-SOURCE: CL 7627878 via CL 7627884 via CL 7636118
#ROBOMERGE-BOT: (v372-7473910)
[CL 7636120 by michael trepka in Main branch]
FLocTextConflicts ConflictTracker member is explicitly marked non-copyable / movable, therefore default move for FLocTextHelper can't be generated. There is currently no reason for FLocTextHelper to be movable, therefore default move ops are now simply removed from code. Move ops can be added to FLocTextConflicts if necessary in the future.
#rb arciel.rekman
#jira UE-72151
#lockdown cristina.riveron
#ROBOMERGE-OWNER: lina.halper
#ROBOMERGE-AUTHOR: yuriy.odonnell
#ROBOMERGE-SOURCE: CL 5773428 in //UE4/Release-4.22/... via CL 5773429
#ROBOMERGE-BOT: ANIM (Main -> Dev-Anim)
[CL 5784093 by yuriy odonnell in Dev-Anim branch]
FLocTextConflicts ConflictTracker member is explicitly marked non-copyable / movable, therefore default move for FLocTextHelper can't be generated. There is currently no reason for FLocTextHelper to be movable, therefore default move ops are now simply removed from code. Move ops can be added to FLocTextConflicts if necessary in the future.
#rb arciel.rekman
#jira UE-72151
#lockdown cristina.riveron
#ROBOMERGE-SOURCE: CL 5773428 in //UE4/Release-4.22/...
#ROBOMERGE-BOT: RELEASE (Release-4.22 -> Main)
[CL 5773429 by yuriy odonnell in Main branch]
The localization pipeline locks the relative paths used by a target to either the engine or project root (depending on the target type), however the UE4 engine isn't localized into many languages, so project targets often have to override some of the engine localization to support their additional languages. For in-source builds, this was possible by using a project relative path to the engine directory (which was in a fixed location), however for any out-of-source projects (such as those in the "Unreal Projects" directory) there was no way to do this in a portable way.
This change adds a "path root" to every include and exclude path, which can be set to "Auto" (the default, which detects the root based on the target type), "Engine" (to force the path to be resolved relative to the engine root), or "Project" (to force the path to be resolved relative to the project root). This allows out-of-source projects to specify paths relative to the engine in a portable way.
#jira UE-70296
#rb Lauren.Ridge
#ROBOMERGE-OWNER: lina.halper
#ROBOMERGE-AUTHOR: jamie.dale
#ROBOMERGE-SOURCE: CL 5073204 in //UE4/Release-4.22/... via CL 5073205
#ROBOMERGE-BOT: ANIM (Main -> Dev-Anim)
[CL 5137242 by jamie dale in Dev-Anim branch]
The localization pipeline locks the relative paths used by a target to either the engine or project root (depending on the target type), however the UE4 engine isn't localized into many languages, so project targets often have to override some of the engine localization to support their additional languages. For in-source builds, this was possible by using a project relative path to the engine directory (which was in a fixed location), however for any out-of-source projects (such as those in the "Unreal Projects" directory) there was no way to do this in a portable way.
This change adds a "path root" to every include and exclude path, which can be set to "Auto" (the default, which detects the root based on the target type), "Engine" (to force the path to be resolved relative to the engine root), or "Project" (to force the path to be resolved relative to the project root). This allows out-of-source projects to specify paths relative to the engine in a portable way.
#jira UE-70296
#rb Lauren.Ridge
#ROBOMERGE-SOURCE: CL 5073204 in //UE4/Release-4.22/...
#ROBOMERGE-BOT: RELEASE (Release-4.22 -> Main)
[CL 5073205 by jamie dale in Main branch]
This is handled by the ELocTextPlatformSplitMode enum, used by FLocTextHelper (default is ELocTextPlatformSplitMode::None to preserve old behavior), and allows you to optionally split localization data for all platforms, or for any NDA restricted platforms. Note: Any localization data that is used by multiple platforms is still considered platform agnostic, even if it appears only within platform specific files.
#jira UE-65600
#rb Francis.Hurteau
#lockdown Matt.Kuhlenschmidt
[CL 4761508 by Jamie Dale in Dev-Editor branch]