Hi Aleksandr

After compiling crypto++ I just created two directories within the cryptopp
directory so I ended up with:
/cryptopp/cryptopp
/cryptopp/lib

I then copied the resulting .lib files (I'm using it on windows) into ./lib
and the header files into ./cryptopp. After that I set my include directory
to /cryptopp and simply used #include <cryptopp/....h> and set my lib
directory to cryptopp/lib...

This dealt with your first issue, and only took a minute or so...

Ian



|---------+--------------------------->
|         |           Aleksandr       |
|         |           Furmanov        |
|         |           <[EMAIL PROTECTED]|
|         |           comm.com>       |
|         |                           |
|         |           15/07/2003 09:59|
|         |           AM              |
|         |           Please respond  |
|         |           to cryptopp-list|
|         |                           |
|---------+--------------------------->
  
>---------------------------------------------------------------------------------------------------------------|
  |                                                                                    
                           |
  |        To:      [EMAIL PROTECTED]                                                  
                    |
  |        cc:                                                                         
                           |
  |        Subject: Crypto++ integration issues.                                       
                           |
  
>---------------------------------------------------------------------------------------------------------------|




Hi everyone,

I'm newbie to Crypto++ library. I recently adopted Crypto++ into a my
project and found following issues:

1. Crypto++ include style is:
             #include "crypto_lib_filename.h"
When library is used in large project consisting of big number of c/c++
files there is nonzero probability of header name conflict. IMO more
preferable style for library is:
    #include "CryptoPP/crypto_lib_filename.h"

2. While library itself is C++ one it uses old style #include for
standard C headers, for example:
// in secblock.h
// ....
#include <string.h>

It brings C functions in global namespace which is not desirable in
certain situations.
Modern C++ style is:
#include <cstring>

If it is recognized as a bug by Crypto++ developers,
-how I can submit it?
-or how I can fix it by myself?

-Aleksandr Furmanov.






 The information contained in this email is confidential.  If you are not
the intended recipient, you may not disclose or use the information in this
email in any way.  Protocom does not guarantee the integrity of any emails
                            or attached files.
_______________________________________________________________________________________



Reply via email to