Thanks for the extra explanation, that's helpful info. About the C API: yes
I'm already using that one successfully on Windows to build my [ultraleap]
external. And that API even works for both the Leap Motion and Ultraleap
hardware, which is nice. Unfortunately, that API (LeapC) no longer
To be more specific, the linker error itself is most likely caused by
name mangling differences. When you include the header file in your
project, the class/function definitions use /your /compiler's name
mangling, but the accompanying DLL has been built with /another
/compiler, using a
Great tips, thanks to you both!
On Tue, Jan 3, 2023 at 3:45 PM Christof Ressi
wrote:
> That said, would it be worth my time to try and set up a Visual Studio
> project and build against the old C++ library there?
>
> If you use CMake, you only have to specify the appropriate Visual Studio
>
That said, would it be worth my time to try and set up a Visual Studio
project and build against the old C++ library there?
If you use CMake, you only have to specify the appropriate Visual Studio
generator. That's it. You build your project with
cmake --build .
and it will automatically
Thanks IOhannes, this is helpful and it explains why I was able to link to
the newest Leap library on Windows for the ultraleap external - that one is
in straight C.
That said, would it be worth my time to try and set up a Visual Studio
project and build against the old C++ library there? I only
Am 3. Jänner 2023 23:10:59 MEZ schrieb William Brent :
>
>x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
>src/leapmotion.o:leapmotion.cpp:(.text+0x411): undefined reference to
>`Leap::Frame::timestamp() const'
C++ is a fantastic language.
Unfortunately it is not really
Hello all,
I'm finishing up work on new [leapmotion] and [ultraleap] externals and
trying to make them available for all compatible platforms (I'll skip the
rundown of which hardware and SDKs work on which platforms here unless it's
helpful).
I've got everything working except the [leapmotion]
