On Wed, Dec 17, 2008 at 08:30, Kenneth Goldman <kgoldman_at_us.ibm.com> wrote:
> JeremyP <jeremyp_at_jeremyp.net> wrote on 12/16/2008 07:42:51 AM:
>
>> What I do is have a target called genversion (in Xcode, but it'll work
>> if you use make or ant or anything) that creates a .c file and .h file
>> with the output of svnversion embedded. My binary build includes a
>> dependency on the genversion build target so that the .c file is
>> always regenerated.
>>
>
> I thought of that one too. But putting a call to 'svnversion' in
> my makefile to rebuild the .c file will break my customers who
> want to build from just the source without access to svn.
I think you're missing the point that's been made elsewhere. You're
presumably offering this source as a tarball or other package, since
these clients won't have access to your repository. *Hopefully* you
have an automated, repeatable process for doing this. Make part of the
process that creates that package rebuild that .c file, and distribute
that as part of the package.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=986660
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-18 14:48:18 CET