Why not only relink if the output of svnversion changes?
Michael
On 7/17/06, Sigfred HÃ¥versen <bsdlist@mumak.com> wrote:
>
> Max Bowsher wrote:
> > Christopher Ness wrote:
> >
> >>Does anyone out there have a patch to update the build system so that it
> >>includes the revision number the source was built from in
> >>`/subversion/include/svn_version.h`
> >>
> >> SVN_VER_TAG
> >> SVN_VER_NUMTAG
> >>
> >>Instead of the non-descriptive development strings?
> >>
> >>I'd like to know what revision I'm running without having to find the
> >>working copy I built the source from.
> >>
> >>Please note I'm not suggesting removing the dev strings, I feel it is
> >>still important to know a development version of the code is used, but
> I'd
> >>also like to know the revision.
> >
> >
> > It's deliberately not done to avoid needing to run 'svnversion', and
>
> That is understandable :-) Very useful feature, but not for every "make"
> as you point out.
>
> > relink everything from libsvn_subr on upwards, on *every* invocation of
> > 'make'.
> > Ideas welcome, but clearly relinking the entire libsvn_foo library stack
> > on every 'make' is unacceptable.
>
> This one I don't understand.
>
> /Sigfred
>
>
> /Sigfred
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
Received on Mon Jul 17 23:16:23 2006