Wing's Perforce is disabled by default and must be enabled with the Active preference in the Version Control / Perforce preferences group. The support also requires the p4 command line executable to be installed separately from Wing. Please see http://www.perforce.com for information about Perforce. The p4 executable may either be in your path or set it with the Perforce executable preference.
Wing finds Perforce's working directory is found by executing p4 client -o in the environment defined in Project Properties when a project is opened or the environment is changed. The client specification must be defined outside of Wing.
If Wing's Project Home Directory project property is set to a value outside of the Perforce tree, it may be necessary to add -d pathname (with the appropriate pathname for your configuration) to Extra Global Arguments in Wing's Perforce preferences.
If you usually use the Perforce GUI, you may need to start up the GUI before the environment used by the p4 executable is set up properly.
Perforce defines the following commands, in addition to those documented in Common Version Control Operations:
Prepare the files for editing and make any editor the file is opened in writable. Note that revert on an unmodified file that's opened for editing will release the file from edit status.
|« 14.5. Mercurial||Table of Contents||14.7. Subversion »|