Ben Laurie wrote:
>
> What are we going to do about them? They are currently slapped on the
> end of Makefile.ssl in the traditional way, but of course this causes a
> problem with CVS.
>
> Developing without them is a bugger, of course, so I don't consider that
> to be an option.
>
> Arrange things so Makefile is a copy of Makefile.ssl instead of a link,
> perhaps?
>
> Use includes?
>
OK lets see if this works...
As I mentioned before you can get nastier problems with error codes. If
you add one new error code and do a "make errors" you end up modifying
several files: you can ignore all of these except the .h file which is
part auto-generated part "real" source.
Hmm what you said gives me an idea. Have a static .org or whatever file
with a "stripped" version of the .h file and then have the .h file build
from the .org. The .h can then be ignored.
I've been looking at the error stuff anyway. Eric had been adding stuff
to allow proper external use of ASN1 stuff: it needs a bit of tweaking
because it doesn't quite work yet.
Steve.
--
Dr Stephen N. Henson. UK based freelance Cryptographic Consultant.
For info see homepage at http://www.drh-consultancy.demon.co.uk/
Email: [EMAIL PROTECTED]
NOTE NEW (13/12/98) PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
