Quantcast
Channel: Gemalto Sentinel Customer Discussions
Viewing all 38 articles
Browse latest View live

Visual Studio 2015 build of spromeps.lib

$
0
0
Hello,

I have run into a problem with unresolved externals (vsprintf, vfprintf) when trying to build a project that uses spromeps.lib in the newly released Visual Studio 2015. It worked fine using Visual Studio 2013. So I am looking to find out my options for moving forward, whether the library can be rebuilt from an available SDK download, or maybe there is a proposed workaround, etc.

Thanks,

Keith Dennison

Re : Visual Studio 2015 build of spromeps.lib

$
0
0
Dear Keith Dennison,

Sentinel SuperPro being a legacy product in maintenance mode, we will not add "official" support for new Visual Studio releases.
Regarding the missing definition symbols "vsprintf" & "vfprintf", it occurs because Microsoft has made changes in the location of legacy C functions.
To keep working with the static library (spromeps.lib), these 2 legacy definitions symbols can be resolved by linking "legacy_stdio_definitions.lib" in your Visual Studio 2015 project.

Regards,
Olivier

Re : Visual Studio 2015 build of spromeps.lib

$
0
0
Hi,

even when linking with legacy_stdio_definitions.lib I get some unresolved external symbols:

spromeps.lib(util1.obj) : error LNK2019: unresolved external symbol __imp___iob referenced in function _SNTLSSP710DC
spromeps.lib(procopts.obj) : error LNK2001: unresolved external symbol __imp___iob
spromeps.lib(strutil.obj) : error LNK2019: unresolved external symbol __imp___pctype referenced in function _SNTLSSP710PP
spromeps.lib(xmlParseConfig.obj) : error LNK2001: unresolved external symbol __imp___pctype
spromeps.lib(strutil.obj) : error LNK2019: unresolved external symbol __imp____mb_cur_max referenced in function _SNTLSSP710PP
spromeps.lib(xmlParseConfig.obj) : error LNK2001: unresolved external symbol __imp____mb_cur_max

Is it possible to get an "unofficial" VS 2015 build of spromeps.lib?

Regards,
Kenneth

Re : Visual Studio 2015 build of spromeps.lib

Re : Visual Studio 2015 build of spromeps.lib

$
0
0
Hello.

Like Keith, is also my request to have an updated version of Sentinel SuperPro libraries for Visual Studio 2015.

I know that is a legacy product but is still present on the market. Provide  an updated version of Sentinel SuperPro libraries for new Visual studio compiler could be a value and appreciated solution.

Regards.
Gianluca

Re : Visual Studio 2015 build of spromeps.lib

$
0
0
Hi Gianluca,

Hope you are doing good.

SuperPro being our legacy product, enhancements are not possible over the same.

You can check with our latest range of products for support over Visual studio 2015.

Thanks,
SafeNet Support

Re : Visual Studio 2015 build of spromeps.lib

$
0
0
Dear customers,

With the latest Microsoft update of Visual Studio 2015, our SuperPro static library 7.1.0 built with the multi-threaded MT flag is working fine on both 32 and 64 bit after linking with library legacy_stdio_definitions.lib

Microsoft has resolved this issue in latest update.

Note that the SuperPro dynamic library 7.1.0, sx32w.dll works fine as well.

Regards,
Olivier

Re : Visual Studio 2015 build of spromeps.lib

$
0
0
Dear Oliver,
it's true that Sentinel SuperPro static library 7.1.0 built with the multi-threaded MT flag is working fine.
But it's also true that Sentinel SuperPro static library 7.1.0 built with the multi-threaded DLL  /MD flag is not working at all.
It seems that the only way to use Sentinel SuperPro libraries with Visual studio 2015 in programs that needs to be compiled with /MD flag is to obtain an updated version of the libraries recompiled with VS 2015.


Gianluca.


Re : Visual Studio 2015 build of spromeps.lib

$
0
0

Dear Gianluca,

Yes, we are aware that the SuperPro static compiled with /MD flag is still not working within VS2015 projects.

There is still an issue with the new Microsoft's "legacy_stdio_definitions.lib" library.

It was reported to Microsoft that the legacy_stdio_definitions.lib library is missing the __imp_ -prefixed aliases.

Microsoft has already added them for MT libraries of legacy_stdio_definitions.lib with latest update. Similarly they still need to add the same for MD libraries.

///////////
Hello,

Thank you for reporting this issue. This problem is a result of some of the redesign work that went into the runtime libraries for Visual Studio 2015. As a workaround for the problem, please link with legacy_stdio_definitions.lib. This library has external definitions of most of the symbols that the Windows SDK (and many other libraries) require but which are not present in the new runtime libraries. This library should resolve most link issues.

There are several libraries in the Windows 8.1 SDK that have additional dependencies that are not satisfied by this legacy_stdio_definitions.lib library. The final release of Visual Studio 2015 will include an updated Windows SDK that resolves remaining issues. Additionally, the legacy_stdio_definitions.lib library is currently missing the __imp_-prefixed aliases required by some libraries; these will be added in a future builds of Visual Studio 2015.

We are continuing to work on improving the developer experience for future builds of Visual Studio 2015.

