XCode ld and static lib.a files...
XCode ld and static lib.a files...
- Subject: XCode ld and static lib.a files...
- From: John Weeks <email@hidden>
- Date: Thu, 29 Jun 2006 11:18:04 -0700
I sent this a while back, but got no responses, not even, "there's no
workaround", so I thought I'd try again:
I am building a static library from Fortran code using a Makefile and
libtool. I want to distribute this library to other programmers who don't
have the Fortran compiler, so I checked it into the subversion repository.
Checking it out results in a new file, of course, with a new date. Now ld
(and consequently XCode) complains that the table of contents is out of
date. This is covered in the man page for libtool:
BUGS
With the way libraries used to be created, errors were possible if the
library was modified with ar(1) and the table of contents was not
updated by rerunning ranlib(1). Thus the link editor, ld, warns when
the modification date of a library is more recent than the creation
date of its table of contents. Unfortunately, this means that you get
the warning even if you only copy the library.
Unfortunately, this seems to be inaccurate in that XCode treats this as an
error. Is there a way to prevent XCode from reporting a build failure? I
hate to force my colleagues to run ranlib on the library every time they
check it out.
Regards,
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
email 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