Re: [CMake] How to build and reference dlopen-able libraries?

2014-09-06 Thread Hendrik Sattler
On 6. September 2014 05:49:44 MESZ, J Decker d3c...@gmail.com wrote: you'll need separate includes for dlopen thing, because you'll need the functions declares are pointers... Not really void (*f)( void ); or typedefed as functions typedef void (*some_function_type)( void ); some_function_type

Re: [CMake] How to build and reference dlopen-able libraries?

2014-09-06 Thread J Decker
And without defining variables to get the functions stored into, how do you propose to actually use the functions loaded? Standard headers will provide prototypes, but those will be useless. On Sat, Sep 6, 2014 at 12:58 AM, Hendrik Sattler p...@hendrik-sattler.de wrote: On 6. September 2014

[CMake] How to build and reference dlopen-able libraries?

2014-09-05 Thread Ted Middleton
Just wondering if there's a nice way of getting a library target's includes but not linking to it, so I can use dlopen() on it instead. If I want to build a shared library that gets implicitly loaded by an executable, I would do this: mylib/CMakeLists.txt: add_library( mylib SHARED

Re: [CMake] How to build and reference dlopen-able libraries?

2014-09-05 Thread Nils Gladitz
On 06.09.2014 00:44, Ted Middleton wrote: Just wondering if there's a nice way of getting a library target's includes but not linking to it, so I can use dlopen() on it instead. If I want to build a shared library that gets implicitly loaded by an executable, I would do this: