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]
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]
- In local runs UAT will no longer attempt to autodetect the current CL# if not asked to (with -p4cl command line param)
- Small client detection performance improvements - added client filter based on a known path under the client root.
- More logging during p4 autodetection
[CL 2053356 by Robert Manuszewski in Main branch]
- Project rules will now be stored in EngineSavedFolder when running non-installed UAT, otherwise in Temp/UAT/EscapedRoot folder
- Added CommandUtils.EscapePath utility function
- Moved DeleteDirectoryContents function from LocalBuildEnvironment to CommandUtils
- Added code to clean rules folder up on startup.
#codereview gil.gribb
[CL 2044393 by Robert Manuszewski in Main branch]
#change The engine now accepts a -UTF8Output command line argument which allows the output stream to be in the correct mode.
#change UAT accepts the same UTF8Output parameter to allow the connecting streams to be in the correct mode too (though it's currently only passed during the UnrealPak invocation).
#add FPlatformMisc::SetUTF8Output added to allow the opting-in of a UTF-8 output stream in Windows.
#codereview robert.manuszewski
[CL 2043167 by Steve Robb in Main branch]
