I’ve noticed an issue after I downloaded the package. There are some workarounds for it as I’ve read on StackOverflow, however it was simpler just to cmake it without backtrace option and comment out these lines from the list: Since you haven’t provided windows binaries for C++ development, I decided to compile it from source, but (latest) MinGW doesn’t have the dbghelp library. I don’t know what /WX /W4 and /EHsc are doing (probably the link above would have explained it if I had opened that :)), but CodeBlocks didn’t compile it with that line enabled.įurthermore, since mingw-g++ haven’t found the lib using -ldbghelp flag, I also turned FL_LIBS dbghelp off. I managed to compile it using Cmake-gui (CodeBlocks MinGW makefiles), and MinGW (4.7.1) initiated from CodeBlocks project. The sample application you posted in the C++ section also worked fine.

If I can advise, you should include a non-stripped dll so the users could make imports (using dlltool or such) for their compilers, instead of recompiling the whole package. This topic was modified 8 years, 5 months ago by Unknown.Īs far as I know, dlls can be compiled with debug/symbol information, or without it. In the first case, it is possible to create a library only from the dll file, that a compiler can use in later projects. For example mingw has its /lib subdirectory containing the libraries in order to resolve external references. These *.a files can be generated using the dll file, some grepping and a program like dlltool.

In the downloadable windows package I only found a fuzzylite.dll file that seems to be stripped.

Codeblocks compiler matlab