On Aug 10, 2008, at 6:39 PM, Uli Kusterer wrote:

On 10.08.2008, at 19:38, Bob Sabiston wrote:
I got my Cocoa bundle to compile on the Intel machine. It still doesn't load within my app, though. Is there something special I need to do to include it in my project? I just dragged it in on the left, amongst all the other types of files, and it gave me a menu of targets from which I selected the correct one. But the load is still failing. I'm using the function below, gotten from Apple's examples. Anyone know what could be the problem? CFBundleCreate is just setting bundlePtr to 0, I don't know why.


I've done stuff like that and it worked fine for me (heck, I've loaded CFM bundles into Mach-O apps). What template did you use as a basis for your bundle? You keep saying bundle, but the variable names mention frameworks. Now, there are different ways of building stuff like that. E.g. frameworks contain a path they expect to be loaded at (installation path setting), while bundles as they're used for plugins generally don't.

Did you perhaps mix those up? Alternately, are you perhaps mixing debug and release builds? Anything not 100% homogeneous in there?

Cheers,
-- Uli Kusterer

Well, I checked the builds -- one was Debug, one was Release. Now they are both Debug, and it does get farther than it did before. CFBundleCreate() is returning a valid bundle now, instead of 0. But then I try to use it, starting with this:

funcPtr = (FunkyPtr) CFBundleGetFunctionPointerForName(runbundleRef, CFSTR("initializeRTBundle"));

It returns 0 for the function pointer. So something still isn't working. Anyone know what could be the problem?

Thanks
Bob


_______________________________________________

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]

Reply via email to