Re: ranlib
Re: ranlib
- Subject: Re: ranlib
- From: Steve Baxter <email@hidden>
- Date: Tue, 28 Feb 2006 20:05:24 +0000
On 28 Feb 2006, at 19:27, Stefan Haller wrote:
Steve Baxter <email@hidden> wrote:
When we check a .a library out of CVS and try and build the project
with Xcode, we get an error:
ld: table of contents for archive: ../../Openlab 2.x/3rd Party Stuff/
Hasp4/libhasposx.a is out of date; rerun ranlib(1) (can't load
from it)
I can run ranlib on this and it works OK - is there any way of
telling the linker to ignore the date mismatch and just get on with
it?
This is mentioned as a known bug in the ranlib man page. We work
around
it by copying the .a files and running ranlib on the copies; but we
have
a Makefile-based build system, so it is very easy to do there. In
Xcode, you probably have to add a shell script build phase that does
this; if you set the input and output files of the build phase
correctly, it should only kick in when a new version has come in from
CVS.
Thanks, I'll give that a try.
On that note, why does Xcode update project files (making them dirty
for version control) when nothing has changed?
They are text files, so just diff them to see what has changed. I
have
seen cases where a build product's entry changed from
lastKnownFileType
to explicitFileType after building, or something like that.
Nothing has changed apart from the modification date (which Mac CVS
Pro considers to be a change).
Cheers,
Steve.
Stephen Baxter
Software Development Manager
Improvision
email@hidden
+44-2476-692229
_______________________________________________
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
| References: | |
| | >Re: ranlib (From: email@hidden (Stefan Haller)) |