> On Jan 16, 2016, at 12:21 PM, Scott Ribe <scott_r...@elevated-dev.com> wrote: > > On Jan 15, 2016, at 11:44 AM, Carl Hoefs <newsli...@autonomy.caltech.edu> > wrote: >> >> Or is the only way to avoid this to use the static archive "*.a" form of the >> library > > FYI, in your example, if you add the .a, it (the linker, not Xcode, IIRC) > will use the .dylib instead. The only way to get it to use the .a is to put a > copy of the .a into some other folder where there is no corresponding dylib > and add that copy.
Interesting, but many s/w packages (OpenCV, etc) deliver only .dylib versions. For the others, I added libXXXX.a in Xcode. The build/link log shows it to be using "-lXXXX", so according to your comment, it's picking up the dynamic version, which is fine, if there is one. -Carl _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
