Using TurboActivate with MinGW 4.8 and QT 4.8.1 on Win

Hi,

I have a slightly older project that I simply can't migrate to something new at this moment, configuration is:QT 4.8.1/Mingw 4.8.I want static TurboActive library added to the project.

I added TurboActive.h to the project, updated INCLUDEPATH.I defined TURBO... STATIC, and checked that it is correctly processed in TurboActive.hI see that the pragma indicates to TurboActive-MT.lib. I added to the LIBS+= .. .TurboActive-MT.lib from the VisualStudio2010 + curl/crypt libs from the 32 bit, build is for 32 bit.

I get a lot of undefined symbols like:@__security_check_cookie@4 in hmac.obj_CxxFrameHandler3 same ..??1exception2std@@UAE@XZ...From all sort of .obj files.

Help would be appreciated. I would like to use static not dynamic link.Thanks !

Note: under Linux, I added the static lib, linked it, all is working fine, I can activate a license from the server, all is cool, Windows has issues.

You can't use the TurboActivate static libraries with MingW. Why? Because they're compiled with and for Visual Studio.

http://www.mingw.org/wiki/Interoperability_of_Libraries_Created_by_Different_Compiler_Brands

On Windows we recommend using Visual Studio because the binaries created are faster, smaller, and more stable than what MingW generates. Plus, there are free Visual Studio editions: https://www.visualstudio.com/products/visual-studio-community-vs

If you don't want to use Visual Studio, then you can always use the dynamic version of TurboActivate.

You understand of course that each customer has it's own requirements and you can just allign each customer to Visual Studio just because you are using that tool. There is more than VisualStudio in this world...

You should provide support and a way to fix customers problem. It's not that difficult after all...Your recomandation is in fact not a recomandation is in fact a limited use case for your product. At least you should have stated it as a "limitation" not as a recomandation.

Your answer is in fact not an aswer at all...

Thanks 😳

>> "You understand of course that each customer has it's own requirements and you can just allign each customer to Visual Studio just because you are using that tool. There is more than VisualStudio in this world..."

I'm aware of that. But we can't create static libraries for MingW because we can't ensure that the resultant version of TurboActivate would be stable. We could put an enormous amount of developer resources towards creating a MingW static library, and then ensuring it was a stable, but that would not be a good use of our resources at this time.

Especially considering that you can use the dynamic library version of TurboActivate with any language and any compiler.

Dynamic library version worked, not the preferred solution, but it is there.Thanks

Reply
Discard post