Re: dylib problems
Re: dylib problems
- Subject: Re: dylib problems
- From: Markus Hitter <email@hidden>
- Date: Tue, 5 Jul 2005 10:11:44 +0200
Am 05.07.2005 um 01:53 schrieb Bill Nalen:
dyld: Library not loaded: /usr/local/lib/libWand.6.dylib
Referenced from: /usr/local/lib/libMagick++.6.dylib
Reason: image not found
[...]
This means little to me. I'm guessing it cannot find libWand.
6.dylib, however it exists in the same folder as the other dylib.
In the same folder or in /usr/local/lib/ ? It's the latter what matters.
I'd much rather link statically to the library to avoid these kinds
of things, but that doesn't seem to be an option with the
ImageMagick package I downloaded.
You have to build a static lib and remove any chance to link against
the .dylib.
Question 1: can the error messages be made clearer?
The message is pretty clear, IMHO.
I have no idea what signal 5 is, nor do I really care to know.
If you don't care about the error given, why do you complain about
it's message, then?
Apps terminating after a signal > 2 usually means the app "crashed".
Question 2: When I'm linking against a dylib file, I need to be
sure the client machine has that same library file available right?
If I ship this application, how can I know which files I need to
distribute with my application? (all the dylib ones and any
dependencies they might have)?
"otool -L" (type "man otool" in a Terminal window).
Question 3: Is there a way to package up the dylib files I need for
my app, into the application itself?
Search in Xcode's documentation for "embedded framework". While
frameworks are preferred on Mac OS X, the principles for embedding
apply to naked .dylibs as well. framework = .dylib + possibly their
headers + possibly additional resources packaged into a single
directory, arranged to support different versions of the .dylib being
installed at once.
I realize that some of my difficulty arises from the habits I'm
bringing over from Windows. It'd be great if there was a site
somewhere that explained all these things to Windows developers.
This would support you to keep your habits.
Try to understand Mac OS X as a different platform, with a strength
on it's own devlopment environment (Cocoa, Bindings, CoreData) and
different user expectations (simplicity, ease of use). Mac users
didn't buy a Mac to use software cloned from Windows, after all.
I've searched for a few hours both on the web and within the
documentation to no avail.
Start with the tutorials and basics, you'll catch up quickly (Links
are local with Xcode 2.1 installed):
<file:///Developer/ADC Reference Library/documentation/Cocoa/
Conceptual/ObjCTutorial/chapter01/chapter_1_section_1.html#//
apple_ref/doc/uid/20001101>
<file:///Developer/ADC Reference Library/documentation/Cocoa/
Conceptual/CurrencyConverterBindings/01introduction/
chapter_1_section_1.html#//apple_ref/doc/uid/TP40001095-CH202>
<file:///Developer/ADC Reference Library/referencelibrary/
GettingStarted/GS_Cocoa/index.html#//apple_ref/doc/uid/TP30001088>
and sites of great volunteers, like e.g. <http://
www.cocoadevcentral.com/>
HTH,
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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