That is, if you have not set up the paths to the source-control command line clients, even if a working copy exists and the appropriate command line client is installed, Embedded Studio cannot establish source-control integration for the project. If Embedded Studio cannot determine, from the file system, the source-control system in use, it disables source-control integration. When Embedded Studio loads a project, it examines the file system folder that contains the project to determine the source-control system the project uses.
Fetching files in the project from source control.Adding files in the project to source control.Showing the source-control status of files in the project.Connecting to the source-control repository and mapping files in the Embedded Studio project to those in source control.The source-control integration capability provides: On Windows operating systems, the Git command is hg.exe.Įxample with SVN Source control capabilities Set the Executable environment option of the Mercurial Options group to point to Mercurial hg command.On Windows operating systems, the Git command is git.exe.
Set the Executable environment option of the Git Options group to point to Git git command.On Windows operating systems, the Subversion command is svn.exe. Set the Executable environment option of the Subversion Options group to point to Subversion svn command.Select the Source Control category in the options dialog.Once you have installed the command line client, you must configure Embedded Studio to use it. To enable Embedded Studio to utilize source-control features, you need to install the appropriate command line client on your operating system for the source-control systems that you will use. Embedded Studio supports Subversion, Git, and Mercurial as source-control systems.
0 kommentar(er)
