LNK2001 unresolved external symbol for SHA3 class members - c++

Question

I am need to calculate SHA3 in my program as well as use AES in my sockets and have decided to use crypto++ library.
I am new to Visual Studio environment with no prior experience on visual studios but have extensively worked on g++ (linux/mingw-w64). One of the third part library I am using recommends Visual Studios (causes linker error when used with g++).
I am getting an linker error.
Error :
LNK2001 unresolved external symbol "public: virtual void __cdecl CryptoPP::SHA3::Update(unsigned char const *,unsigned __int64)" (?Update#SHA3#CryptoPP##UEAAXPEBE_K#Z) ConsoleApplication2 C:\Users\Admin\source\repos\ConsoleApplication2\ConsoleApplication2\ConsoleApplication2.obj 1
LNK2019 unresolved external symbol "public: virtual void __cdecl CryptoPP::SHA3::Restart(void)" (?Restart#SHA3#CryptoPP##UEAAXXZ) referenced in function "public: __cdecl CryptoPP::SHA3::SHA3(unsigned int)" (??0SHA3#CryptoPP##QEAA#I#Z) ConsoleApplication2 C:\Users\Admin\source\repos\ConsoleApplication2\ConsoleApplication2\ConsoleApplication2.obj 1
Error LNK2001 unresolved external symbol "public: virtual void __cdecl CryptoPP::SHA3::TruncatedFinal(unsigned char *,unsigned __int64)" (?TruncatedFinal#SHA3#CryptoPP##UEAAXPEAE_K#Z) ConsoleApplication2 C:\Users\Admin\source\repos\ConsoleApplication2\ConsoleApplication2\ConsoleApplication2.obj 1
The same code works properly in g++(mingw-w64 - I am using dll created in mingw-w64)
OS : Windows 10 Pro 64 bit
Development Environment : Visual Studios 2017
Target : Debug x64
Source :
#include <sha3.h>
#include <filters.h>
#include <hex.h>
#include <string>
#include <iostream>
#include <vector>
#include <algorithm>
#include <iostream>
#include <base64.h>
int main()
{
CryptoPP::SHA3_512 hash;
std::cout << hash.AlgorithmName() << " Test." << std::endl;
std::string in = "The quick brown fox jumps over the lazy dog";
std::vector<CryptoPP::byte> out(hash.DigestSize());
hash.CalculateTruncatedDigest(&out[0], hash.DigestSize(), reinterpret_cast<CryptoPP::byte*>(&in[0]), in.size());
std::cout << in << std::endl;
std::cout.setf(std::ios::hex, std::ios::basefield);
for_each(out.begin(), out.end(), [](CryptoPP::byte i) {
printf("%x", i);
});
std::cout << "Original String : " << str << std::endl;
return 0;
}
Kindly advice me how to load (copy) all generated dll in some common folder just like the make install command (facility) in gcc.
Edit :
I have added cryptopp.lib in additional dependencies and added the folder containing both cryptopp.lib and cryptopp.dll in Additional Library Directory. I have added the directory in Path environment variable. I have selected Multi Threaded Debug Dll in Debug x64 configuration during dll generation in cryptolib project.

Answer 1

Paul Sanders is quite correct, the classes and functions you want to use from the crypto++ DLL must be qualified with _declspec(dllexport) / _declspec(dllimport).
Some of this has been done already, as described in Crypto++ wiki page for Fips dll. It works thru the preprocessor macro CRYPTOPP_DLL, which is defined in the crypto++ header config.h and used in fips140.h.
There is a problem though - not all the algorithms you want are in FIPS and, as you have found, are not exported for use in a DLL. You could modify other headers to add the DLL export/imports but note that the wiki page suggests : "If you really need a DLL, then provide a wrapper DLL that links against the static library.". Rather than wrap every component of every crypto++ algorithm you use, it would be more convenient to encapsulate entire operations into a high level class or function which is then exported/imported from your wrapper DLL.
GCC exports everything by default, which is why shared libraries worked for you on Linux.

Answer 2

You need to link your app against (I believe) cryptopp.lib. This probably comes in separate versions for 32 bit and 64 bit (I believe the names in the import table differ) so make sure you use the right one.
You can tell Visual Studio to do this via Solution Explorer -> Right-click on project name -> Properties -> Linker -> Input -> Additional Dependencies. Then just build again.
Your app will need to be able to find the DLL at runtime, not at link time. If it can't, you will get an error message telling you so when you try to run it. Copying the DLL to the same directory as the executable is what people usually do (and I hope there's no issue using a DLL created by mingw in Visual Studio).