• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
dylib problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

dylib problems


  • Subject: dylib problems
  • From: Bill Nalen <email@hidden>
  • Date: Mon, 4 Jul 2005 19:53:39 -0400

This probably isn't a specific Xcode problem per se, but I'd like to see Xcode do more to help me with these kinds of problems.

I'd like to use ImageMagick (Magick++) in my application. I downloaded the installer for 6.1.7 and ran it. Then I created a simple Carbon application to test out it's usage. I added libMagick++. 6.dylib to my project. To my surprise I get a message like this:

dyld: Library not loaded: /usr/local/lib/libWand.6.dylib
  Referenced from: /usr/local/lib/libMagick++.6.dylib
  Reason: image not found

TestIM has exited due to signal 5 (SIGTRAP).

Here's an even more descriptive example (no clue what's going on from this description) from the sample code included with ImageMagick itself.
TestIM has exited due to signal 11 (SIGSEGV).



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. Nothing I do seems to fix the problem. I think I understand that dylib files are dynamically linked libraries like the dll files I'm used to on Windows. 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.


Question 1: can the error messages be made clearer? I have no idea what signal 5 is, nor do I really care to know. Library not found or library not loaded is better. How I can load the library or why it wasn't loaded would be even better.

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)?

Question 3: Is there a way to package up the dylib files I need for my app, into the application itself? I don't want the user to have to run some other package installer before my app, and I don't want to have my package installing things outside the users folder.

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. I've searched for a few hours both on the web and within the documentation to no avail.

Thanks
Bill


_______________________________________________ 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
  • Follow-Ups:
    • Re: dylib problems
      • From: Markus Hitter <email@hidden>
  • Prev by Date: Cross-platform & Cross-SDK
  • Next by Date: Documentation frustrations
  • Previous by thread: Re: Cross-platform & Cross-SDK
  • Next by thread: Re: dylib problems
  • Index(es):
    • Date
    • Thread