Re: cannot load library at @executable path/ openvrm
Re: cannot load library at @executable path/ openvrm
- Subject: Re: cannot load library at @executable path/ openvrm
- From: Christiaan Hofman <email@hidden>
- Date: Tue, 18 May 2010 19:21:17 +0200
On May 18, 2010, at 19:08, Ignacio Enriquez wrote:
> On Wed, May 19, 2010 at 1:54 AM, Christiaan Hofman <email@hidden> wrote:
>>
>> On May 18, 2010, at 18:32, Ignacio Enriquez wrote:
>>
>>> Hi all
>>> I get the following error when trying to run my c++ application
>>>
>>> dyld: Library not loaded: @executable_path/libboost_thread-1_33_1.dylib
>>> Referenced from:
>>> /Users/nacho4d/Documents/3DMultiMap/MultiMap/build/Debug/MultiMapInteraction
>>> Reason: image not found
>>> sharedlibrary apply-load-rules all
>>> Data Formatters temporarily unavailable, will re-try after a
>>> 'continue'. (Cannot call into the loader at present, it is locked.)
>>>
>>> I have libbosst_thread-1_33_1.dylib copied to my target,
>>>
>>> I wonder what is wrong? Is there any other place inside my project I
>>> should check? or maybe a way to check if they are really copied to the
>>> target?
>>>
>>> I've trying to run this app in my Mac for quite long and this is the
>>> last error (I hope)
>>>
>>> Any help is appreciated.
>>> Thanks.
>>>
>>>
>>> Ignacio
>>
>> Apparently you did not copy it to the correct location in your target,
>
> How can I check they are really copied in the target? (I can see it
> inside copied group of my target)
>
I am not talking about the groups in your project file, I am talking about the built product, i.e. the app bundle.
> or the library has the wrong installation directory. It's looking in
> the same place as where the executable itself is located, that seems
> to be the wrong place, as embedded libraries should normally be placed
> in the Frameworks folder.
>>
> Or how can I check the installation directory in the library? (If I
> can, what should I look for?)
otool -D /path/to/the/library/executable
> BTW: This libboost_thread-1_33_1.dylib is the one inside ARToolKit,
> which I downloaded from source forge.
>
Perhaps you can file a bug report on that, they should use @executable_path/../Frameworks/libboost_thread-1_33_1.dylib instead of @executable_path/libboost_thread-1_33_1.dylib.
You could also build your own version with the correct build setting, as this is an OSS project.
With the current setting, you should copy the library in the MacOS folder, which in Xcode is referenced as "Executables" in the popup for a copy files build phase.
Christiaan
>
> Ignacio
_______________________________________________
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