aboutsummaryrefslogtreecommitdiff
path: root/base
diff options
context:
space:
mode:
authorWillem Jan Palenstijn2006-04-29 13:17:22 +0000
committerWillem Jan Palenstijn2006-04-29 13:17:22 +0000
commitaf280f967b7288940ed2adabd4c00b66f6a708db (patch)
tree031af763afa1f8c3e07aaa8a69f7740eb9243a18 /base
parent1735b0421bbbc1fcd2a6d0126a152ceef39b6b43 (diff)
downloadscummvm-rg350-af280f967b7288940ed2adabd4c00b66f6a708db.tar.gz
scummvm-rg350-af280f967b7288940ed2adabd4c00b66f6a708db.tar.bz2
scummvm-rg350-af280f967b7288940ed2adabd4c00b66f6a708db.zip
add small note about svnversion
svn-id: r22220
Diffstat (limited to 'base')
-rw-r--r--base/version.cpp8
1 files changed, 4 insertions, 4 deletions
diff --git a/base/version.cpp b/base/version.cpp
index cdc949b60f..79ae2dc92a 100644
--- a/base/version.cpp
+++ b/base/version.cpp
@@ -45,10 +45,10 @@
* was made.
*
* So, how could we implement this? At least on unix systems, a special script
- * could do it. Basically, that script could parse the output of "svn info" to
- * determine the revision of the checkout, and insert that information somehow
- * into the build process (e.g. by generating a tiny header file, analog to
- * internal_version.h, maybe called svn_rev.h or so.
+ * could do it. Basically, that script could parse the output of "svn info" or
+ * "svnversion" to determine the revision of the checkout, and insert that
+ * information somehow into the build process (e.g. by generating a tiny
+ * header file, analog to internal_version.h, maybe called svn_rev.h or so.)
*
* Drawback: This only works on systems which can run suitable scripts as part
* of the build proces (so I guess Visual C++ would be out of the game here?