iOS 6.1 Dynamic Library build and link

时间秒杀一切 提交于 2019-11-29 08:21:01

As Victor Ronin pointed out, "dlsym" is for C symbols. To obtain objective-C class from dylib that you linked at runtime you can use objc runtime functions. In your case:

void* dylibLink = dlopen("/usr/lib/libKDylibTwo.dylib", RTLD_NOW);
id KDylibTwo = [[objc_getClass("KDylibTwo") alloc] init];
[KDylibTwo run];

First line is linking your library at runtime. This is required in order to use code inside of it.

Second line creates instance of class KDylibTwo. objc_getClass function returns class object that you can later use to create instances of this class like you would with any objective-C class - using alloc and init methods. Once you obtained class object with objc_getClass you can work with him like nothing happend. At this point you can forget that you dynamically linked you library at runtime.

Third line is calling run method. As you can see, it's normal objective-C syntax. Nothing is changed because you linked your library at runtime. You can call any method you want.

I have never used dlsym to get a pointer to objective c method (I believe it's not possible to call objective c method through dlsym, but I may be wrong).

However, most important bit of information that second parameter of dlsym should be the symbol name.

Symbol name "run" will work only for C function. Something like:

EXPORT void run()
{
 NSLog(@"Run");
}

Object C method has more complex symbol names and as I said, I am not sure whether they could be passed to dlsym at all.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!