Please feel free to contact me directly via e-mail if you have further questions.

Sincerely,

James McNellis
Visual C++ Libraries
james.mcnellis@microsoft.com
///////////


I believe you already reported this issue to Safenet Inc Support, as part of Service request 1-812961183.

My colleagues will follow this request with you.

Regards,
Olivier

spromeps.lib with Visual Studio 2015

$
0
0
We also have unresolved externals  issues with our applications when we link with in VS 2015.  We have to use that version of VS because the host application we plug into is written by a third party, in VS 2015.

If you are OK to sell us the Superpro keys (which you regularly do) then really you should not consider it to be a legacy product.

To port all 500+ of our users to a newer security system is not practical for us, and I would imagine that porting spromeps.lib to VS 2015 so it can be used with /MD is a fairly trivial task for most competent developers.

If we cannot use spromeps.lib with /MD in VS 2015 then we will have to go elsewhere for a security product in the future, or develop our own.

Please can you escalate this problem internally, as without a fix we can't see any future for us with Gemalto.

Thank you,
David

Re : spromeps.lib with Visual Studio 2015

Re : spromeps.lib with Visual Studio 2015

$
0
0
We have the same problem.

We would like to receive an updated version of spromeps.lib compatible with MS VS 2015 in order to be able to compile with flad /MD.

Regards

Gianluca

Re : Visual Studio 2015 build of spromeps.lib

$
0
0
Some news about this issue?
Regards
Gianluca

Re : spromeps.lib with Visual Studio 2015

Re : Visual Studio 2015 build of spromeps.lib

$
0
0

Dear Customer,

Support Ticket 1-812961183 is currently closed.
Please get back to support@safenet-inc.com to get your request escalated again.

Regards,
Olivier


Re : spromeps.lib with Visual Studio 2015

$
0
0

Hi,

New Superpro C/C++ Client Libraries v 7.1.0.11 /MD and /MT compatible with Visual Studio 2015 are now available.

These updated Libraries have no dependency on legacy_stdio_definitions.lib

Link to Safenet Knowledge Base (requires Service portal Login) :

https://kb.safenet-inc.com/kb/link.jsp?ID=DOW4436

Regards,
Olivier

Re : Visual Studio 2015 build of spromeps.lib

$
0
0

Hi,

New Superpro C/C++ Client Libraries v 7.1.0.11 /MD and /MT compatible with Visual Studio 2015 are now available.

These updated Libraries have no dependency on "legacy_stdio_definitions.lib"

Link to Safenet Knowledge Base (requires Service portal Login) :

https://kb.safenet-inc.com/kb/link.jsp?ID=DOW4436

Regards,
Olivier

Re : Visual Studio 2015 build of spromeps.lib

$
0
0

Dear Gianluca,

Yes, we are aware that the SuperPro static compiled with /MD flag is still not working within VS2015 projects.

There is still an issue with the new Microsoft's "legacy_stdio_definitions.lib" library.

It was reported to Microsoft that the legacy_stdio_definitions.lib library is missing the __imp_ -prefixed aliases.

Microsoft has already added them for MT libraries of legacy_stdio_definitions.lib with latest update. Similarly they still need to add the same for MD libraries.

///////////
Hello,

Thank you for reporting this issue. This problem is a result of some of the redesign work that went into the runtime libraries for Visual Studio 2015. As a workaround for the problem, please link with legacy_stdio_definitions.lib. This library has external definitions of most of the symbols that the Windows SDK (and many other libraries) require but which are not present in the new runtime libraries. This library should resolve most link issues.

There are several libraries in the Windows 8.1 SDK that have additional dependencies that are not satisfied by this legacy_stdio_definitions.lib library. The final release of Visual Studio 2015 will include an updated Windows SDK that resolves remaining issues. Additionally, the legacy_stdio_definitions.lib library is currently missing the __imp_-prefixed aliases required by some libraries; these will be added in a future builds of Visual Studio 2015.

We are continuing to work on improving the developer experience for future builds of Visual Studio 2015.

Please feel free to contact me directly via e-mail if you have further questions.

Sincerely,

James McNellis
Visual C++ Libraries
james.mcnellis@microsoft.com
///////////


I believe you already reported this issue to Safenet Inc Support, as part of Service request 1-812961183.

My colleagues will follow this request with you.

Regards,
Olivier

spromeps.lib with Visual Studio 2015

$
0
0
We also have unresolved externals  issues with our applications when we link with in VS 2015.  We have to use that version of VS because the host application we plug into is written by a third party, in VS 2015.

If you are OK to sell us the Superpro keys (which you regularly do) then really you should not consider it to be a legacy product.

To port all 500+ of our users to a newer security system is not practical for us, and I would imagine that porting spromeps.lib to VS 2015 so it can be used with /MD is a fairly trivial task for most competent developers.

If we cannot use spromeps.lib with /MD in VS 2015 then we will have to go elsewhere for a security product in the future, or develop our own.

Please can you escalate this problem internally, as without a fix we can't see any future for us with Gemalto.

Thank you,
David

Re : spromeps.lib with Visual Studio 2015

Viewing all 38 articles
Browse latest View live