cp "destroys" static libraries?
cp "destroys" static libraries?
- Subject: cp "destroys" static libraries?
- From: Jesper Papmehl <email@hidden>
- Date: Tue, 16 Aug 2005 18:38:17 +0200
My app links to a static library that is created using a separate
project. When the static lib is built, I use a shell script to copy
it (using cp -R on the enclosing folder) to a separate location for
distribution. I then copy it from that location to a place where my
app project will find it.
When I try to link my app, I get the following error message:
ld: table of contents for archive: <path>/libMyLib.a is out of date;
rerun ranlib(1) (can't load from it)
If I copy the library manually in the Finder, instead of using cp -R,
my app links without any problems. In other words, it seems that cp
does something to the library that causes it to break, or
alternatively that the Finder does something to it to fix it.
What do I have to do to get a working copy of a static library when
copying it from a shell script? Do I need to run ranlib (whatever
that is) after every cp invocation?
TIA
/Jesper Papmehl
_______________________________________________
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