-
Notifications
You must be signed in to change notification settings - Fork 31
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
toupper or isspace is not a member of std. #10
Comments
I managed to "solve" the errors by removing the std part of every However, now I am getting the following warnings (they are warnings, nevertheless):
It might be working but this is just a patch in my local version of Cryptopp-PEM. A fix must be addressed. |
Thanks @RazviOverflow. Sorry about the troubles. I don't think I have ever compiled this on Visual Studio. Let me give it a whirl. I'd like to try to keep The problem with |
Thanks again @RazviOverflow. Give Commit ac4c98d779bfa8e4 a try. It compiles cleanly under Visual Studio using We needed to avoid |
Hello again @noloader, you are most welcome! Glad to help. I manually changed everything in order to make it compile. Tomorrow I will try your ac4c98d779bfa8e4 and afterwards post here my feedback. Until then, could you tell me how did you import/compile it in MVS? Did you import latest Crypto++ version and add headers and sources into their respective folders or there is something else to it? |
I test the source files from the command line using cryptest.nmake:
Once |
You will also need Commit 3833d017c6fb. I missed the compile error last time around. I think Nmake failed to build a file that was updated. Or I forgot to copy the updated file into the |
I explicitly need to use MVS for this project. I will describe step-by-step how I managed to get it working, just for the record @noloader.
Then I built the project again and it finished with no errors and just 3
Hope it helps. |
I added the precompiled header include at Commit 2b20f9292e3c. That probably should have been there a long time ago. The linker warnings are par for the course. We have not been able to squash them. They are present because the *.cpp file is included in the *.h file in certain configurations. There's also a |
I'm trying to use Crypto++ with cryptopp-pem in Windows Visual Studio 2017 (moving the project from a Unix-based environment to Windows) and I'm facing several problems.
After manually adding the sources and headers in their respective cryptlib folders, I had to add
#include "pch.h"
at the beginning ofpem_commong.cpp
,pem_read.cpp
andpem.write.cpp
in order to not get the errors related to the precompiled header (pch.h).Now, when I try to build cryptlib I get several errors related to C++, regardless of the configuration (it happens either in Debug or Release builds).
When trying to build or compile
pem_read.cpp
the following errors appear:When trying to build or compile
pem_write.cpp
the following errors appear:On the other hand,
pem_common.cpp
compiles or builds without problems.The text was updated successfully, but these errors were encountered: