Thanks Martin,
I had already figured that out and though it works it requires some
intervention on every update.
I was looking more for a tag to place in the .../debian/LocalConfig.kmk
that would take the already generated release number and use it.
Example: VBOX_VERSION_STRING := $(VBOX_VERSION_STRING_RAW) when we were
compiling beta and the string was too long.
I see where the $(svn_revision) is used in two of the three types of
builds (assumption) and the third is 0 (zero) which is what I get when
looking at the about in the program. I can of course manually change the
0 to match the release but figured there was some way to automate this.
Line 54 of debian/rules
svnrev :=$(if $(svn_revision),$(svn_revision),0)
Ideas?
On 09/12/2011 10:41 AM, Martin Simmons wrote:
On Fri, 09 Sep 2011 12:43:48 -0500, Perry Halbert said:
Two questions
I have looked through the code for some time and just can't seem to see it.
Building DEB from SVN:
What tag and where would I put it to *not build the *-dbg... .deb?
Also when building deb, the release version is built into the file name
but the release version is not included in the about screen like it is
when building a *.run (it just shows r0). What would I need to do to
include the release number in the about information?
Try creating a file callled SVN_REVISION at the top level of the source tree
containing the line
svn_revision := nnnnn
The deb/rpm build scripts get their revision number from that variable.
Oracle's build process has some unpublished steps.
__Martin
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev
