Hi! Ralph Glasstetter wrote:
>>>Seemed to me a little bit more transparent/easier than this svnrev.c tool >>>we talked about a few weeks ago... and which always needs to be compiled >>>before usage. >> >>As long as you have (ba)sh and a few tools... > > > Of course,... but that's no problem under Linux and Windows with > MinGW/MSYS. Older versions of bash (i.e. bash2) have problems, and some other Bourne compatible shells may fail as well. I'm working on that. >>>Additionally in that header file a version string containing the last >>>official release is set, which is got from the envirionment variable >>>$VERSION, some text file "version.txt", a pre-build header file or some >>>default set in the script (in that order!). >> >>Ugh. That's a bit too much. ;-) > > Just to have the choice and play a bit with different options... ;-) I think we should skip $VERSION. >>>At the moment I'm not sure which method to use... I would prefer setting >>>it via a template "version.h" to minimize the need for additionally >>>"hidden" resources, but don't know if this causes any conflicts, since it >>>has to be in the repository that way. >> >>setversion should not modify a file that comes from the repository. >>Otherwise, I might check in the modified version by mistake. > > > OK,... than we are fine with a simple text file named "version.txt" in the > top directory which just contains the string "0.5.4". I'll rename that file to VERSION, if you don't mind. > Hhmmm,... maybe it's a good idea to put it under version control, i.e. allow > for a comment line containing $Id$ and scan it also additionally by > setversion? Version control - yes. $Id$ line - not sure. > In case one "declares" an official version just by changing the text file.... > I attached an updated script allowing comments (and with a small bug fix)! Maybe we should check for a .svn subdirectory. If none exists, the sources probably come from a release tarball. [...] >>You probably forgot to tell make that dvbcut.cpp now depends on >>version.h - if you don't, it will simply ignore any changes to the file. > > Hmmm, .... are the include files not checked automatically? > Also a "make dep" did not work... Did you add `#include "version.h"' to dvbcut.cpp? -- Michael "Tired" Riepe <[EMAIL PROTECTED]> X-Tired: Each morning I get up I die a little ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
