Any plans for Visual Studio 2017?

[Andrew Marlow]

Hello everyone,

I am working on a project that uses cryptopp with Visual Studio 2015. I am
currently thinking about what we would have to do in order to move to
Visual Studio 2017. Part of this is ensuring that all third party libraries
can be relatively easily be built using VS2017. Are there any plans for
cryptopp to support VS2017 please?

Regards,

Andrew Marlow

[Marcel Raad]

Hi Andrew,

Am 21.12.2017 10:34 schrieb "Andrew Marlow" <***@gmail.com>:

Are there any plans for cryptopp to support VS2017 please?


the current master branch does support it. I'm using version 5.6.5 + some
patches from git master with VS2017 myself.

Marcel

[James Young]

Hello,

On the github page, there seems to be a reference to VS 2017 for the latest
release of crypto++ 7.0.0.

I'm on Win 10 with the latest patches and updates, and can't figure out how
to work with crypto++ using Visual Studio 2017 Community Edition. It seems
to build fine, although there are some lines that fly by occasionally which
I can't interpret.

I open cryptest.sln in Visual Studio 2017 CE and batch build everything.
It seems to work out. I've tried the 8.1 SDK and Win 10 SDK.

But when I try to use it in a project, after adding the include path and
the output path with the x64 cryptlib.lib file, I always get linker
errors. I use the same SDK version and same x64 config for my projects, so
I'm not entirely sure what's going on.

Does anyone else use VS 2017 CE and successfully build crypto++ 7.0.0 on
Win10? If yes, did you have to configure anything to get it to build, and
link when using it in other projects?

Thanks for any tips. I'm stuck and there are no VS build instructions for
VS2017 Crypto++ 7.0.0 on the Wiki, although maybe I'm missing something
obvious...

James

Post by Andrew Marlow
Hello everyone,
I am working on a project that uses cryptopp with Visual Studio 2015. I am
currently thinking about what we would have to do in order to move to
Visual Studio 2017. Part of this is ensuring that all third party libraries
can be relatively easily be built using VS2017. Are there any plans for
cryptopp to support VS2017 please?
Regards,
Andrew Marlow

[Marcel Raad]

Hi James,

Post by James Young
But when I try to use it in a project, after adding the include path and
the output path with the x64 cryptlib.lib file, I always get linker
errors. I use the same SDK version and same x64 config for my projects, so
I'm not entirely sure what's going on.
Does anyone else use VS 2017 CE and successfully build crypto++ 7.0.0 on
Win10? If yes, did you have to configure anything to get it to build, and
link when using it in other projects?

what errors do you get? Are you using the same C runtime for Crypto++ and
your project (static vs. dynamic)?

All I had to do was setting the include and library directory and adding
cryptlib.lib to the linker input.

Marcel