Open Menu
Close Menu
Apple
Shopping Bag
Apple
Mac
iPad
iPhone
Watch
TV
Music
Support
Search apple.com
Shopping Bag
Lists
Open Menu
Close Menu
Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists
Why do static libraries require ranlib?
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Why do static libraries require ranlib?
Subject
:
Why do static libraries require ranlib?
From: Andy Wiese <
email@hidden
>
Date: Sun, 16 Jul 2006 23:59:46 -0700
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?
_______________________________________________
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
Follow-Ups
:
Re: Why do static libraries require ranlib?
From:
Steve Checkoway <email@hidden>
Prev by Date:
Stack trace for i386 yet?
Next by Date:
Re: Stack trace for i386 yet?
Previous by thread:
Re: Stack trace for i386 yet?
Next by thread:
Re: Why do static libraries require ranlib?
Index(es):
Date
Thread