TA / TF v4.0.4 statically linked to a .dll in Windows

Hallo,

I'm facing a strange situation under Windows after the port I made from v3.4.7 to v4.0.4.I've the same C++ application that works in 2 different ways:1) During the development I am using the dynamic linking with TA/TF libraries: everything works fine.2) For the deployment instead, I am recompiling the project with CMake + TA/TF static libraries to obtain a .dll. In this second case I don't get errors in compilation, my application starts regularly but the activation fails for both TA and TF.a) in TF TF_RequestLease(...) returns TF_FAIL (but TF Server provides a lease as well and TF_PDetsFromPath - TF_GetHandle - TF_SetLeaseCallback - TF_SaveServer return TF_OK)b) in TA TA_PDetsFromPath, TA_GetHandle return TF_OK but the first TA_CheckAndSavePKey before TA_Activate fails (TA_FAIL)

To add additional smoke to the story I've also developed a small executable statically linked only to TA / TF (but the latter is not used) that simply tests whether a license is valid and activated, and deactivates it. This works.

I'm almost sure that I'm doing something wrong in CMake but the only message that I get is during the linking phase:"TurboFloat-MD.lib(TurboFloat.obj) : MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance".

Any suggestion? Thanks in advance

Alessandro