Sorry for a 2nd reply but I just looked at what ImageMagick is.
If your app uses this library, you don't need to (and shouldn't) install it at the root of the OS. Instead, put the shared library into your application bundle. That way your app doesn't need authorization, doesn't alter the OS, and is entirely self-contained. I do this in my code — my current app's got about four open-source libraries embedded in it at last count. (The details of how to do this are off-topic for this list; check the Xcode documenation, or ask on Apple's Xcode mailing list.)
If there's some reason the library absolutely has to be installed into the OS itself, consider making an installer package for your app, which installs the library too. That way your app doesn't have to deal with the installation process.
Finally, unless you're porting an existing codebase that already uses ImageMagic, consider using Quartz [aka CoreGraphics] APIs instead. They do all of the same stuff and are probably faster because they've been highly optimized for the Mac architecture (including hardware acceleration.)
Remember, the less your app does as root, the less your users can blame you for if something goes wrong :)
—Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
