[Scummvm-cvs-logs] SF.net SVN: scummvm: [22220] scummvm/trunk/base/version.cpp

[wjpalenstijn at users.sourceforge.net]

Revision: 22220
Author:   wjpalenstijn
Date:     2006-04-29 06:17:22 -0700 (Sat, 29 Apr 2006)
ViewCVS:  http://svn.sourceforge.net/scummvm/?rev=22220&view=rev

Log Message:
-----------
add small note about svnversion

Modified Paths:
--------------
    scummvm/trunk/base/version.cpp
Modified: scummvm/trunk/base/version.cpp
===================================================================
--- scummvm/trunk/base/version.cpp	2006-04-29 13:01:35 UTC (rev 22219)
+++ scummvm/trunk/base/version.cpp	2006-04-29 13:17:22 UTC (rev 22220)
@@ -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?


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.