So I was going to use SVN to develop my project with my team but I followed M. Allars guide to setting up a Perforce server on DigitalOcean.
My team-members can connect fine using P4V and in-editor for our test project and we are able to commit files from the editor and from P4V so we have the VERY basics down. If any tips like branches etc, or beginner setup tips are around, I’d definitly be grateful, cant find much regarding P4/UE4 except the offical guide which isn’t much help, odd considering its used by major teams and Epic themselves.
Heres the cavets.
- I do 95% of the only C++ coding, the rest of the team uses blueprints or does art etc.
- When I compile from source the plugins recompile everytime which takes up 75% of the compile time. Ie Ramas Victory Plugin is re-compiled but the /source/ folder is there and so Visual Studio recompiles it EVERY time, same with the ocean plugin.
So a few key things that are rambling around in my head
Is there anyway to setup P4V or how would I go into shell to setup any committed files/folders to be auto-ignored, my team has accidently comitted /saved/ and /intermediate/ in the past and with source it gets more complicated.
Which files do I commit and not commit regarding source? If I understand from my previous thread everything is local except /source/* /content/* /binaries/* /config/* projectX.uproject and projectX.sln. Edit: Just learned you should not commit your VS .sln or .suo and generate them locally. Is there anyway a bat file could be committed to the root directory so people not “Code minded” can generate the files needed?
The SDF and PCH’s and any intermediate folders are ignored right? This would be really easy if I could setup an auto-ignore system so everyone can just commit everything at once and Perforce figures it out itself, just like gits .gitignore
How do I prevent myself (and my team-members) from re-compiling the /source/ .cpp and .h files from plugin source code when the plugins arleady been compiled and has /binaries/ files that open in the editor just fine?
If a team member did accidently commit their own .sdf file or VS solution file or .pch’s, it would be as simple as deleting it from the depot and back to business right?
Edit: Is there bat file to generate .sln files automatically for non-code-minded team members? Building on that is there a way to hide the .suo and .sdf files in different folder say /DontCommit/ and still have the solution work everytime?
Edit2: Do all files in /binaries/ have to be set to +w so that team memberse dont get read-only errors still? I read that on answerhub.
Any guides out there to using P4V and also using shell to setup Perforce servers to help a newbie team to source control/team setting/C++ in general. I really dont want to screw up months and months of work, even with backups.
Im running perforce 15.1 on a Ubuntu linux server using a DigitalOcean droplet.