Let's assume you have a library named tools. You created it from a

special template named "library/static". Then you write a program and

feel the need for this library. What should you do? It's enough just to

open the "Project files" dialog, position it on the "Connected libraries"

folder and press "Ins" or select "Add" item. The list of library

projects is displayed. All you need is to select it here and press

Enter. All the necessary paths and file names will be passed to the

compiler the next time you try to build the project. The library with all

of its attributes can be removed from the project in the same way.

Being a Linux developer you must have heard about CVS. It's a

powerful version control system for Linux. But I'll explain what it is

in a few words for newbies. CVS allows you to keep track of all the changes

made to a program source. You can retrieve old versions of your code if

some bugs were added with the last modifications. Every change can be

commented and put into a history. Lets move on to how motor interacts with

CVS.

To be able to use CVS you should have a repository, place to put the

stuff. CVS can work though TCP/IP as well as in local mode. Here I'll

explain how to create a minimalist local repository. For further

information about setting up a CVS TCP/IP server, please consult the CVS

documentation and info pages.

First, make sure you have CVS installed in your system by typing cvs

on your command line. If you haven't got it, you can download it from

its web site at www.cvshome.org.

For example, you want the repository to reside in your home directory

in the cvsroot/ sub-dir. To create it, execute the following command.

cvs -d /home/myusername/cvsroot init

To be able to use CVS with Motor, first of all you should point it to

the repositories you wanna work with. It can be done with the "Motor

settings" dialog, invoked either from the project list dialog or from

the "File" menu. You can see two options of switch kind here and a

list of CVS repositories. Press Ins to add one. A repository

specification consists of two parts: access method and path. For our

local repository we should specify the following: