02-20-2025 04:39 PM
FTDI has confirmed that their .lib cannot be used on the LabWindows compiler.
...which is odd. We have been using their DLL-linking .lib without issue for almost a decade.
I guess we stick with using the DLL version.
02-21-2025 03:05 PM
For anyone else who runs into it, here is the scoop. Special thanks to FTDI for their great support with this.
1. The FTDI library was compiled using Microsoft Visual Studio 2015. Because of that, the STATIC libraries is produces cannot be linked with Clang (LabWindows) or GCC. I need to switch to using Visual Studio to create my DLL.
2. In Visual Studio, you must install the 2015 toolkit, and Windows 10 SDK, and use that with your project. FTDI was built with this, and needs it to link.
I was able to build my DLL inside of Visual Studio 2015 and create a .dll and .lib that included the static FTDI library. That DLL/.lib has now been tested via GCC and Clang 3.3 successfully.
Huzzah!