Re: including dylibs in my .app
Re: including dylibs in my .app
- Subject: Re: including dylibs in my .app
- From: Taylor Holliday <email@hidden>
- Date: Fri, 29 May 2009 10:16:14 -0700
Is it really that bad to potentially duplicate a few libs? I'd rather
have a self-contained .app that doesn't require an installer.
On Fri, May 29, 2009 at 10:00 AM, Tommy Nordgren
<email@hidden> wrote:
>
> On May 29, 2009, at 3:15 AM, Nick Zitzmann wrote:
>
>>
>> On May 28, 2009, at 4:56 PM, Taylor Holliday wrote:
>>
>>> How can I include those
>>> libs in my app so it can be used on machines which don't have the
>>> required libs in /opt/local.
>>
>>
>> Copy them into your app bundle, then add a shell script build phase to the
>> project that runs install_name_tool to adjust the paths of the library in
>> both the library and the application that uses it. See the man page for
>> install_name_tool for more details.
>>
>> Nick Zitzmann
>> <http://seiryu.home.comcast.net/>
>>
>
> With that "solution" code won't be shared by other apps. It's
> probably better to write an installer,
> to install a copy of the library at the same path as the developer machine
>
> ----------------------------------
> Skinheads are so tired of immigration, that they are going to move to a
> country that don't accept immigrants!
> Tommy Nordgren
> 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
>
_______________________________________________
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