Thanks for your report. There is a known issue with packaging projects built with 4.5 and 4.5.1 source code from GitHub that sounds like it may be related (UE-5317) and is currently under investigation. Those experiencing this problem have reported being able to build their projects through the launcher version of the engine instead.
I am using the launcher version, so sadly that fix isn’t a possibility for me.
Is this a known issue with the launcher version? If so, should I wait for the next engine version or is there something I can do ? (for example, there could be something in my project causing an issue or perforce)
The output logs from your build and mine are nearly identical and I have not had any reports of the launcher being unable to build a project. I suspect your issue may have to do with perforce version control, which I have included in the report of this problem. If you have access to a version of the engine that is not tied to perforce I would try opening your project there and trying to build.
Another user was able to solve this issue by opening the source code in Visual Studios and building CrashReportClient. Try this and then run the project again and let me know if that helps at all.
Just made a clone of the project in a new location (outside of perforce location) - then unchecked only on every file to undo what perforce was doing - and I can now build my project/ It seems perforce integration needs some serious work.