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

[HateDread]

@kamrann;598021

I think you should only add the text file and the ini entries after having built the engine. Once it’s there, it’s essentially saying “Don’t build the engine, it’s been prebuilt”, which presumably accounts for the GenerateProjectFiles.bat failure.

So this solution is just to mark an engine build as installed/prebuilt. It doesn’t affect the actual process of building the engine or what gets built. If you need control of that, I think you need to look at that new build graph stuff.

Thanks; that definitely solved the issue. The resulting setup still isn’t what I’m after - it protects the engine from being rebuilt under some circumstances, but sometimes the engine apparently does really need to be rebuilt even though I’m only working on a project, at which point I actually need to remove that text file to build. Not quite a Rocket-level of ease of use. I wonder if there’s a way to pass something or set some flag so that generating project files for the game project results in a VS project like binary builds - no ‘Programs’, no project build dependency on ‘ShaderCompileWorker’, etc.

I’ve been looking at the new BuildGraph system, but I can’t seem to get it off the ground. I passed this to RunUAT.bat:

BuildGraph -target=”Make Installed Build Win64” -script=Engine/Build/InstalledEngineBuild.xml

But it complains with

BuildGraph.Execute: ERROR: Missing -Script= parameter for BuildGraph

Tried swapping out for absolute paths just in case, but same issue.

Any advice, folks?