Ulf Moeller <[EMAIL PROTECTED]> writes:
> On Thu, Jul 08, 1999, William M. Perry wrote:
>
> > > Perl is not just needed for running the configuration script; it is also
> > > needed for putting together some of the assembler files, changing
> > > defaults in various files (well, this counts as configuration, I guess),
> >
> > This is easily taken care of by making 'foo.bar.in' files that get sed'd
> > into `foo.bar' files with the correct paths in them.
>
> I'd be curious to see crypto/sha/asm/sha1-586.pl written in sed. Not!
Some things would still have to be done in perl, or you would have to
actually maintain a lot of separate asm/foo.s files, which isn't really
much fun.
> > > creating a single Makefile (for Windows builds)
> >
> > This will probably just have to be a standard NT makefile that is in the
> > tree instead of a mismash of the unix ones.
>
> If you can come up with a standard Makefile that works for VC++, Mingw32
> and Borland C, and is easily kept in sync with the Unix Makefiles, great.
> > The fact that OpenSSL modifies .h files and things like that _in_place_
>
> Show me one single .h file that is modified in place.
I was looking at the 0.9.2b release that is in our source tree. We haven't
synched up with the 0.9.3 release yet. It looks like most of the .h file
mucking about with has gone away.
But just for the record, lots and lots of them were modified in 0.9.2 :)
> The only in-place changes are the dependencies in the Makefiles if you
> remove a cipher (for example the Makefiles mustn't reference rsa.h if
> that file doesn't exist) and when new files are added.
Any reason the dependencies aren't auto-generated?
-bp
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
