search for: update_version

bat guano wrote: >> >> "script failed to extract a version" > > Shouldn't the "update_version" scripts be called during the autogen.sh processes? It's run by configure (look for the CURRENT_VERSION definition).

bat guano wrote: > (look for the CURRENT_VERSION definition). > > CURRENT_VERSION > > Search string not found configure.ac:3 dnl The package_version file will be automatically synced to the git revision dnl by the update_version script when configured in the repository, but will dnl remain constant in tarball releases unless it is manually edited. m4_define([CURRENT_VERSION], m4_esyscmd([ ./update_version 2>/dev/null || true if test -e package_version; then...

The automake script doesn't mess with it in any way, and the projects use win32/version.h and not version.mk. As it is works now, it's just an annoyance for VS devs that use git. --- win32/genversion.bat | 8 -------- 1 file changed, 8 deletions(-) diff --git a/win32/genversion.bat b/win32/genversion.bat index cd1d4dc..8b31831 100644 --- a/win32/genversion.bat +++ b/win32/genversion.bat

"unknown" usually means this > script failed to extract a version for some reason (couldn't run git, or > your git version was too old). "script failed to extract a version" Yes, failed to extract a version. But I'm not going to re-compile git. @ubuntu:~$ git --version git version 1.7.4.1 I will use opus_1.1-beta and opus-tools_0.1.7 "tar.gz"

The opus code default compiles on -o2 optimization level. I would like to change it to -o3. I have tried doing the changes in makefile.unix . The change is not getting reflected. I am building the code in Code composer studio for TI processor C6000. Could anybody help me with this -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi When we compile opus and opus-tools from git they seem to be version unknown. Is this an oversight - or is it a 'feature'? How about giving them versions like this:- 1.1-git and 0.1.7-git Or even incorporate the commit. version-git-commit When opus is compiled now from git, opus-tools complains because it's not v1.1. And when opus-tools is compiled now from git, it shows as

bat guano wrote: > How about giving them versions like this:- > 1.1-git and 0.1.7-git > Or even incorporate the commit. We do this. See the update_version script. "unknown" usually means this script failed to extract a version for some reason (couldn't run git, or your git version was too old). For example, with git 1.5.6.1, the git describe command fails with "error: unknown option `dirty'", which results in version &...

> > "script failed to extract a version" ? Shouldn't the "update_version" scripts be called during the autogen.sh processes?

---------------------------------------- > dnl The package_version file will be automatically synced to the git > revision > dnl by the update_version script when configured in the repository, Not working for me. :-( This:- $ git clone --depth 1 git://git.xiph.org/opus.git $ cd opus $ ./autogen.sh $ ./configure Then this:- $ cat package_version | grep "PACKAGE_VERSION" PACKAGE_VERSION="unknown" Also... This:- $ git clone...