Yes, it would have been useful information that you were trying to use a library built with MSVC in a project using MingW. Qt is not a compiler and works equally well with Microsoft, GNU, and other compilers. Unfortunately you didn't provide that information, or any other error/warning/diagnostic information, which was my point. We might have guessed binary incompatibility, or that you had no idea how to link a 3rd party library into an program, or that the library was dynamically linked and not being found at run time, ...
Link your application to the soundtouch.a file.So I compiled it now with MSYS (after fixing a totally messed up installation) and recieved a half-working library.
Now I have:
soundtouch.a
soundtouch.la
pkgconfig/soundtouch.pc
What do I have to do with them?
Good so you have your linker library search path set correctly for soundtouch.a to be found.I tried to link with "LIBS += -lsoundtouch" which let me compile my project and run it,
Not enough information. Gdb crashes? Your program crashes and gdb reports it? Is a backtrace produced? Any other (error) output? Can you produce a minimal, complete program that reproduces the behaviour? Is the compiler version in your MSYS installation the same compiler, or the same version, as the one you are building your application with?BUT if I want to debug, it crashes right away with "gdb exited unexpectedly (code 1)"
No. The library is statically linked into your application executable and a copy is not needed on the target machine. The other two files are information files for other utilities (libtools and pkgconfig) that can be used to configure projects that need to find the library.Do I have to place the above files at a certain location? I don't know what to do with the .la and the .pc file.





Reply With Quote
Bookmarks