fix for generating Target.cs when -nocodeproject is provided (removed -nocodeproject as it is no longer needed due to other fixes)
default plugins no longer cause a target file to be generated
#codereview ankit.khare, josh.adams, daniel.lamb
[CL 2473705 by Peter Sauerbrei in Main branch]
Only stage CEF3 if bUsesCEF3 is set to true in the game's target.cs file. Fix for UE-9983.
#codereview Josh.Adams, Matthew.Griffin, Peter.Knepley
[CL 2450041 by Matthew Griffin in Main branch]
There were two problems with this. One, I had to suppress registering build platforms in UBT if the project has no code. To achieve this I added new flag -nocodeproject and I'm passing it down from the editor to UAT.
The second one emerged after fixing previous one. The Editor was adding -build flag to the UAT if it found any of the VS 2012 or 2013. -build flag is making UAT to try to build, which fails as it is not supported on VS 2012-only system. During the discussion with platform team we came up with the solution to not check for VS 2012 in editor, as we only support it for XDK development, which requires both VSes on the system (2012 and 2013). Hence flag -build should be appended to the UAT command line if and only if there is VS2013 on the system.
[CL 2431415 by Jaroslaw Palczynski in Main branch]
Add BuildOnlyPlatforms_MonolithicOnly to the RulesCompiler, to specify platforms that we want to compile but not cook
Add concept of "Dependent platform" to UAT, where the cooked data comes from a source platform, and is duplicated at stage time
Updated brutal submit to handle the same changes already being submitted during a build.
Brutal submit now considers it as success when it attempts to reconcile with latest in P4 and finds no files are different in its workspace.
Fix formatting on automation.cs files to avoid future integration issues, unify as tabs-as-tabs instead of spaces
#codereview kellan.carr
[CL 2261070 by Ben Zeigler in Main branch]
TTP# 335070 - Add GUI based way to specify additional non-asset files or paths to package
CookCommandlet now uses the project settings to work out which additional directories it should cook (this removes the need for the editor to pass this information to that UAT via the command line). I've left the COOKDIR option in the UAT/CookCommandlet as, while non of our projects seem to be using it, I'm not comfortable removing it in case any scripts are using it.
CopyBuildToStagingDirectory also uses these project settings to work out which additional directories it should stage when producing the staging manifest (these are split into UFS and non-UFS directories). This allows users to define additional directories in the editor (or directly in the settings file) which will always be staged regardless of how UAT is invoked.
All of these paths are specified in the settings file as relative to the project Content directory, and the editor will enforce this fact when using the directory picker.
Also mirrored the meta-data interface from UField on IPropertyHandle. This takes care of accessing the meta-data from the correct property, even when you're accessing an element inside an array (MattK approved!).
ReviewedBy Thomas.Sarkanen, Robert.Manuszewski, Max.Preussner
[CL 2088172 by Jamie Dale in Main branch]
