In my case the user did not exist when I tried to open the connection. So we just create a user.



Click on New and fill out the new user details.

You will be presented with the following message if you open the connection. Hit yes because you want to be the administrator on this server.

P4Admin lets you create and manage users, groups and set permissions to each. For our use case, it is not necessary. One thing I would advise you to do would be to require a password for the depot. You can change the password security level through the administration menu entry.

The last thing we can do but is not necessary (unless you want to follow step by step) is to rename the depot in p4admin.

Select the “Depots” tab



Right-Click on “depot”



Select “Delete Depot ‘depot’”

Select File > New > Depot to create a new Repository



Give it a name, I called mine “Projects”



That is all we have to do in P4 Admin.

P4V

P4V (GUI for Perforce) is where you typically would create the connection from your local working files and where you want to place them in the Perforce depot. Firstly, start up P4V. You should see this:

For now, let us leave workspace blank as we have yet to create it.

P4V looks something like this: (It may seem daunting at first but it is not a difficult program to master, you probably will not need to use the majority of functions Perforce provides.)

Ok let’s create the Workspace that we will use for our Development Branch.

Click on the Workspaces Tab (If you cannot see it, it is accessible via the View Menu)

Right click in the white space and select “New Workspace”

For Workspace Name call it “WIP_Development” (Like we called our P4CLIENT earlier)

Point it to the location on your PC where you will be working from. Mine is:

C:\_Projects\Where is Poppy\WIP_Development

Workspace mappings are used to map folders from the repository to your local workspace.

It also functions much like a “.gitignore” by settings file types or specific locations you do or don’t want versioned.



My mapping looks like the following:

//Projects/WIP_Dev/... //WIP_Development/... -//Projects/WIP_Dev/....sdf //WIP_Development/....sdf -//Projects/WIP_Dev/....suo //WIP_Development/....suo -//Projects/WIP_Dev/....gitignore //WIP_Development/....gitignore -//Projects/WIP_Dev/....user //WIP_Development/....user -//Projects/WIP_Dev/....userosscache //WIP_Development/....userosscache -//Projects/WIP_Dev/....sln.docstates //WIP_Development/....sln.docstates -//Projects/WIP_Dev/....userprefs //WIP_Development/....userprefs -//Projects/WIP_Dev/.../.vs //WIP_Development/.../.vs -//Projects/WIP_Dev/....obj //WIP_Development/....obj -//Projects/WIP_Dev/....idb //WIP_Development/....idb -//Projects/WIP_Dev/....ilk //WIP_Development/....ilk -//Projects/WIP_Dev/....exp //WIP_Development/....exp -//Projects/WIP_Dev/....tlog //WIP_Development/....tlog -//Projects/WIP_Dev/....log //WIP_Development/....log -//Projects/WIP_Dev/....lastbuildstate //WIP_Development/....lastbuildstate "-//Projects/WIP_Dev/Source Code/dmc/..." "//WIP_Development/Source Code/dmc/..." "-//Projects/WIP_Dev/Source Code/ricochet/..." "//WIP_Development/Source Code/ricochet/..." "-//Projects/WIP_Dev/Source Code/linux/..." "//WIP_Development/Source Code/linux/..." "-//Projects/WIP_Dev/Source Code/projects/vs2010/Debug/..." "//WIP_Development/Source Code/projects/vs2010/Debug/..."

The first line directs Perforce to include the whole repository and version it under “WIP_Development” which we set above to be:

C:\_Projects\Where is Poppy\WIP_Development

Imagine “WIP_Development” as a variable that holds the above path.



Note: This is our Project Source Directory which we will be setting up later, for now create an empty directory.



The remaining lines with a preceding minus “ – ” are being told to exclude files and directories from being versioned, These include intermediately created files from visual studio that we don’t want to clutter out commits with.



Save your workspace and select it.

If you see the following message, there are files within your selected project folder. This may be because you are moving from one PC to another or you prepared source assets within it already.



In my case I choose “No”

If you see the following Screen Ignore it and Cancel.

For paths with spaces be sure to use enclosing “quotes”.



For those interested my Release branch is basically the same setup but in the above workspace mappings “WIP_Dev” is replaced with “WIP_Rel” and the Workspace itself is called “Release” and not “Develop” I would then have to set “P4CLIENT=Release” If I ever want to commit files to that repository.



As I won’t be building the code on Release frequently (I mostly merge to it from the Develop branch – binaries included) it won’t really be an issue.

Level Editor