-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building on Windows using MSVC #169
Comments
Okay, so a little update, when using static version of CryptoPP, there are different errors:
So the library must be dynamic. I think the problem is that I am not building the CryptoPP library correctly, which is maybe a question to ask elsewhere. |
Thanks for highlighting your solution in such great detail @Irisbus ! Much appreciated! |
I am sharing some of my other notes about building Vanetza with MSVC. Maybe someone will find it useful. BuildingPrerequisities:I recommend to put those libraries in the folder
Generate Visual Studio projectOpen Visual Studio Developer PowerShell, change to Vanetza directory. Issue those commands (change directories accordingly):
Note 1: credit for the last flag Note 2: command for static libraries:
Note 3: For Now the project should be generated. Project changesIn order for the project to be build, some changes must be made (everytime the project is generated).
Source code changesIn the source code, some changes must be made (those changes are done only one time).
Now you can select the Release configuration and build the project. Other resources |
Hi,
I am trying to build Vanetza on windows using Microsoft Visual Studio 17.3.6. I have some problems with the CryptoPP library. When I build as static library, it seems correct. However, when I try to build as shared library, I get following errors:
I built CryptoPP version 8.7.0 also from Visual Studio using configuration DLL-Import Release. I tried changing define
CRYPTOPP_ENABLE_COMPLIANCE_WITH_FIPS_140_2
in fips140.cpp to 1 but it did not help. I also tried to use older version of CryptoPP, 8.3.0, but it also did not help.Does someone have any idea what could I be doing wrong?
Except this, there are also some problems in RegionalExtensions.h file (it cannot be compiled because of the empty enums) but I managed to somehow resolve those.
Regards,
Karel
The text was updated successfully, but these errors were encountered: