- UnsafeTypeCastWarningLevel can be set to WarningLevel.Warning or WarningLevel.Error in ModuleName.Build.cs (off by default)
- Currently only supported on MS compilers (Clang ignores the setting for now)
#jira UE-86949
#rb ben.marsh
#ROBOMERGE-SOURCE: CL 11050203 via CL 11050250 via CL 11050262
#ROBOMERGE-BOT: (v637-11041722)
[CL 11050266 by michael noland in Main branch]
Fix FConfigCacheIni::GetSectionNames returning names in reverse order.
Make sure build scripts properly respect bundle order.
change 2/2 - everything not internal
[at]Daniel.Lamb [at]Hongyi.Yu
#ROBOMERGE-SOURCE: CL 11047646 via CL 11047649 via CL 11047656
#ROBOMERGE-BOT: (v637-11041722)
[CL 11047666 by justin marcus in Main branch]
This will deploy the same project from different streams or users to to different workspaces.
Use the DeployFolder instead of the ShortProjectName for all platforms.
The existing -deploy=DeployFolder argument can be used to specify any custom workspace name.
#rb jeff.newquist
[CL 11041420 by PJ Kack in Dev-Core branch]
- Add "ExtraTargetsToStageWithClient" parameter which allows you to select other build targets to stage alongside a client build.
- Added the notion of a "primary target" for a given target type, so a project can have many editor targets but know which was is the primary one that it should use for cooking
- Fixed a typo in UAT param parsing where the check for the correct number of game targets was looking at the number of editor targets
#rb ben.marsh
#ROBOMERGE-SOURCE: CL 10950660 via CL 10950663 via CL 10950667
#ROBOMERGE-BOT: (v632-10940481)
[CL 10950672 by graeme thornton in Main branch]
* Paths to projects with spaces in the name now work correctly on XB1
* Loose builds for content-only projects no longer crash due to missing project arg (UE-78746, UE-78739)
* Packaged projects with version numbers in the name are correctly recognized (UE-85189)
#jira UE-78739, UE-78746, UE-85189
#rb josh.engebretson
#lockdown cristina.riveron
#ROBOMERGE-SOURCE: CL 10944220 in //UE4/Release-4.24/...
#ROBOMERGE-BOT: RELEASE (Release-4.24 -> Main) (v632-10940481)
[CL 10944226 by andrew grant in Main branch]
#rnx
#rb none
#ROBOMERGE-SOURCE: CL 10878174 via CL 10878175 via CL 10878176 via CL 10878177 via CL 10878178
#ROBOMERGE-BOT: (v626-10872990)
[CL 10878179 by ryan durand in Main branch]
Added support for generating additional backgrounddownloadsini files for builds that already exist.
#test preflight
#rb Justin.Marcus
#ROBOMERGE-SOURCE: CL 10809746 via CL 10809748 via CL 10809756
#ROBOMERGE-BOT: (v610-10636431)
[CL 10809761 by daniel lamb in Main branch]
There is a new packaging setting, LocalizationTargetsToChunk, which lets you specify which of your localization targets should be chunked during cook.
If enabled, any localization entries corresponding to assets will be split into a separate LocRes file for the chunk containing that asset, and will be removed from any chunks (including the primary chunk) that do not contain that asset. This is useful to restrict localized text to the chunk that contains the corresponding asset for the text, and allows localization data to be selectively encrypted based on the chunking rules.
At runtime this chunked data will be loaded into the text localization manager automatically when the chunk is loaded.
#jira
#rb Graeme.Thornton
#ROBOMERGE-OWNER: jamie.dale
#ROBOMERGE-AUTHOR: jamie.dale
#ROBOMERGE-SOURCE: CL 10791622 via CL 10791636 via CL 10793057 via CL 10793091 via CL 10793112
#ROBOMERGE-BOT: (v610-10636431)
[CL 10793116 by jamie dale in Main branch]
CompatibleChangelist number was being overridden as part of the build process due to CL 9823639. The desired effect here was to ensure that Epic's compatible changelist number was cleared out for licensee builds; instead of just forcing it to be set, we clear it out if we're changing the licensee flag.
#jira UE-85874
#rb none
#ROBOMERGE-SOURCE: CL 10727491 in //UE4/Release-4.24/...
#ROBOMERGE-BOT: RELEASE (Release-4.24 -> Main) (v610-10636431)
[CL 10727503 by ben marsh in Main branch]
