Carew> Re my initial message, I am adding a NEW directory to the
Carew> crypto directory. I was hoping there was someone out there who
Carew> could give me some pointers on what to look for so I could add
Carew> new functionality to the project without compromising its
Carew> quality. If someone who has some experience in this doesn't
Carew> respond, then I will do my best to make it fit without doing
Carew> too much damage.
First of all, we don't use autoconf, at least yet. So, what you have
left to do is to create your directory and copy a Makefile.ssl from
one of the other directories under crypto/, as well as add a reference
to your subdirectory in crypto/Makefile.ssl.
There are a couple of other things too look out for. If you make up
new error messages the way it's usually done in OpenSSL, you will want
to add a line in crypto/err/openssl.ec (no, I don't know the format
well enough to describe it yet. It's making an association between
whatever header file you create and the C file with errors. Look in
openssl.ec and look at the files mentioned in there to figure it out.
If you're going to do ASN.1 stuff, you might want to look in
crypto/pem/ to see how it's erlated to crypto/asn1/.
I'm too tired to come up with other things to tell you. I encourage
you to give it a shot and show us what you did, and we may be able to
help you further.
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
