Re: .a under version control
Re: .a under version control
- Subject: Re: .a under version control
- From: Jim Correia <email@hidden>
- Date: Thu, 18 May 2006 13:44:49 -0400
On May 18, 2006, at 1:03 PM, David Dunham 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.
Don't put the build products under revision control.
Check in the sqlite3 source, and have the static library built with
your project (via a secondary target, or a cross-project dependency.)
Jim
_______________________________________________
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