![]() uproject files with Unreal Editor to do so. Now launch the Unreal Editor by clicking the ShooterGame.uproject.Click Submit.Īfter all files are sync’ed to the depot, your depot layout should look something like this, with all ShooterGame files under source control: Right-click ShooterGame again and click Submit… write a changelist description, like “initial check in”. Right-click ShooterGame and click Mark for Add….You should now see all the ShooterGame files in your workspace. If you use this file (as opposed to using your own), please edit it to ensure you have replaced the text “GAMEPROJECT” at the bottom of the file with “ShooterGame”.This saves sync time and disk space for artifacts that will get compiled anyway. This file will ensure that the depot will not contain data that doesn’t need to get checked in, e.g.You can get the contents from this GitHub location p4ignore (no extension) in the ShooterGame folder, at the same place you find ShooterGame.uproject. Following the ongoing example, install to c:\p4depots\depot\ShooterGame In Choose Project Name and Location, choose the p4 depot.Click on the tile to start installing Shooter Game. Scroll down to the Learning Games section, and find the Shooter Game tile. This is a unique situation for a first-time Perforce depot setup, and we will fix this manually: But the main depot will likely be missing because there are no files in it. ![]() You should see the config-depot and spec depots show up. In Workspace tab, right-click c:\p4depots and click Get Latest Revision. ![]() Your workspace set up should look similar to the one below. Name your workspace and select the C:\p4depots folder as your Workspace root. (We will set up the build user’s workspace later.) Here is a suggested configuration of the dev user’s workspace. We will set up the workspace for the developer user with this. Now open the Perforce Visual Client (p4v). Your Users & Groups tab should appear similar to this: For this demo, we will use the names dev_user and build_user respectively. Create two Standard users, one developer and one build user.Take note of this fingerprint, you will need it later. Upon first login, you will be asked by Perforce to trust the fingerprint of the server.Open the Helix Core Admin tool (p4admin). ![]() We will use this as our Workspace root later. We’ll use the developer workstation to do this. Once the Helix Core commit server is up and running, the next step is to set up the depot, and check in the demo game source code. Login is via the SSH key that you would have generated or provided at creation time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |