aboutsummaryrefslogtreecommitdiff
path: root/INSTALL-GIT
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2011-02-15 16:55:18 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2011-02-15 16:55:18 +0200
commit391a4c294e9d9a378c636b7c25e6da027b60d45b (patch)
treeaca38120e76fe4029f7d85ed774da08670ed0fd5 /INSTALL-GIT
parentc7c9e84915365e54e5656ed215593d2423e73044 (diff)
Add CLI as prerequisite in INSTALL-GIT
Diffstat (limited to 'INSTALL-GIT')
-rw-r--r--INSTALL-GIT7
1 files changed, 4 insertions, 3 deletions
diff --git a/INSTALL-GIT b/INSTALL-GIT
index 3276f45..fc6d7fe 100644
--- a/INSTALL-GIT
+++ b/INSTALL-GIT
@@ -4,9 +4,9 @@ checked out from the git repository.
The major difference between using a released source code package and source
code from the repository is that the former does not contain autotools-based
makefiles or Visual Studio project files. Instead, it contains templates for
-these files as well as its own, custom build system. This build system is
+these files as well as its own, custom build system. This build system is
used for development as well as to automatically generate the autotools and
-Visual Studio files.
+Visual Studio files.
This file describes how to use this build system to build the package as well
as to create a release-ready source distribution which contains the autotools
@@ -22,6 +22,7 @@ following additional packages:
- GNU bash >= 2.0.0 http://www.gnu.org/software/bash/
- GNU make >= 3.81 http://www.gnu.org/software/make/
- build >= latest http://www.codesynthesis.com/projects/build/
+ - cli >= latest http://www.codesynthesis.com/projects/cli/
If you are planning to create the source code distributions, then you will
also need the following packages:
@@ -39,7 +40,7 @@ Configuring and Building
To build the source code simply run make in the root directory of the package.
The first time you run make, the build process will also configure the
-package by asking you several questions. On the subsequent runs, make will
+package by asking you several questions. On the subsequent runs, make will
only rebuild what has changed.
To run the automated test suite (if any), run 'make test'. To clean the object