Re: How make app use static sqlite in its package, instead of dylib
Re: How make app use static sqlite in its package, instead of dylib
- Subject: Re: How make app use static sqlite in its package, instead of dylib
- From: Jean-Daniel Dupas <email@hidden>
- Date: Mon, 20 Dec 2010 17:17:47 +0100
Le 20 déc. 2010 à 16:40, Scott Ribe a écrit :
> On Dec 19, 2010, at 10:55 PM, Jerry Krinock wrote:
>
>> Anyhow if someone could confirm that my approach is correct I'd appreciate it.
>
> The linker has an extremely strong preference for dylibs. The fact that your static lib is the wrong architecture is not the problem. The mere presence of the dylib in the same path as your static one will cause the dylib to be used.
>
> For cases like this, where I'm building a static version of a lib that is available as a dylib with the standard system, I put the static lib somewhere else entirely. Like in a sys-libs folder within my project.
An other solution is to simply give your static library an other name that does not conflict with existing dylib. So you don't even have to bother with linker folder search order.
-- Jean-Daniel
_______________________________________________
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