There are numerous different releases of MSVCRT20.DLL version 2.11.000, CT元D.DLL version 1.0 and COMDLG32.DLL version 4.00 "out there". In practice, "stealth" upgrades happen, especially during the beta period. If the world were perfect, there should not exist two different components with the same version number. Each component (DLL, ActiveX object, OLE server, embedded firmware, etc.) may have its own version. Why use SvnRev?Ĭomputer programs have versions. The pre-compiled executables, for Microsoft Windows and Linux, are built with SQLite. The source code for SQLite must be downloaded separately. Our aim was to use it from a "makefile" and to attach to a version control system, and specifically to the Subversion system.įor full functionality, SvnRev must be compiled with SQLite. SvnRev is a portable utility and should run on every environment on which a conforming C compiler is available. SvnRev is a self-contained utility that does not rely on a particular IDE. SvnRev is specifically designed for the Subversion version control system, but it can also be used with CVS and RCS. It gets the revision number from the "RCS keywords" in the source files, or (for recent versions of Subversion) from the "working copy" database. This revision number is stored in constants (macros in the case of C/C++), both as a number and as a string. SvnRev is a little program that writes the current revision number of a project into a C/C++ header file, a Java package file, a C# class file, or an Ant property file. SvnRev: A Utility for Subversion and CVS/RCS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |