Re: Why do static libraries require ranlib?
Re: Why do static libraries require ranlib?
- Subject: Re: Why do static libraries require ranlib?
- From: Steve Checkoway <email@hidden>
- Date: Mon, 17 Jul 2006 00:39:04 -0700
On Jul 16, 2006, at 11:59 PM, Andy Wiese wrote:
We have several static libraries that are stored in a svn
repository, then checked out onto the development workstations.
These libraries will not link on any machine except the one that
built the library, until the ranlib utility is run on it. Its no
more than an annoyance, but I am curious--can anyone explain what
is "out of date" about these libraries? Is there some way that we
can build them so that they link without having to modify them with
ranlib?
I believe it's the archive's table of contents that is out of date.
There was a discussion regarding ways to deal with this a few days
ago. I think the final conclusion we came to was to have a shell
script phase that would copy the archive from your working copy (in
the repository) to some other location and run ranlib on it there.
That way you don't have cvs or svn (or <insert tool here>) saying
that you've modified the file and that way ranlib is automatically
run a single time on the archives.
--
Steve Checkoway
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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