You can still add Crypto++ source files directly to your project. Just
keep adding files to satisfy link errors, and eventually it will stop
complaining.
Also, I just checked in some changes that reduces source file
dependencies. Basically, dll.cpp is always required. It used to depend on
fipstest.cpp, and now it shouldn't. Fipstest.cpp depends on a bunch of
other source files, so avoid adding it to your project if you don't need
to use the FIPS 140 self tests.
On Tue, Oct 14, 2003 at 03:05:05PM +0900, [EMAIL PROTECTED] wrote:
> Hello.
> Browsing CVS and this list I had found some important fixes for my
> use of Crypto++ were made, so I pulled the latest "c5" source from CVS
> and tried it.
>
> I usually use Crypto++ by simply adding relevant Crypto++ source files
> into my VC++ 7.1 project without building static lib nor dynamic lib
> for I use for different projects multiple STL implementations which
> Crypto++ depends on. I had had no problem by doing that on Crypto++
> 5.1, but with "c5" from CVS I can't build the following code with plenty
> of link errors:
>
> #include "secblock.h"
> #include "aes.h"
> #include "modes.h"
>
> int _tmain(int argc, _TCHAR* argv[])
> {
> CryptoPP::CBC_Mode<CryptoPP::AES>::Encryption e;
>
> return 0;
> }
>
> Adding relevant source files such as
> rijndael.cpp / cryptolib.cpp / integer.cpp / rdtables.cpp / mode.cpp /
> misc.cpp and other 10 or more source files from "c5" can't reduce
> link errors to 0. Adding one file reduces some but includes many other
> link errors. File combination that works for Crypto++5.1 no longer works.
> In "c5"there's code for dll and change for that, did it get impossible
> to use it without building libraries? In Crypto++ 5.1 it is possible
> though you have to include fips140.cpp and other seemingly irrelevant
> files to your use because of dependency across source files.
>
> Ken
>
