[Top] / [eMule] / [cleanup]

MetMedic
eMule cleanup
eMule Light
Libraries
Cleanup
0.29a
0.29b
0.29c
0.30a

Crypto++ library

What's needed? Get crypto library from Crypto++™ Library 5.1 project page (SourceForge download).

Note that these build notes are for library release and debug builds. I don't currently see a reason to use FIPS builds.

Because there don't seem to be any general library naming conventions on Windows platform, I named the libraries as:

crypto51.lib
Release build, version 5.1
crypto51D.lib
Debug build, version 5.1

And put the include files to subdirectory crypto51 under include.

As usual, I upped the warning level of Debug build, so you'll get a thousand or so warnings. Didn't start cleaning the code, but at least that indicates that perhaps someone should.. Also, release build is optimized quite heavily.

I'm in the habit of grabbing precompiled headers and program database, too, although I'm not sure what to do with precompiled header file yet.. At least if I happen to learn that I'll have the correct one from build available. Program database is unlikely to be needed, but should I get a crash in cryptolib, it's good to have the database around. Still, those are created to Output Directory now.

Downloads:
My project & solution files.
Header files to put into include-dir.