Unclarity whether to submit Setup.bat downloaded Binaries to p4

Development Pipeline & Plugins
, ,
1

We are wondering what to submit to perforce to support:

  • Coders (building editor binaries themselves)
  • Builder (sync p4 depot, builds new (editor) binaries, submits the new (editor) binaries into p4)
  • Artists (do not build locally, but sync the newest (editor) binaries via UGS from p4 (binaries stored in a different stream)

So for the very first stream/depot population, we do locally on a PC:

  • Download UE source and submit it to p4/depot
  • Then all coders have to run Setup.bat (and the Generate Project Files) locally and are good to go
  • But what about the Builders and the Artists/other Devs. Who do they get the missing binaries from the Setup.bat dependency download?

Should we maybe run Setup.bat with excluding all the platforms like android, mac, which we dont need and still submit the windows binaries into p4 next to the UE/project source?

Or is there a better way to get those platform dependency binaries to builders and artists?

2

Steps to Reproduce

3

Hello!

The recommendation is to submit the engine sources after running Setup.bat so that Coders and Builders don’t have an extra step to go through after synching the stream. You can remove some of the platforms that you are not using (Android, Mac…) but they are spread through the engine folder so it can be a bit daunting to hunt down everything. There is no documentation about doing that clean up. The best reference is to install the Launcher distro and check which folders are not present when removing the platforms you don’t want.

We are aware of licensees that are depending on setup.bat being run on all PCs after setting a new workspace. It’s a matter of preference at this point.

Regards,

Martin

4

Alright, thank you very much for the quick answer and the info, that helps a lot!