Re: .a under version control
Re: .a under version control
- Subject: Re: .a under version control
- From: "Peter Boctor" <email@hidden>
- Date: Thu, 18 May 2006 13:14:18 -0700
This happens because the file modification date changes when you get the file from the repository.
I don't know if there is something equivalent in subversion, but in Perforce you can change the file type to +m. This tells Perforce to preserve the file modification date of the file when it was submitted. See "Preserving timestamps" on this page
www.perforce.com/perforce/doc.052/manuals/p4guide/ab_filetypes.html
-peter
On 5/18/06, David Dunham <email@hidden> wrote:
We're developing a game that uses a static library: libsqlite3.a (we
can't dynamically link since we run on 10.2.8). We put this file
under Subversion version control.
It appears that any time a developer gets it from the repository, the
tool chain complains that you need to run ranlib on it. This works
fine, but then the file is modified, and inevitably gets checked back
in. So the next developer updates, and now he has to run ranlib. Etc.
Is there any way to break this cycle, short of remembering that some
changes aren't significant? Adding a script that runs ranlib every
time seems like overkill.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden