Re: [Gm-devel] complilation issues

[Jesse Lovelace]

Ok, I found out what was making the compile go APE SHIT when.  In our
config.h we:
#define const

for some reason CryptoPP goes **crazy** when this is defined.  I commited
some changes to cvs:

1st: renamed config.h.in to gm_config.h.in and also added #ifndef #define to
the file (so it would be a proper header file) and fixed configure.in to
generate correctly.

2nd: commented out the #define const thing

3rd:  added this to all the files that use the gm_config.h:
#ifdef HAVE_CONFIG_H
#include "gm_config.h"
#endif

so that the file wont be included on windows systems.

I think that's it, good luck on finals.

jesse


----- Original Message -----
From: "Jesse Lovelace" <address@hidden>
To: <address@hidden>
Sent: Tuesday, December 11, 2001 7:46 PM
Subject: [Gm-devel] complilation issues


Hi all,

It seems the the flags we are using to compile the lib (from the ./configure
script) really break when HAVE_CRYPTO is used in the "config.h" because
there is a "config.h" in the cryptopp dir.  I suggest we modify the make-ing
scheme so that the compiler does not include the -I../crypto flag because
then we have two config.h's in the path.  Any ideas here?


_______________________________________________
Gm-devel mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/gm-devel