Keil Logo

Using the SVCS Menu

µVision3 provides a configurable interface to Software Version Control Systems (SVCS). Pre-configured template files are provided for: Intersolv PVCS, Microsoft SourceSafe, MKS Source Integrity, Rational Clear Case, and others. Application Note 179: CVS Integration for µVision3 provides a Concurrent Versions System (CVS) interface. CVS is available under the GNU General Public License.

Via the SVCS Menu you call the command line tools of your Version Control System. The configuration of the SVCS menu is stored in a Template File. This menu is configured with the dialog SVCS — Configure Version Control.... The dialog options are explained below. You can use Key Sequences to specify project name, file names, or other project specific parameters.

Dialog Item Description
Template File name of the SVCS menu configuration file. It is recommended that all members of the software team are using the same template file. Therefore the template file should be copied to the file server.
User Name user name that should be used to log into the SVCS system. The user name is passed with the %U key sequence in the argument line.
Database file name or path for the database used by the SVCS system. The database string is passed with the %V key sequence in the argument line.
Menu Content text shown in the SVCS menu. This line may contain key codes and file codes. Shortcuts are defined with a preceding & character. The selected menu line allows you to specify the options listed below.
Query for
ask for comment that is copied into a temporary file. You may pass the path to that file with the key sequence %Q key sequence as argument to the SVCS command.
Query for
ask for revision information that is passed as string with the %R key sequence.
Query for
ask for checkpoint information that is passed as string with the %C key sequence.
Run Minimized enable this option to execute the application with minimized window.
Command program file that is invoked when you click on the SVCS menu item.
Arguments command line arguments that are passed to the SVCS program file.
Environment environment variables that are set before execution of the SVCS program.

The output of command line SVCS application programs is copied to a temporary file. When the SVCS command completes the content of this temporary file is listed in the Output Window — Build page.

A sample SVCS menu is shown on the right. A selected file in the page Project Workspace — Files is the SVCS argument. The target name selects the *.UV2 project file. The local copy of a looked file is read-only and gets a key symbol.

µVision3 projects are saved in two separate files. Project settings in *.UV2: this file should be looked with the SVCS and is sufficient to re-build an application. The local µVision3 configuration in *.OPT contains window positions and debugger settings.
The following table lists typical SVCS menu items. Depending on your configuration, additional or different items might be available. Include files may be added to the project as document file to access them quickly with the SVCS.

SVCS Menu Item Description
Explorer start the interactive SVCS explorer.
Check In save the file in the SVCS database and make the local copy read-only.
Check Out get the actual file version from the SVCS and allows modifications.
Undo Check Out undo the check out of a file.
Put Current Version save a local file in the SVCS database but still allow modifications to it.
Get Actual Version get a current read-only copy of a file from the SVCS.
Add file to Project add the file to the SVCS project.
Add file to Project add the file to the SVCS project.
Differences, History show SVCS information about the file.
Create Project create a SVCS project with the same name as the local µVision3 project.


  • The pre-configured *.SVCS files may be modified with a text editor to adapt program paths and tool parameters.

  • Microsoft SourceSafe requires the command Set Current Project after you have selected a new µVision3 project. Remove the SSUSER environment variable from the configuration to use the login name of the workstation.

  • MKS Source Integrity is pre-configured to create a project database on a server and a local sandbox workspace on the workstation.

  • Intersolv PVCS is not pre-configured for creating and maintaining projects.

Related Knowledgebase Articles

  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.