Current advice for distributing custom engine builds to team without recompiling?

[HateDread]

@kamrann;597364

This has been changed recently, rocket is being phased out I think.

On 4.12, just doing a regular build, then adding an empty InstalledBuild.txt to the Engine/Build directory along with a config file addition (see here), was enough to prevent engine and engine plugin rebuilds in the context of a project.

If you look at the Build Updates section at the end of this 4.13 post however, it gives some details on what I guess is a more flexible method for determining exactly what gets put into a distributable engine build. I haven’t tried using it. I’m pretty sure the above approach still works in 4.13 if that’s enough for you.

An empty InstalledBuild.txt leads to the following error when trying to run GenerateProjectFiles.bat.

I added the following to Engine/Config/BaseEngine.ini:

[InstalledPlatforms]
+InstalledPlatformConfigurations=(PlatformName=“Win64”, Configuration=“DebugGame”)
+InstalledPlatformConfigurations=(PlatformName=“Win64”, Configuration=“Development”)
+InstalledPlatformConfigurations=(PlatformName=“Win64”, Configuration=“Shipping”)
+InstalledPlatformConfigurations=(PlatformName=“Win32”, Configuration=“DebugGame”)
+InstalledPlatformConfigurations=(PlatformName=“Win32”, Configuration=“Development”)
+InstalledPlatformConfigurations=(PlatformName=“Win32”, Configuration=“Shipping”)

Any ideas? I figured the point of the above was to not have to tie in a specific game into the engine!