Hi, Am Mittwoch, 25. Juli 2007 15:34 schrieb Michael Riepe: > > 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. > > 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... ;-) > > > 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". 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? 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)! > > > Another problem is how to call "setversion"! > > At the moment I'm doing this manually after each checkout since my > > knowledge about make/scons is limited. But that shouldn't be too > > difficult for an expert... ;-) > > > > For the Windows Makefile something like: > > version.h: *.cpp *.h > > $(TOP)/setversion $^ > > ... or something very similar ... I guess so... > > > should do the job (but I don't know where to put it in the Makefile,... > > my first attempts failed... :-( ). > > 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... But I've to admit I didn't tried to find the error very seriously... just checked that the script is working... ;-) > > Where you put the rule doesn't matter much. Just don't make it the first > explicit rule, because that's executed by default when you call "make" > without arguments. That was my very first mistake,... which I solved by myself... ;-) > > > And for SCons... I really not even have an idea what to write into the > > SConstruct/SConscript files... > > Neither do I. Ok, I could just execute the bash script from SConstruct because AFAIK it's just a python script,... but that's not in the sense of a proper build mechanism... > > > although I have some knowledge about python > > and had a look on the scons webside this build tool is still a miracle to > > me... :-( > > Same here. I'll ask Sven... :) Ralph
# That file containes the officially released version # # $Id$ # 0.5.4
setversion
Description: application/shellscript
------------------------------------------------------------------------- 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
