Hi Peter,
thanks, I have added a typedef in libapl.h. SVN 1049.
/// Jürgen
On 05/19/2018 09:53 PM, Peter Teeson
wrote:
Thank you all for your replies. I removed the configure arg
—with-android.
Now there
Thanks Jürgen. Now I have another problem.
The libAPL (libapl) html documentation first line states:
"libapl is a C library,…..” so in theory it should play nicely with Obj-C.
But this tiny test C program is causing me a linker problem that I do not
understand
#include
#include
#include "/usr/l
Hi,
Shouldn't you do something like (removing include libapl.h)
typedef void (*init_libapl_t)(const char*, int);
void* handle =
dlopen("/usr/local/lib/apl/libapl.so",RTLD_NOW|RTLD_GLOBAL);
init_libapl_t init_libapl = (init_libapl_t*)dlsym(handle, "init_libapl");
init_libapl("main", 0);
?
Pet
or just link against libapl (-lapl) and dont use dlopen..
Alexey Veretennikov writes:
> Hi,
>
> Shouldn't you do something like (removing include libapl.h)
>
> typedef void (*init_libapl_t)(const char*, int);
> void* handle =
> dlopen("/usr/local/lib/apl/libapl.so",RTLD_NOW|RTLD_GLOBAL);
>
> ini
Hi Peter,
init_libapl is contained in the libapl.so.
As far as I understand, there are two ways to link libapl with
your application:
1. link it at compile time (with the -lapl linker option) or
2. dlopen() it at runtime (your approach).
Thank you gentlemen for your support. This is all new to me…..
Option 1 sounds reasonable to me. I guess I have to add libapl.so to the Xcode
project.
Sort of like what Apple calls a Framework. I will try that.
What is the -lapl option argument? The Xcode project does have a place to add
Other
2018-05-20 21:44 GMT+02:00 Juergen Sauermann :
> As far as I understand, there are two ways to link libapl with your
> application:
>
> 1. link it at compile time (with the -lapl linker option) or
> 2. dlopen() it at runtime (your approach).
>
> In case 2. the symbol init_libapl is NOT resolved by
