Unity-Technologies
/
NativeVersionControlPlugins
зеркало из https://github.com/Unity-Technologies/NativeVersionControlPlugins.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
Perforce Version Control plugins for Unity
496 коммитов 17 Ветки 16 Теги 129 MiB
C++ 70.2%
C# 23.9%
C 2.7%
Perl 1.8%
Shell 0.7%
Разное 0.6%
Перейти к файлу
Miguel González 2ebe7f0cf6
Update README.md 
Cleanup structure and add references to Perforce API version.

Signed-off-by: Miguel González <miguel.gonzalez@unity3d.com>
 		2022-02-09 13:46:05 +01:00
.github Update pull_request_template.md 2019-11-22 19:17:32 +02:00
.yamato Merge branch 'master' into remove-plasticscm 2021-11-16 10:20:50 +01:00
Common Add exclusive checkout state. 2020-05-11 21:23:23 +03:00
P4Plugin Updated libraries for win32 building 2022-02-09 10:19:14 +01:00
TFSPlugin Updating to 1.5 and checking in binary. 2016-02-08 13:46:44 -08:00
Test Update status test to check for files with exclusive open file type modifier. 2020-05-18 17:33:01 +03:00
.gitignore Ignore CLion (Jetbrains IDE) files 2022-02-09 13:32:38 +01:00
License Remove subversion from build scripts 2019-09-20 14:11:42 +03:00
Makefile.gnu Replace references in build files 2022-02-08 16:18:58 +01:00
Makefile.osx Replace references in build files 2022-02-08 16:18:58 +01:00
Makefile.srcs Replace references in build files 2022-02-08 16:18:58 +01:00
README.md Update README.md 2022-02-09 13:46:05 +01:00
TODO.txt first version of simple TODO list 2016-07-11 14:44:32 +01:00
VersionControl.sln Remove anything related to PlasticSCM 2021-11-03 16:36:26 +01:00
build.pl Remove anything related to PlasticSCM 2021-11-03 16:36:26 +01:00
msbuilder.cmd Initial commit 2013-01-09 22:36:47 +08:00

README.md

NativeVersionControlPlugins

About

This is the source code of the built-in version control plugins that are shipped with Unity.

You can build support for you own favourite version control system into Unity by cloning this repository and make changes as needed.

Note that only Perforce support is shipped for Unity 4.2+, TFSPlugin for 4.6+.

Overview

A plugin is an executable located in a designated directory that Unity can start and kill at will. At startup, Unity will scan the directory and start each executable in order to identify the plugin and its settings. When a version control system has been enabled in unity it will start the associated plugin executable and send commands to it by using stdin/stdout (MacOS) or Named Pipes (Windows).

The Perforce plugin is using the libraries provided by Perforce and its callback style API. Furthermore, is streams results from the perforce server directly to Unity.

You need Unity 4.2+ to use the integrated version control plugins.

Structure

  • Common/ contains structures and functionallity common to all plugins
  • P4Plugin/ contains the Perforce plugin code and Perforce libraries (binaries shipped with Unity)
  • TFSPlugin/ contains the Team Foundation Server/VS Online plugin code
  • Test/ contains integration tests

To build:

perl ./build.pl

To test:

perl ./build.pl -test

 Perforce

The Perforce plugin source code is located under /P4Plugin/Source. It references the Perforce APIs, located under /P4Plugin/Source/r17.2. As its name states, we're targeting the 17.2 release of Perforce.

Perforce API includes and libraries were downloaded from the Perforce downloads page.

 Windows

Windows binaries are located under /P4Plugin/Source/r17.2/lib/win32 and /P4Plugin/Source/r17.2/lib/win32debug.

Both directories contain libraries for Win32 - x86 only. They require Visual Studio v10.0 (2010).

License and terms

The plugin code itself is licensed under public domain.

Libraries used by the plugin have their own licenses and are allowed to be distributed with the plugin.

The PerforcePlugin uses the P4 API. For more information on terms of usage and how to get the P4 API, visit the following links: