Re: linking to private frameworks
Re: linking to private frameworks
- Subject: Re: linking to private frameworks
- From: Greg Hurrell <email@hidden>
- Date: Thu, 30 Sep 2004 13:29:13 +0200
El 30/09/2004, a las 6:51, Eric Ocean escribió:
I'm trying to override a method in a private framework for an
application I own. I generated a header for the class (using
RuntimeBrowser), and then created my category to override the method.
I'm loading the category implementation via SIMBL.
If it's for an application that you own, I don't know why you'd need to
use SIMBL. Just having the category in your project and linking to the
framework should be enough. SIMBL is for injecting code into other
apps, not your own.
The linker complains, so I add the private framework to my project,
but it still complains.
I'm assuming that's because the private framework contains no headers,
but I don't see why that would matter to the linker.
It's a good idea to make your own header, in any case, that lists the
functions/methods etc in the private framework that you'll be making
reference to. This at least will quell the compiler warnings.
As for the linker warnings, you haven't said what they are.
Any suggestions? I know I could delve deep and manipulate the
objective-c runtime dynamically, but I don't want to go that far just
yet.
Sounds like it would definitely be overkill!
Cheers
Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden