Re: .a under version control
Re: .a under version control
- Subject: Re: .a under version control
- From: Brad Oliver <email@hidden>
- Date: Thu, 18 May 2006 15:53:45 -0700
On May 18, 2006, at 12:07 PM, 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.
Unfortunately, the only solution I've found for Subversion is to use
a script to run ranlib during the build process. If you are using
Perforce, it's easier: set the +m attribute on .a files.
--
Brad Oliver
email@hidden
_______________________________________________
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