Open SSL Developers -

Here's a list of things I needed to do to get the current 
versions of the OpenSSL sources to compile and link on 
Windows/NT.  I expect most of these will be dealt with by
the OpenSSL developers when they release a new tarball.
This stuff'll just bite you if you're too impatient to 
wait ... :)

TT

1) When I copy over or unzip from the cvs hierarchy, the 
   protections on the crypto/x509v3/old_v3 directory files 
   always prevent the copy.  It's safe to ignore this.  
   Nothing gets built in this directory anyway.

2) You need to create a date.h file by hand in the crypto
   directory.  If you're running a real shell, you can type
   the line from the makefile.ssl, e.g.:

   $ cd crypto
   $ echo "#define DATE \"`date`\"" >date.h

3) The version of perl I'm running doesn't like this bit of
   syntax in the top-level configure source:

    sub bad_target
        {
        print STDERR "Usage: Configure [-Dxxx] [-Lxxx] [-lxxx] os/compiler\n";
        print STDERR "pick os/compiler from:";
        my $j=0;
>>>>    foreach my $i (sort keys %table)   <<<<
                {
                print STDERR "\n" if ($j++ % 4) == 0;
                printf(STDERR "%-18s ",$i);
                }
        print STDERR "\n";
        }

    So here's how I get it to work:

    sub bad_target
        {
        print STDERR "Usage: Configure [-Dxxx] [-Lxxx] [-lxxx] os/compiler\n";
        print STDERR "pick os/compiler from:";
        my $j=0;
>>>>    my $i=0; <<<<
>>>>    foreach $i (sort keys %table) <<<<
                {
                print STDERR "\n" if ($j++ % 4) == 0;
                printf(STDERR "%-18s ",$i);
                }
        print STDERR "\n";
        }

   The version of perl I'm running is: 

   $ perl -version

   This is perl, version 5.002 with DEBUGGING EMBED

4) Now you can run perl to configure your system:

   $ perl configure VC-WIN32

5) Running configure converts the generic (.org) versions of files
   to local versions according to your configuration.  However there's
   one that gets forgotten--pem.org.  Fortunately, pem.org is the same
   as pem.h, so you just need to 

   $ cd to crypto/pem 
   $ cp pem.org pem.h

6) Ditto re: customizing .asm files.  If you're a real Windowz Stud
   and you've gone to the trouble to locate and install the assembler 
   (check out the MSDN Office Test Platform & Development Tools disk 
   #13), then you'll need to run the perl command to create the MSoft
   assembler input for the cast/asm/c-win32.asm file:

   $ cd crypto/cast/asm
   $ perl cast-586.pl win32 > c-win32.asm

7) Next you wanna create your ntdll.mak file:

   $ perl util/mk1mf.pl dll VC-WIN32 > ms/ntdll.mak
  
8) And your two .def files (there are lots of new source modules):

   $ perl util/mkdef.pl 32 ssleay > ms/ssleay32.def
   $ perl util/mkdef.pl 32 libeay > ms/libeay32.def

That's it, now you *should* be able to type

   $ nmake -f ms/ntdll.mak

And have everything build.

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to