mirror/openssl
2
0
Fork 0
mirror of https://github.com/openssl/openssl.git synced 2024-11-27 05:21:51 +08:00
Code Issues Packages Projects Releases Wiki Activity
81bd0446a9
openssl/Makefile.org

602 lines
21 KiB
Makefile
Raw Normal View History

Remove obsolete references to SSLeay and change default PLATFORM from "FreeBSD" to the generic "dist" as it's done implicitly by "make dist".
1999-03-22 22:45:08 +08:00
##
## Makefile for OpenSSL
##
Linux shared libraries.
1999-04-29 00:16:31 +08:00
VERSION=
MAJOR=
MINOR=
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
SHLIB_VERSION_NUMBER=
SHLIB_VERSION_HISTORY=
SHLIB_MAJOR=
SHLIB_MINOR=
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
SHLIB_EXT=
Remove obsolete references to SSLeay and change default PLATFORM from "FreeBSD" to the generic "dist" as it's done implicitly by "make dist".
1999-03-22 22:45:08 +08:00
PLATFORM=dist
mk1mf.pl and mkdef.pl read OPTIONS from toplevel Makefile. Configure no longer changes files in place.
1999-05-13 18:28:14 +08:00
OPTIONS=
Allow reconfiguration. This can be useful if some source update requires that you configure again, but you don't want to reenter all those configuration arguments again.
2000-08-17 18:23:45 +08:00
CONFIGURE_ARGS=
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
SHLIB_TARGET=
Update the make system for installations: - define a HERE variable to indicate where the source tree is (used very little right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
2002-12-15 13:59:13 +08:00
# HERE indicates where this Makefile lives. This can be used to indicate
# where sub-Makefiles are expected to be. Currently has very limited usage,
# and should probably not be bothered with at all.
HERE=.
Support INSTALL_PREFIX for packagers. Submitted by: Reviewed by: PR:
1999-04-30 05:52:08 +08:00
# INSTALL_PREFIX is for package builders so that they can configure
# for, say, /usr/ and yet have everything installed to /tmp/somedir/usr/.
# Normally it is left empty.
INSTALL_PREFIX=
New Configure option --openssldir to replace util/ssldir.pl.
1999-04-25 06:59:36 +08:00
INSTALLTOP=/usr/local/ssl
# Do not edit this manually. Use Configure --openssldir=DIR do change this!
OPENSSLDIR=/usr/local/ssl
Remove obsolete references to SSLeay and change default PLATFORM from "FreeBSD" to the generic "dist" as it's done implicitly by "make dist".
1999-03-22 22:45:08 +08:00
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# NO_IDEA - Define to build without the IDEA algorithm
# NO_RC4 - Define to build without the RC4 algorithm
# NO_RC2 - Define to build without the RC2 algorithm
# THREADS - Define when building with threads, you will probably also need any
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
# system defines as well, i.e. _REENTERANT for Solaris 2.[34]
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# TERMIO - Define the termio terminal subsystem, needed if sgtty is missing.
# TERMIOS - Define the termios terminal subsystem, Silicon Graphics.
# LONGCRYPT - Define to use HPUX 10.x's long password modification to crypt(3).
# DEVRANDOM - Give this the value of the 'random device' if your OS supports
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
# one. 32 bytes will be read from this when the random
# number generator is initalised.
SSL_ALLOW_ENULL was renamed to SSL_FORBID_ENULL some time ago by Ben.
1999-04-13 19:01:44 +08:00
# SSL_FORBID_ENULL - define if you want the server to be not able to use the
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
# NULL encryption ciphers.
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
#
# LOCK_DEBUG - turns on lots of lock debug output :-)
# REF_CHECK - turn on some xyz_free() assertions.
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
# REF_PRINT - prints some stuff on structure free.
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# CRYPTO_MDEBUG - turns on my 'memory leak' detecting stuff
# MFUNC - Make all Malloc/Free/Realloc calls call
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
# CRYPTO_malloc/CRYPTO_free/CRYPTO_realloc which can be setup to
# call application defined callbacks via CRYPTO_set_mem_functions()
# MD5_ASM needs to be defined to use the x86 assembler for MD5
# SHA1_ASM needs to be defined to use the x86 assembler for SHA1
# RMD160_ASM needs to be defined to use the x86 assembler for RIPEMD160
Import of old SSLeay release: SSLeay 0.9.1b (unreleased)
1998-12-21 19:00:56 +08:00
# Do not define B_ENDIAN or L_ENDIAN if 'unsigned long' == 8. It must
# equal 4.
# PKCS1_CHECK - pkcs1 tests.
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Deal with generated files.
1998-12-29 05:58:19 +08:00
CC= gcc
Import of old SSLeay release: SSLeay 0.9.1b (unreleased)
1998-12-21 19:00:56 +08:00
#CFLAG= -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -m486 -Wall -Wuninitialized -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
Deal with generated files.
1998-12-29 05:58:19 +08:00
CFLAG= -DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486 -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
New Configure option no-<cipher> (rsa, idea, rc5, ...).
1999-04-27 09:14:46 +08:00
DEPFLAG=
We really have no need for PEX_LIBS, so empty it.
2001-03-23 05:20:54 +08:00
PEX_LIBS=
Various cleanups and fixed by Marc and Ralf to start the OpenTLS project
1998-12-22 23:04:48 +08:00
EX_LIBS=
Incorporate some changes that make OpenSSL compilable in CygWin.
2001-04-04 23:50:30 +08:00
EXE_EXT=
Add aix64-cc, and make sure that ar gets proper flags for 64-bit libraries
2002-08-02 04:28:16 +08:00
ARFLAGS=
AR=ar $(ARFLAGS) r
New Makefile variables $(RANLIB) and $(PERL).
1999-04-01 20:34:33 +08:00
RANLIB= ranlib
PERL= perl
Make it possible to have differing tar versions.
2000-02-24 09:59:55 +08:00
TAR= tar
I'm using GNU tar...
2000-09-21 15:15:52 +08:00
TARFLAGS= --no-recursion
Make all configuration macros available for application by making sure they are available in opensslconf.h, by giving them names starting with "OPENSSL_" to avoid conflicts with other packages and by making sure e_os2.h will cover all platform-specific cases together with opensslconf.h. I've checked fairly well that nothing breaks with this (apart from external software that will adapt if they have used something like NO_KRB5), but I can't guarantee it completely, so a review of this change would be a good thing.
2001-02-20 00:06:34 +08:00
MAKEDEPPROG=makedepend
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Unified targets for ELF assembler modules. Tested on Linux, Solaris and FreeBSD. Goal is to extend support even to SCO5, UnixWare/OpenUnix...
2003-01-04 01:37:53 +08:00
# We let the C compiler driver to take care of .s files. This is done in
# order to be excused from maintaining a separate set of architecture
# dependent assembler flags. E.g. if you throw -mcpu=ultrasparc at SPARC
# gcc, then the driver will automatically translate it to -xarch=v8plus
# and pass it down to assembler.
AS=$(CC) -c
ASFLAGS=$(CFLAG)
Import of old SSLeay release: SSLeay 0.9.1b (unreleased)
1998-12-21 19:00:56 +08:00
# Set BN_ASM to bn_asm.o if you want to use the C version
BN_ASM= bn_asm.o
#BN_ASM= bn_asm.o
#BN_ASM= asm/bn86-elf.o # elf, linux-elf
#BN_ASM= asm/bn86-sol.o # solaris
#BN_ASM= asm/bn86-out.o # a.out, FreeBSD
#BN_ASM= asm/bn86bsdi.o # bsdi
#BN_ASM= asm/alpha.o # DEC Alpha
#BN_ASM= asm/pa-risc2.o # HP-UX PA-RISC
#BN_ASM= asm/r3000.o # SGI MIPS cpu
#BN_ASM= asm/sparc.o # Sun solaris/SunOS
#BN_ASM= asm/bn-win32.o # Windows 95/NT
#BN_ASM= asm/x86w16.o # 16 bit code for Windows 3.1/DOS
#BN_ASM= asm/x86w32.o # 32 bit code for Windows 3.1
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
New option to generate 80386 code.
1999-03-31 20:38:27 +08:00
# For x86 assembler: Set PROCESSOR to 386 if you want to support
# the 80386.
PROCESSOR=
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# Set DES_ENC to des_enc.o if you want to use the C version
#There are 4 x86 assember options.
Deal with generated files.
1998-12-29 05:58:19 +08:00
DES_ENC= asm/dx86-out.o asm/yx86-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#DES_ENC= des_enc.o fcrypt_b.o # C
#DES_ENC= asm/dx86-elf.o asm/yx86-elf.o # elf
#DES_ENC= asm/dx86-sol.o asm/yx86-sol.o # solaris
#DES_ENC= asm/dx86-out.o asm/yx86-out.o # a.out, FreeBSD
#DES_ENC= asm/dx86bsdi.o asm/yx86bsdi.o # bsdi
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# Set BF_ENC to bf_enc.o if you want to use the C version
#There are 4 x86 assember options.
Deal with generated files.
1998-12-29 05:58:19 +08:00
BF_ENC= asm/bx86-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#BF_ENC= bf_enc.o
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
#BF_ENC= asm/bx86-elf.o # elf
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#BF_ENC= asm/bx86-sol.o # solaris
#BF_ENC= asm/bx86-out.o # a.out, FreeBSD
#BF_ENC= asm/bx86bsdi.o # bsdi
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
# Set CAST_ENC to c_enc.o if you want to use the C version
#There are 4 x86 assember options.
Deal with generated files.
1998-12-29 05:58:19 +08:00
CAST_ENC= asm/cx86-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#CAST_ENC= c_enc.o
#CAST_ENC= asm/cx86-elf.o # elf
#CAST_ENC= asm/cx86-sol.o # solaris
#CAST_ENC= asm/cx86-out.o # a.out, FreeBSD
#CAST_ENC= asm/cx86bsdi.o # bsdi
# Set RC4_ENC to rc4_enc.o if you want to use the C version
#There are 4 x86 assember options.
Deal with generated files.
1998-12-29 05:58:19 +08:00
RC4_ENC= asm/rx86-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#RC4_ENC= rc4_enc.o
#RC4_ENC= asm/rx86-elf.o # elf
#RC4_ENC= asm/rx86-sol.o # solaris
#RC4_ENC= asm/rx86-out.o # a.out, FreeBSD
#RC4_ENC= asm/rx86bsdi.o # bsdi
# Set RC5_ENC to rc5_enc.o if you want to use the C version
#There are 4 x86 assember options.
Deal with generated files.
1998-12-29 05:58:19 +08:00
RC5_ENC= asm/r586-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#RC5_ENC= rc5_enc.o
#RC5_ENC= asm/r586-elf.o # elf
#RC5_ENC= asm/r586-sol.o # solaris
#RC5_ENC= asm/r586-out.o # a.out, FreeBSD
#RC5_ENC= asm/r586bsdi.o # bsdi
# Also need MD5_ASM defined
Deal with generated files.
1998-12-29 05:58:19 +08:00
MD5_ASM_OBJ= asm/mx86-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#MD5_ASM_OBJ= asm/mx86-elf.o # elf
#MD5_ASM_OBJ= asm/mx86-sol.o # solaris
#MD5_ASM_OBJ= asm/mx86-out.o # a.out, FreeBSD
#MD5_ASM_OBJ= asm/mx86bsdi.o # bsdi
# Also need SHA1_ASM defined
Deal with generated files.
1998-12-29 05:58:19 +08:00
SHA1_ASM_OBJ= asm/sx86-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#SHA1_ASM_OBJ= asm/sx86-elf.o # elf
#SHA1_ASM_OBJ= asm/sx86-sol.o # solaris
#SHA1_ASM_OBJ= asm/sx86-out.o # a.out, FreeBSD
#SHA1_ASM_OBJ= asm/sx86bsdi.o # bsdi
# Also need RMD160_ASM defined
Deal with generated files.
1998-12-29 05:58:19 +08:00
RMD160_ASM_OBJ= asm/rm86-out.o
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
#RMD160_ASM_OBJ= asm/rm86-elf.o # elf
#RMD160_ASM_OBJ= asm/rm86-sol.o # solaris
#RMD160_ASM_OBJ= asm/rm86-out.o # a.out, FreeBSD
#RMD160_ASM_OBJ= asm/rm86bsdi.o # bsdi
First tentative impementation of Kerberos 5 cryptos and keys for SSL/TLS. Implemented by Vern Staats <staatsvr@asc.hpc.mil>, further hacked and distributed by Jeffrey Altman <jaltnab@columbia.edu>
2000-12-01 06:53:34 +08:00
# KRB5 stuff
KRB5_INCLUDES=
Handle krb5 libraries separately and make sure only libssl.so depends on it.
2003-02-14 21:12:00 +08:00
LIBKRB5=
First tentative impementation of Kerberos 5 cryptos and keys for SSL/TLS. Implemented by Vern Staats <staatsvr@asc.hpc.mil>, further hacked and distributed by Jeffrey Altman <jaltnab@columbia.edu>
2000-12-01 06:53:34 +08:00
Step 12 of move of engines: Time to make the changes to support automatic load of dynamic engines. Make the changes in the main Makefile so the engines are built, but now in the engines/ directory. Note: The changes in step 12 have all been made by Geoff Thorpe. Credit where credit is due.
2002-10-12 02:51:29 +08:00
DIRS= crypto ssl engines apps test tools
Linux shared libraries.
1999-04-29 00:16:31 +08:00
SHLIBDIRS= crypto ssl
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# dirs in crypto to build
SDIRS= \
MD4 implemented. Assar Westerlund provided the digest code itself and the test utility, I added the bits to get a EVP interface, the command line utility and the speed test
2000-08-14 22:05:53 +08:00
md2 md4 md5 sha mdc2 hmac ripemd \
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
des rc2 rc4 rc5 idea bf cast \
Add ECDH support. Additional changes: - use EC_GROUP_get_degree() in apps/req.c - add ECDSA and ECDH to apps/speed.c - adds support for EC curves over binary fields to ECDSA - new function EC_KEY_up_ref() in crypto/ec/ec_key.c - reorganize crypto/ecdsa/ecdsatest.c - add engine support for ECDH - fix a few bugs in ECDSA engine support Submitted by: Douglas Stebila <douglas.stebila@sun.com>
2002-08-09 16:43:04 +08:00
bn ec rsa dsa ecdsa dh ecdh dso engine aes \
More X509 V3 stuff. Add support for extensions in the 'req' application so that: openssl req -x509 -new -out cert.pem will take extensions from openssl.cnf a sample for a CA is included. Also change the directory order so pem is nearer the end. Otherwise 'make links' wont work because pem.h can't be built.
1999-01-25 09:09:21 +08:00
buffer bio stack lhash rand err objects \
Patches from Vern Staats <staatsvr@asc.hpc.mil> to get Kerberos 5 in SSL according to RFC 2712. His comment is: This is a patch to openssl-SNAP-20010702 to support Kerberized SSL authentication. I'm expecting to have the full kssl-0.5 kit up on sourceforge by the end of the week. The full kit includes patches for mod-ssl, apache, and a few text clients. The sourceforge URL is http://sourceforge.net/projects/kssl/ . Thanks to a note from Simon Wilkinson I've replaced my KRB5 AP_REQ message with a real KerberosWrapper struct. I think this is fully RFC 2712 compliant now, including support for the optional authenticator field. I also added openssl-style ASN.1 macros for a few Kerberos structs; see crypto/krb5/ if you're interested.
2001-07-10 05:46:58 +08:00
evp asn1 pem x509 x509v3 conf txt_db pkcs7 pkcs12 comp ocsp ui krb5
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
For a long time, I've wanted to be able to easily run one or a few individual tests. I finally got myself to implement it...
2000-11-13 04:24:30 +08:00
# tests to perform. "alltests" is a special word indicating that all tests
# should be performed.
TESTS = alltests
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
MAKEFILE= Makefile.ssl
Move the shared library construction stuff to Makefile.shared, a helper makefile that generalises our way of building shared libraries and is designed to take care of almost anything (I hope).
2002-10-11 08:37:11 +08:00
NEWMAKE= make
MAKE= $(NEWMAKE) -f Makefile.ssl
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Install manpages below OPENSSLDIR (I think it was meant to be this way?). New variable for man directory.
2000-02-16 02:34:46 +08:00
MANDIR=$(OPENSSLDIR)/man
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
MAN1=1
MAN3=3
SHELL=/bin/sh
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
TOP= .
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
ONEDIRS=out tmp
VMS support. Submitted by: Richard Levitte <richard@levitte.org>
1999-05-13 19:37:32 +08:00
EDIRS= times doc bugs util include certs ms shlib mt demos perl sf dep VMS
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
WDIRS= windows
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
LIBS= libcrypto.a libssl.a
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
SHARED_CRYPTO=libcrypto$(SHLIB_EXT)
SHARED_SSL=libssl$(SHLIB_EXT)
SHARED_LIBS=
SHARED_LIBS_LINK_EXTS=
On Solaris64, cc needs the flag -xarch=v9 when linking shared libraries. Make a general change to support shared library linking flags in general. Noted by Nick Briggs <briggs@parc.xerox.com>
2002-01-02 18:30:07 +08:00
SHARED_LDFLAGS=
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
GENERAL= Makefile
*** empty log message ***
1998-12-23 15:58:53 +08:00
BASENAME= openssl
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
NAME= $(BASENAME)-$(VERSION)
TARFILE= $(NAME).tar
WTARFILE= $(NAME)-win.tar
Make all configuration macros available for application by making sure they are available in opensslconf.h, by giving them names starting with "OPENSSL_" to avoid conflicts with other packages and by making sure e_os2.h will cover all platform-specific cases together with opensslconf.h. I've checked fairly well that nothing breaks with this (apart from external software that will adapt if they have used something like NO_KRB5), but I can't guarantee it completely, so a review of this change would be a good thing.
2001-02-20 00:06:34 +08:00
EXHEADER= e_os2.h
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
HEADER= e_os.h
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Generate openssl.pc so pkg-config can return proper data. PR: 163
2002-11-07 07:35:00 +08:00
all: Makefile.ssl build_all openssl.pc
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Change the main Makefile to have "mini-build" targets. PR: 253, last part.
2002-10-09 22:52:01 +08:00
BUILD_CMD=if echo " $(DIRS) " | grep " $$i " >/dev/null 2>/dev/null; then \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making all in $$i..." && \
Unified targets for ELF assembler modules. Tested on Linux, Solaris and FreeBSD. Goal is to extend support even to SCO5, UnixWare/OpenUnix...
2003-01-04 01:37:53 +08:00
$(MAKE) CC='${CC}' PLATFORM='${PLATFORM}' CFLAG='${CFLAG}' AS='${AS}' ASFLAGS='${ASFLAGS}' SDIRS='$(SDIRS)' INSTALLTOP='${INSTALLTOP}' PEX_LIBS='${PEX_LIBS}' EX_LIBS='${EX_LIBS}' BN_ASM='${BN_ASM}' DES_ENC='${DES_ENC}' BF_ENC='${BF_ENC}' CAST_ENC='${CAST_ENC}' RC4_ENC='${RC4_ENC}' RC5_ENC='${RC5_ENC}' SHA1_ASM_OBJ='${SHA1_ASM_OBJ}' MD5_ASM_OBJ='${MD5_ASM_OBJ}' RMD160_ASM_OBJ='${RMD160_ASM_OBJ}' AR='${AR}' PROCESSOR='${PROCESSOR}' PERL='${PERL}' RANLIB='${RANLIB}' KRB5_INCLUDES='${KRB5_INCLUDES}' LIBKRB5='${LIBKRB5}' EXE_EXT='${EXE_EXT}' SHARED_LIBS='${SHARED_LIBS}' SHLIB_EXT='${SHLIB_EXT}' SHLIB_TARGET='${SHLIB_TARGET}' all ) || exit 1; \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
else \
$(MAKE) $$i; \
Change the main Makefile to have "mini-build" targets. PR: 253, last part.
2002-10-09 22:52:01 +08:00
fi; fi
Keep the sub_all symbol so all the algorithm Makefiles won't break.
2002-10-09 23:03:21 +08:00
sub_all: build_all
Change the main Makefile to have "mini-build" targets. PR: 253, last part.
2002-10-09 22:52:01 +08:00
build_all: build_libs build_apps build_tests build_tools
Step 12 of move of engines: Time to make the changes to support automatic load of dynamic engines. Make the changes in the main Makefile so the engines are built, but now in the engines/ directory. Note: The changes in step 12 have all been made by Geoff Thorpe. Credit where credit is due.
2002-10-12 02:51:29 +08:00
build_libs: build_crypto build_ssl build_engines
Change the main Makefile to have "mini-build" targets. PR: 253, last part.
2002-10-09 22:52:01 +08:00
build_crypto:
@i=crypto; $(BUILD_CMD)
build_ssl:
@i=ssl; $(BUILD_CMD)
Step 12 of move of engines: Time to make the changes to support automatic load of dynamic engines. Make the changes in the main Makefile so the engines are built, but now in the engines/ directory. Note: The changes in step 12 have all been made by Geoff Thorpe. Credit where credit is due.
2002-10-12 02:51:29 +08:00
build_engines:
@i=engines; $(BUILD_CMD)
Change the main Makefile to have "mini-build" targets. PR: 253, last part.
2002-10-09 22:52:01 +08:00
build_apps:
@i=apps; $(BUILD_CMD)
build_tests:
@i=test; $(BUILD_CMD)
build_tools:
@i=tools; $(BUILD_CMD)
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
libcrypto$(SHLIB_EXT): libcrypto.a
Avoid loops, and make sure that it's possible to still build shared libraries even if the "shared" configuration option wasn't chosen.
2000-07-25 04:36:46 +08:00
@if [ "$(SHLIB_TARGET)" != "" ]; then \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
$(MAKE) SHLIBDIRS=crypto build-shared; \
Avoid loops, and make sure that it's possible to still build shared libraries even if the "shared" configuration option wasn't chosen.
2000-07-25 04:36:46 +08:00
else \
echo "There's no support for shared libraries on this platform" >&2; \
fi
Superflous '\' messes up with HP-UX make.
2002-01-29 00:30:06 +08:00
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
libssl$(SHLIB_EXT): libcrypto$(SHLIB_EXT) libssl.a
Avoid loops, and make sure that it's possible to still build shared libraries even if the "shared" configuration option wasn't chosen.
2000-07-25 04:36:46 +08:00
@if [ "$(SHLIB_TARGET)" != "" ]; then \
Minimise the amount of -L. when linking the shared libraries. It seems like some Unixen (SCO) have opinions about too many -L.
2001-03-16 06:10:07 +08:00
$(MAKE) SHLIBDIRS=ssl SHLIBDEPS='-lcrypto' build-shared; \
Avoid loops, and make sure that it's possible to still build shared libraries even if the "shared" configuration option wasn't chosen.
2000-07-25 04:36:46 +08:00
else \
echo "There's no support for shared libraries on this platform" >&2; \
fi
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
clean-shared:
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
@for i in $(SHLIBDIRS); do \
if [ -n "$(SHARED_LIBS_LINK_EXTS)" ]; then \
tmp="$(SHARED_LIBS_LINK_EXTS)"; \
for j in $${tmp:-x}; do \
( set -x; rm -f lib$$i$$j ); \
done; \
fi; \
( set -x; rm -f lib$$i$(SHLIB_EXT) ); \
At Corinna Vinschen's request, change CygWin32 to Cygwin
2002-02-14 20:28:24 +08:00
if [ "$(PLATFORM)" = "Cygwin" ]; then \
Update the configuration of CygWin32 to use the new capabilities of CygWin 1.3.x, which includes thread and shared library support. Submitted by Corinna Vinschen <vinschen@redhat.com> and modified a little bit.
2002-02-13 22:44:33 +08:00
( set -x; rm -f cyg$$i$(SHLIB_EXT) lib$$i$(SHLIB_EXT).a ); \
fi; \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
done
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
link-shared:
Move the shared library construction stuff to Makefile.shared, a helper makefile that generalises our way of building shared libraries and is designed to take care of almost anything (I hope).
2002-10-11 08:37:11 +08:00
@ for i in ${SHLIBDIRS}; do \
Update the make system for installations: - define a HERE variable to indicate where the source tree is (used very little right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
2002-12-15 13:59:13 +08:00
$(NEWMAKE) -f $(HERE)/Makefile.shared \
Move the shared library construction stuff to Makefile.shared, a helper makefile that generalises our way of building shared libraries and is designed to take care of almost anything (I hope).
2002-10-11 08:37:11 +08:00
LIBNAME=$$i LIBVERSION=${SHLIB_MAJOR}.${SHLIB_MINOR} \
LIBCOMPATVERSIONS=";${SHLIB_VERSION_HISTORY}" \
symlink.$(SHLIB_TARGET); \
For systems where gcc is used and where we don't know if GNU ld is used or not, let's ask collect2 which ld it uses and choose to use the target do-gnu_shared if GNU ld is used. This solves the reported problems on Solaris systems where GNU cc is used but GNU ld isn't, and probably on other systems with similar setups.
2001-10-10 22:46:41 +08:00
libs="$$libs -l$$i"; \
Add what's needed to get shared libraries on HP-UX. N.B.: This has not been tested at all, that's my next step.
2000-10-22 05:24:11 +08:00
done
Move the shared library construction stuff to Makefile.shared, a helper makefile that generalises our way of building shared libraries and is designed to take care of almost anything (I hope).
2002-10-11 08:37:11 +08:00
build-shared: do_$(SHLIB_TARGET) link-shared
do_$(SHLIB_TARGET):
@ libs='-L. ${SHLIBDEPS}'; for i in ${SHLIBDIRS}; do \
Handle krb5 libraries separately and make sure only libssl.so depends on it.
2003-02-14 21:12:00 +08:00
if [ "${SHLIBDIRS}" = "ssl" -a -n "$(LIBKRB5)" ]; then \
libs="$(LIBKRB5) $$libs"; \
fi; \
Move the shared library construction stuff to Makefile.shared, a helper makefile that generalises our way of building shared libraries and is designed to take care of almost anything (I hope).
2002-10-11 08:37:11 +08:00
$(NEWMAKE) -f Makefile.shared \
CC="$(CC)" LDFLAGS="$(LDFLAGS)" \
SHARED_LDFLAGS="$(SHARED_LDFLAGS)" \
LIBNAME=$$i LIBVERSION=${SHLIB_MAJOR}.${SHLIB_MINOR} \
LIBCOMPATVERSIONS=";${SHLIB_VERSION_HISTORY}" \
LIBDEPS="$$libs $(EX_LIBS)" \
Add full support for -rpath/-R, both in shared libraries and applications, at least on the platforms where it's known how to do it. Note: this has only been tested on GNU-based platforms (Linux), and needs to be tested on all others. Additionally, it's not yet supported on the following platforms, for lack of information: Darwin (MacOS X) Cygwin OSF1/Alpha SVR3 ReliantUNIX Please help out with testing and the platforms we don't yet know well enough.
2003-02-14 07:52:54 +08:00
LIBRPATH="$(INSTALLTOP)/lib" \
Move the shared library construction stuff to Makefile.shared, a helper makefile that generalises our way of building shared libraries and is designed to take care of almost anything (I hope).
2002-10-11 08:37:11 +08:00
link_a.$(SHLIB_TARGET); \
Handle krb5 libraries separately and make sure only libssl.so depends on it.
2003-02-14 21:12:00 +08:00
libs="-l$$i $$libs"; \
Add old patch from Robert Dahlem <Robert.Dahlem@ffm2.siemens.de> to make it possible to produce shared libraries on ReliantUNIX.
2002-01-26 11:17:27 +08:00
done
Because the contents of openssl.pc may have to change when a configuration has been performed (and possibly changed), have it depend on Makefile.ssl.
2002-12-20 05:56:40 +08:00
openssl.pc: Makefile.ssl
Generate openssl.pc so pkg-config can return proper data. PR: 163
2002-11-07 07:35:00 +08:00
@ ( echo 'prefix=$(INSTALLTOP)'; \
echo 'exec_prefix=$${prefix}'; \
echo 'libdir=$${exec_prefix}/lib'; \
echo 'includedir=$${prefix}/include'; \
echo ''; \
echo 'Name: OpenSSL'; \
echo 'Description: Secure Sockets Layer and cryptography libraries and tools'; \
echo 'Version: '$(VERSION); \
echo 'Requires: '; \
echo 'Libs: -L$${libdir} -lssl -lcrypto $(EX_LIBS)'; \
Since we're including Kerberos 5 headers in our exported header files (when OpenSSL is configured to use Kerberos), we'd better tell pkg-config users where they can be found. PR: 421
2002-12-30 07:03:12 +08:00
echo 'Cflags: -I$${includedir} $(KRB5_INCLUDES)' ) > openssl.pc
Generate openssl.pc so pkg-config can return proper data. PR: 163
2002-11-07 07:35:00 +08:00
Make sure people know when they need to rebuild the Makefile.
1999-01-25 02:15:00 +08:00
Makefile.ssl: Makefile.org
Print a little bit more information
1999-03-22 22:38:33 +08:00
@echo "Makefile.ssl is older than Makefile.org."
Make the perl module compile and eliminate some of the warnings. Still doesn't work (the destructor on BIO and SSL is called immediately after creating the object. Why that??)
1999-07-23 00:10:31 +08:00
@echo "Reconfigure the source tree (via './config' or 'perl Configure'), please."
Make sure people know when they need to rebuild the Makefile.
1999-01-25 02:15:00 +08:00
@false
Import of old SSLeay release: SSLeay 0.9.1b (unreleased)
1998-12-21 19:00:56 +08:00
libclean:
Remove duplication and have clean depend on libclean
2003-02-22 23:04:03 +08:00
rm -f *.map *.so *.so.* engines/*.so *.a */lib */*/lib
Import of old SSLeay release: SSLeay 0.9.1b (unreleased)
1998-12-21 19:00:56 +08:00
Remove duplication and have clean depend on libclean
2003-02-22 23:04:03 +08:00
clean: libclean
rm -f shlib/*.o *.o core a.out fluff rehash.time testlog make.log cctest cctest.c
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
@for i in $(DIRS) ;\
do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making clean in $$i..." && \
$(MAKE) SDIRS='${SDIRS}' clean ) || exit 1; \
rm -f $(LIBS); \
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
Generate openssl.pc so pkg-config can return proper data. PR: 163
2002-11-07 07:35:00 +08:00
rm -f openssl.pc
Remove duplication and have clean depend on libclean
2003-02-22 23:04:03 +08:00
rm -f speed.* .pure
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
rm -f $(TARFILE)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
@for i in $(ONEDIRS) ;\
do \
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
rm -fr $$i/*; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done
makefile.one: files
New Makefile variables $(RANLIB) and $(PERL).
1999-04-01 20:34:33 +08:00
$(PERL) util/mk1mf.pl >makefile.one; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
sh util/do_ms.sh
Bad dependencies.
1999-04-08 23:19:36 +08:00
files:
New Makefile variables $(RANLIB) and $(PERL).
1999-04-01 20:34:33 +08:00
$(PERL) $(TOP)/util/files.pl Makefile.ssl > $(TOP)/MINFO
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
@for i in $(DIRS) ;\
do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making 'files' in $$i..." && \
$(MAKE) SDIRS='${SDIRS}' PERL='${PERL}' files ) || exit 1; \
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
links:
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
@$(TOP)/util/point.sh Makefile.ssl Makefile
mkdir -p is not fully portable (according to Marc Crispin, NeXTstep creates a directory called -p); now mkdir-p.pl does its job.
1999-06-07 21:33:50 +08:00
@$(PERL) $(TOP)/util/mkdir-p.pl include/openssl
e_os.h does not belong with the exported headers. Do not put it there and make all files the depend on it include it without prefixing it with openssl/. This means that all Makefiles will have $(TOP) as one of the include directories.
2001-02-22 22:45:02 +08:00
@$(PERL) $(TOP)/util/mklink.pl include/openssl $(EXHEADER)
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
@for i in $(DIRS); do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making links in $$i..." && \
First tentative impementation of Kerberos 5 cryptos and keys for SSL/TLS. Implemented by Vern Staats <staatsvr@asc.hpc.mil>, further hacked and distributed by Jeffrey Altman <jaltnab@columbia.edu>
2000-12-01 06:53:34 +08:00
$(MAKE) CC='${CC}' PLATFORM='${PLATFORM}' CFLAG='${CFLAG}' SDIRS='$(SDIRS)' INSTALLTOP='${INSTALLTOP}' PEX_LIBS='${PEX_LIBS}' EX_LIBS='${EX_LIBS}' BN_ASM='${BN_ASM}' DES_ENC='${DES_ENC}' BF_ENC='${BF_ENC}' CAST_ENC='${CAST_ENC}' RC4_ENC='${RC4_ENC}' RC5_ENC='${RC5_ENC}' SHA1_ASM_OBJ='${SHA1_ASM_OBJ}' MD5_ASM_OBJ='${MD5_ASM_OBJ}' RMD160_ASM_OBJ='${RMD160_ASM_OBJ}' AR='${AR}' PERL='${PERL}' KRB5_INCLUDES='${KRB5_INCLUDES}' LIBKRB5='${LIBKRB5}' links ) || exit 1; \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
Make dummy tests to make it easier to physically remove unwanted algorithms. This should complete PR 75
2002-07-23 21:31:04 +08:00
gentests:
@(cd test && echo "generating dummy tests (if needed)..." && \
$(MAKE) CC='${CC}' PLATFORM='${PLATFORM}' CFLAG='${CFLAG}' SDIRS='$(SDIRS)' INSTALLTOP='${INSTALLTOP}' PEX_LIBS='${PEX_LIBS}' EX_LIBS='${EX_LIBS}' BN_ASM='${BN_ASM}' DES_ENC='${DES_ENC}' BF_ENC='${BF_ENC}' CAST_ENC='${CAST_ENC}' RC4_ENC='${RC4_ENC}' RC5_ENC='${RC5_ENC}' SHA1_ASM_OBJ='${SHA1_ASM_OBJ}' MD5_ASM_OBJ='${MD5_ASM_OBJ}' RMD160_ASM_OBJ='${RMD160_ASM_OBJ}' AR='${AR}' PROCESSOR='${PROCESSOR}' PERL='${PERL}' RANLIB='${RANLIB}' TESTS='${TESTS}' KRB5_INCLUDES='${KRB5_INCLUDES}' LIBKRB5='${LIBKRB5}' EXE_EXT='${EXE_EXT}' SHARED_LIBS='${SHARED_LIBS}' SHLIB_EXT='${SHLIB_EXT}' SHLIB_TARGET='${SHLIB_TARGET}' TESTS='${TESTS}' OPENSSL_DEBUG_MEMORY=on generate );
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
dclean:
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
rm -f *.bak
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
@for i in $(DIRS) ;\
do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making dclean in $$i..." && \
$(MAKE) SDIRS='${SDIRS}' PERL='${PERL}' dclean ) || exit 1; \
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
Implement MD5-based "apr1" password hash.
2000-02-12 00:25:44 +08:00
rehash: rehash.time
rehash.time: certs
Correct a few typos that I introduced after applying DJGPP patches.
2002-12-05 03:13:43 +08:00
@(OPENSSL="`pwd`/apps/openssl"; OPENSSL_DEBUG_MEMORY=on; \
Change the shared library support so the shared libraries get built sooner and the programs get built against the shared libraries. This requires a bit more work. Things like -rpath and the possibility to still link the programs statically should be included. Some cleanup is also needed. This will be worked on.
2001-10-30 16:00:59 +08:00
export OPENSSL OPENSSL_DEBUG_MEMORY; \
Make sure that all the library paths are modified in prepend mode, not replace mode. PR: 528
2003-03-20 19:37:47 +08:00
LD_LIBRARY_PATH="`pwd`:$$LD_LIBRARY_PATH"; \
DYLD_LIBRARY_PATH="`pwd`:$$DYLD_LIBRARY_PATH"; \
SHLIB_PATH="`pwd`:$$SHLIB_PATH"; \
LIBPATH="`pwd`:$$LIBPATH"; \
DJGPP doesn't have DLLs, so skip adding to %PATH% in that environment. PR: 453
2003-01-13 23:16:40 +08:00
if [ "$(PLATFORM)" = "Cygwin" ]; then PATH="`pwd`:$$PATH"; fi; \
Changes to make shared library building and use work better with Cygwin
2002-11-16 00:48:38 +08:00
export LD_LIBRARY_PATH DYLD_LIBRARY_PATH SHLIB_PATH LIBPATH PATH; \
Change the shared library support so the shared libraries get built sooner and the programs get built against the shared libraries. This requires a bit more work. Things like -rpath and the possibility to still link the programs statically should be included. Some cleanup is also needed. This will be worked on.
2001-10-30 16:00:59 +08:00
$(PERL) tools/c_rehash certs)
Corrections.
2000-02-12 01:18:50 +08:00
touch rehash.time
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
test: tests
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Do make rehash automatically at make test.
1999-04-29 00:14:39 +08:00
tests: rehash
General source tree makefile cleanups: Made `making xxx in yyy...' display consistent in the source tree and replaced `/bin/rm' by `rm'. Additonally cleaned up the `make links' target: Remove unnecessary semicolons, subsequent redundant removes, inline point.sh into mklink.sh to speed processing and no longer clutter the display with confusing stuff. Instead only the actually done links are displayed.
1999-03-06 20:32:06 +08:00
@(cd test && echo "testing..." && \
For the main directory, Makefile.org is significant :-)
2002-06-06 18:21:04 +08:00
$(MAKE) CC='${CC}' PLATFORM='${PLATFORM}' CFLAG='${CFLAG}' SDIRS='$(SDIRS)' INSTALLTOP='${INSTALLTOP}' PEX_LIBS='${PEX_LIBS}' EX_LIBS='${EX_LIBS}' BN_ASM='${BN_ASM}' DES_ENC='${DES_ENC}' BF_ENC='${BF_ENC}' CAST_ENC='${CAST_ENC}' RC4_ENC='${RC4_ENC}' RC5_ENC='${RC5_ENC}' SHA1_ASM_OBJ='${SHA1_ASM_OBJ}' MD5_ASM_OBJ='${MD5_ASM_OBJ}' RMD160_ASM_OBJ='${RMD160_ASM_OBJ}' AR='${AR}' PROCESSOR='${PROCESSOR}' PERL='${PERL}' RANLIB='${RANLIB}' TESTS='${TESTS}' KRB5_INCLUDES='${KRB5_INCLUDES}' LIBKRB5='${LIBKRB5}' EXE_EXT='${EXE_EXT}' SHARED_LIBS='${SHARED_LIBS}' SHLIB_EXT='${SHLIB_EXT}' SHLIB_TARGET='${SHLIB_TARGET}' TESTS='${TESTS}' OPENSSL_DEBUG_MEMORY=on tests );
Make sure that all the library paths are modified in prepend mode, not replace mode. PR: 528
2003-03-20 19:37:47 +08:00
@LD_LIBRARY_PATH="`pwd`:LD_LIBRARY_PATH"; \
DYLD_LIBRARY_PATH="`pwd`:DYLD_LIBRARY_PATH"; \
SHLIB_PATH="`pwd`:SHLIB_PATH"; \
LIBPATH="`pwd`:LIBPATH"; \
if [ "$(PLATFORM)" = "Cygwin" ]; then PATH="`pwd`:$$PATH"; fi; \
export LD_LIBRARY_PATH DYLD_LIBRARY_PATH SHLIB_PATH LIBPATH PATH; \
apps/openssl version -a
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
New make target "report" to run util/selftest.pl
2000-02-24 07:47:05 +08:00
report:
@$(PERL) util/selftest.pl
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
depend:
@for i in $(DIRS) ;\
do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making dependencies $$i..." && \
Pass CFLAG to dependency makers, so non-standard system include paths are handled properly. Part of PR 75
2002-06-28 00:39:25 +08:00
$(MAKE) SDIRS='${SDIRS}' CFLAG='${CFLAG}' DEPFLAG='${DEPFLAG}' MAKEDEPPROG='${MAKEDEPPROG}' KRB5_INCLUDES='${KRB5_INCLUDES}' PERL='${PERL}' depend ) || exit 1; \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
lint:
@for i in $(DIRS) ;\
do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making lint $$i..." && \
$(MAKE) SDIRS='${SDIRS}' lint ) || exit 1; \
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
tags:
@for i in $(DIRS) ;\
do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i && echo "making tags $$i..." && \
$(MAKE) SDIRS='${SDIRS}' tags ) || exit 1; \
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done;
errors:
Use $(PERL) in place of hard-coded perl
2001-01-11 00:40:30 +08:00
$(PERL) util/mkerr.pl -recurse -write
Step 12 of move of engines: Time to make the changes to support automatic load of dynamic engines. Make the changes in the main Makefile so the engines are built, but now in the engines/ directory. Note: The changes in step 12 have all been made by Geoff Thorpe. Credit where credit is due.
2002-10-12 02:51:29 +08:00
(cd engines; $(MAKE) PERL=$(PERL) errors)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
This change will cause builds (by default) to not use different STACK structures and functions for each stack type. The previous behaviour can be enabled by configuring with the "-DDEBUG_SAFESTACK" option. This will also cause "make update" (mkdef.pl in particular) to update the libeay.num and ssleay.num symbol tables with the number of extra functions DEBUG_SAFESTACK creates. The way this change works is to accompany each DECLARE_STACK_OF() macro with a set of "#define"d versions of the sk_##type##_*** functions that ensures all the existing "type-safe" stack calls are precompiled into the underlying stack calls. The presence or abscence of the DEBUG_SAFESTACK symbol controls whether this block of "#define"s or the DECLARE_STACK_OF() macro is taking effect. The block of "#define"s is in turn generated and maintained by a perl script (util/mkstack.pl) that encompasses the block with delimiting C comments. This works in a similar way to the auto-generated error codes and, like the other such maintenance utilities, is invoked by the "make update" target. A long (but mundane) commit will follow this with the results of "make update" - this will include all the "#define" blocks for each DECLARE_STACK_OF() statement, along with stripped down libeay.num and ssleay.num files.
2000-06-01 13:13:52 +08:00
stacks:
Use $(PERL) in place of hard-coded perl
2001-01-11 00:40:30 +08:00
$(PERL) util/mkstack.pl -write
This change will cause builds (by default) to not use different STACK structures and functions for each stack type. The previous behaviour can be enabled by configuring with the "-DDEBUG_SAFESTACK" option. This will also cause "make update" (mkdef.pl in particular) to update the libeay.num and ssleay.num symbol tables with the number of extra functions DEBUG_SAFESTACK creates. The way this change works is to accompany each DECLARE_STACK_OF() macro with a set of "#define"d versions of the sk_##type##_*** functions that ensures all the existing "type-safe" stack calls are precompiled into the underlying stack calls. The presence or abscence of the DEBUG_SAFESTACK symbol controls whether this block of "#define"s or the DECLARE_STACK_OF() macro is taking effect. The block of "#define"s is in turn generated and maintained by a perl script (util/mkstack.pl) that encompasses the block with delimiting C comments. This works in a similar way to the auto-generated error codes and, like the other such maintenance utilities, is invoked by the "make update" target. A long (but mundane) commit will follow this with the results of "make update" - this will include all the "#define" blocks for each DECLARE_STACK_OF() statement, along with stripped down libeay.num and ssleay.num files.
2000-06-01 13:13:52 +08:00
"make update" (added to top Makefile, and applied).
1999-06-10 00:18:53 +08:00
util/libeay.num::
Use $(PERL) in place of hard-coded perl
2001-01-11 00:40:30 +08:00
$(PERL) util/mkdef.pl crypto update
"make update" (added to top Makefile, and applied).
1999-06-10 00:18:53 +08:00
util/ssleay.num::
Use $(PERL) in place of hard-coded perl
2001-01-11 00:40:30 +08:00
$(PERL) util/mkdef.pl ssl update
"make update" (added to top Makefile, and applied).
1999-06-10 00:18:53 +08:00
Change obj_... generation so that it does not generate rubbish or abort with errors if no name is defined for some object, which was the case for 'pilotAttributeType 27'. Also avoid this very situation by assigning the name 'pilotAttributeType27'.
2001-03-06 16:58:38 +08:00
crypto/objects/obj_dat.h: crypto/objects/obj_dat.pl crypto/objects/obj_mac.h
Use $(PERL) in place of hard-coded perl
2001-01-11 00:40:30 +08:00
$(PERL) crypto/objects/obj_dat.pl crypto/objects/obj_mac.h crypto/objects/obj_dat.h
typo
2001-03-14 00:30:09 +08:00
crypto/objects/obj_mac.h: crypto/objects/objects.pl crypto/objects/objects.txt crypto/objects/obj_mac.num
Use $(PERL) in place of hard-coded perl
2001-01-11 00:40:30 +08:00
$(PERL) crypto/objects/objects.pl crypto/objects/objects.txt crypto/objects/obj_mac.num crypto/objects/obj_mac.h
Generate obj_dat.h in "make update".
1999-09-30 05:03:02 +08:00
Oops, I forgot to add the dependency "TABLE: Configure".
1999-06-10 05:13:30 +08:00
TABLE: Configure
tiny optical change
1999-06-10 07:13:03 +08:00
(echo 'Output of `Configure TABLE'"':"; \
Use $(PERL) in place of hard-coded perl
2001-01-11 00:40:30 +08:00
$(PERL) Configure TABLE) > TABLE
"make update" (added to top Makefile, and applied).
1999-06-10 00:18:53 +08:00
This change will cause builds (by default) to not use different STACK structures and functions for each stack type. The previous behaviour can be enabled by configuring with the "-DDEBUG_SAFESTACK" option. This will also cause "make update" (mkdef.pl in particular) to update the libeay.num and ssleay.num symbol tables with the number of extra functions DEBUG_SAFESTACK creates. The way this change works is to accompany each DECLARE_STACK_OF() macro with a set of "#define"d versions of the sk_##type##_*** functions that ensures all the existing "type-safe" stack calls are precompiled into the underlying stack calls. The presence or abscence of the DEBUG_SAFESTACK symbol controls whether this block of "#define"s or the DECLARE_STACK_OF() macro is taking effect. The block of "#define"s is in turn generated and maintained by a perl script (util/mkstack.pl) that encompasses the block with delimiting C comments. This works in a similar way to the auto-generated error codes and, like the other such maintenance utilities, is invoked by the "make update" target. A long (but mundane) commit will follow this with the results of "make update" - this will include all the "#define" blocks for each DECLARE_STACK_OF() statement, along with stripped down libeay.num and ssleay.num files.
2000-06-01 13:13:52 +08:00
update: depend errors stacks util/libeay.num util/ssleay.num crypto/objects/obj_dat.h TABLE
"make update" (added to top Makefile, and applied).
1999-06-10 00:18:53 +08:00
Support building the distribution .tar file on platforms with limited argument list length. This requires Gnu-tar. As we use the non-standard "tardy" software anyway, it doesn't hurt too much to require Gnu-tar. "make dist" will probably only be used by team-members anyway.
2002-06-12 20:26:34 +08:00
# Build distribution tar-file. As the list of files returned by "find" is
# pretty long, on several platforms a "too many arguments" error or similar
# would occur. Therefore the list of files is temporarily stored into a file
# and read directly, requiring GNU-Tar. Call "make TAR=gtar dist" if the normal
# tar does not support the --files-from option.
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
tar:
Make sure permissions are friendly when building release tar file. Submitted by: Reviewed by: PR: 171
2002-11-11 16:57:04 +08:00
find . -type d -print | xargs chmod 755
find . -type f -print | xargs chmod a+r
find . -type f -perm -0100 -print | xargs chmod a+x
Support building the distribution .tar file on platforms with limited argument list length. This requires Gnu-tar. As we use the non-standard "tardy" software anyway, it doesn't hurt too much to require Gnu-tar. "make dist" will probably only be used by team-members anyway.
2002-06-12 20:26:34 +08:00
find * \! -path CVS/\* \! -path \*/CVS/\* \! -name CVS \! -name .cvsignore \! -name STATUS \! -name TABLE | sort > ../$(TARFILE).list; \
$(TAR) $(TARFLAGS) --files-from ../$(TARFILE).list -cvf - | \
Start with some more tarball rolling preparation to make sure it's not overlooed next Monday: - rmlinks is no longer existing - use openssl as the name and not rse - don't roll the STATUS file into the tarball
1999-03-08 20:17:53 +08:00
tardy --user_number=0 --user_name=openssl \
*** empty log message ***
1998-12-23 15:58:53 +08:00
--group_number=0 --group_name=openssl \
--prefix=openssl-$(VERSION) - |\
Various cleanups and fixed by Marc and Ralf to start the OpenTLS project
1998-12-22 23:04:48 +08:00
gzip --best >../$(TARFILE).gz; \
Support building the distribution .tar file on platforms with limited argument list length. This requires Gnu-tar. As we use the non-standard "tardy" software anyway, it doesn't hurt too much to require Gnu-tar. "make dist" will probably only be used by team-members anyway.
2002-06-12 20:26:34 +08:00
rm -f ../$(TARFILE).list; \
Various cleanups and fixed by Marc and Ralf to start the OpenTLS project
1998-12-22 23:04:48 +08:00
ls -l ../$(TARFILE).gz
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
e_os.h does not belong with the exported headers. Do not put it there and make all files the depend on it include it without prefixing it with openssl/. This means that all Makefiles will have $(TOP) as one of the include directories.
2001-02-22 22:45:02 +08:00
tar-snap:
@$(TAR) $(TARFLAGS) -cvf - \
Avoid emacs backup files when making a snapshot
2002-04-13 20:28:44 +08:00
`find * \! -path CVS/\* \! -path \*/CVS/\* \! -name CVS \! -name .cvsignore \! -name STATUS \! -name TABLE \! -name '*.o' \! -name '*.a' \! -name '*.so' \! -name '*.so.*' \! -name 'openssl' \! -name '*test' \! -name '.#*' \! -name '*~' | sort` |\
e_os.h does not belong with the exported headers. Do not put it there and make all files the depend on it include it without prefixing it with openssl/. This means that all Makefiles will have $(TOP) as one of the include directories.
2001-02-22 22:45:02 +08:00
tardy --user_number=0 --user_name=openssl \
--group_number=0 --group_name=openssl \
--prefix=openssl-$(VERSION) - > ../$(TARFILE);\
ls -l ../$(TARFILE)
Import of old SSLeay release: SSLeay 0.9.0b
1998-12-21 18:56:39 +08:00
dist:
New Makefile variables $(RANLIB) and $(PERL).
1999-04-01 20:34:33 +08:00
$(PERL) Configure dist
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
@$(MAKE) dist_pem_h
@$(MAKE) SDIRS='${SDIRS}' clean
Make sure that flags are passed to "make" subprocesses.
2002-06-10 16:10:32 +08:00
@$(MAKE) TAR='${TAR}' TARFLAGS='${TARFLAGS}' tar
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
dist_pem_h:
VMS support. Submitted by: Richard Levitte <richard@levitte.org>
1999-05-13 19:37:32 +08:00
(cd crypto/pem; $(MAKE) CC='${CC}' SDIRS='${SDIRS}' CFLAG='${CFLAG}' pem.h; $(MAKE) clean)
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
Implement MD5-based "apr1" password hash.
2000-02-12 00:25:44 +08:00
install: all install_docs
Use mkdir-p.pl more efficiently.
1999-06-08 18:18:19 +08:00
@$(PERL) $(TOP)/util/mkdir-p.pl $(INSTALL_PREFIX)$(INSTALLTOP)/bin \
$(INSTALL_PREFIX)$(INSTALLTOP)/lib \
It was pointed out to me that .pc files are normally stored in ${prefix}/lib/pkgconfig, not ${prefix}/lib/pkginfo.
2002-12-20 01:44:42 +08:00
$(INSTALL_PREFIX)$(INSTALLTOP)/lib/pkgconfig \
Use mkdir-p.pl more efficiently.
1999-06-08 18:18:19 +08:00
$(INSTALL_PREFIX)$(INSTALLTOP)/include/openssl \
Step 12 of move of engines: Time to make the changes to support automatic load of dynamic engines. Make the changes in the main Makefile so the engines are built, but now in the engines/ directory. Note: The changes in step 12 have all been made by Geoff Thorpe. Credit where credit is due.
2002-10-12 02:51:29 +08:00
$(INSTALL_PREFIX)$(OPENSSLDIR)/engines \
Use mkdir-p.pl more efficiently.
1999-06-08 18:18:19 +08:00
$(INSTALL_PREFIX)$(OPENSSLDIR)/misc \
$(INSTALL_PREFIX)$(OPENSSLDIR)/certs \
$(INSTALL_PREFIX)$(OPENSSLDIR)/private \
Implement MD5-based "apr1" password hash.
2000-02-12 00:25:44 +08:00
$(INSTALL_PREFIX)$(OPENSSLDIR)/lib
e_os* corrections.
1999-05-15 21:24:16 +08:00
@for i in $(EXHEADER) ;\
do \
(cp $$i $(INSTALL_PREFIX)$(INSTALLTOP)/include/openssl/$$i; \
chmod 644 $(INSTALL_PREFIX)$(INSTALLTOP)/include/openssl/$$i ); \
done;
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
@for i in $(DIRS) ;\
do \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
if [ -d "$$i" ]; then \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
(cd $$i; echo "installing $$i..."; \
We need to propogate SHARED_LIBS to sub-directories for "install" targets now.
2002-10-19 03:05:32 +08:00
$(MAKE) CC='${CC}' CFLAG='${CFLAG}' INSTALL_PREFIX='${INSTALL_PREFIX}' INSTALLTOP='${INSTALLTOP}' OPENSSLDIR='${OPENSSLDIR}' EX_LIBS='${EX_LIBS}' SDIRS='${SDIRS}' RANLIB='${RANLIB}' EXE_EXT='${EXE_EXT}' SHARED_LIBS='${SHARED_LIBS}' install ); \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
fi; \
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
done
@for i in $(LIBS) ;\
do \
Redo and enhance the support for building shared libraries. Currently there's support for building under Linux and True64 (using examples from the programming manuals), including versioning that is currently the same as OpenSSL versions but should really be a different series. With this change, it's up to the users to decide if they want shared libraries as well as the static ones. This decision now has to be done at configuration time (well, not really, those who know what they do can still do it the same way as before). The OpenSSL programs (openssl and the test programs) are currently always linked statically, but this may change in the future in a configurable manner. The necessary makefile variables to enable this are in place. Also note that I have done absolutely nothing about the Windows target to get something similar. On the other hand, DLLs are already the default there, but without versioning, and I've no idea what the possibilities for such a thing are there...
2000-07-21 23:08:53 +08:00
if [ -f "$$i" ]; then \
( echo installing $$i; \
Installed libraries should not be overwritten, especially shared ones. Use mv to make sure the old copy is unlinked instead of overwritten. PR: 273, and probably others...
2002-10-04 21:43:43 +08:00
cp $$i $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new; \
$(RANLIB) $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new; \
chmod 644 $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new; \
Update the make system for installations: - define a HERE variable to indicate where the source tree is (used very little right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
2002-12-15 13:59:13 +08:00
mv -f $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i ); \
Add missing ";" after fi Submitted by: bryanh@giraffe-data.com Reviewed by: PR: [openssl.org #18]
2002-05-07 23:35:48 +08:00
fi; \
done;
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
@if [ -n "$(SHARED_LIBS)" ]; then \
tmp="$(SHARED_LIBS)"; \
for i in $${tmp:-x}; \
do \
Update the configuration of CygWin32 to use the new capabilities of CygWin 1.3.x, which includes thread and shared library support. Submitted by Corinna Vinschen <vinschen@redhat.com> and modified a little bit.
2002-02-13 22:44:33 +08:00
if [ -f "$$i" -o -f "$$i.a" ]; then \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
( echo installing $$i; \
At Corinna Vinschen's request, change CygWin32 to Cygwin
2002-02-14 20:28:24 +08:00
if [ "$(PLATFORM)" != "Cygwin" ]; then \
Installed libraries should not be overwritten, especially shared ones. Use mv to make sure the old copy is unlinked instead of overwritten. PR: 273, and probably others...
2002-10-04 21:43:43 +08:00
cp $$i $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new; \
chmod 555 $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new; \
Update the make system for installations: - define a HERE variable to indicate where the source tree is (used very little right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
2002-12-15 13:59:13 +08:00
mv -f $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i; \
Update the configuration of CygWin32 to use the new capabilities of CygWin 1.3.x, which includes thread and shared library support. Submitted by Corinna Vinschen <vinschen@redhat.com> and modified a little bit.
2002-02-13 22:44:33 +08:00
else \
c=`echo $$i | sed 's/^lib/cyg/'`; \
Installed libraries should not be overwritten, especially shared ones. Use mv to make sure the old copy is unlinked instead of overwritten. PR: 273, and probably others...
2002-10-04 21:43:43 +08:00
cp $$c $(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new; \
chmod 755 $(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new; \
Update the make system for installations: - define a HERE variable to indicate where the source tree is (used very little right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
2002-12-15 13:59:13 +08:00
mv -f $(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new $(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c; \
Installed libraries should not be overwritten, especially shared ones. Use mv to make sure the old copy is unlinked instead of overwritten. PR: 273, and probably others...
2002-10-04 21:43:43 +08:00
cp $$i.a $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.a.new; \
chmod 644 $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.a.new; \
Update the make system for installations: - define a HERE variable to indicate where the source tree is (used very little right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
2002-12-15 13:59:13 +08:00
mv -f $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.a.new $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.a; \
Update the configuration of CygWin32 to use the new capabilities of CygWin 1.3.x, which includes thread and shared library support. Submitted by Corinna Vinschen <vinschen@redhat.com> and modified a little bit.
2002-02-13 22:44:33 +08:00
fi ); \
Add missing ";" after fi Submitted by: bryanh@giraffe-data.com Reviewed by: PR: [openssl.org #18]
2002-05-07 23:35:48 +08:00
fi; \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
done; \
( here="`pwd`"; \
cd $(INSTALL_PREFIX)$(INSTALLTOP)/lib; \
Update the make system for installations: - define a HERE variable to indicate where the source tree is (used very little right now) - make more use of copying and making attribute changes to {file}.new, and then move it to {file} - use 'mv -f' to avoid all those questions to the user when the file in question doesn't have write attributes for that user.
2002-12-15 13:59:13 +08:00
$(NEWMAKE) -f $$here/Makefile HERE="$$here" link-shared ); \
Add documentation on how to handle the shared libaries. PR: 423
2003-01-11 00:14:32 +08:00
if [ "$(INSTALLTOP)" != "/usr" ]; then \
echo 'OpenSSL shared libraries have been installed in:'; \
echo ' $(INSTALLTOP)'; \
echo ''; \
Double the dollars that are intended for the command line. PR: 423
2003-01-11 00:32:32 +08:00
sed -e '1,/^$$/d' doc/openssl-shared.txt; \
Add documentation on how to handle the shared libaries. PR: 423
2003-01-11 00:14:32 +08:00
fi; \
Rework the system to generate shared libraries: - Make note of the expected extension for the shared libraries and if there is a need for symbolic links from for example libcrypto.so.0 to libcrypto.so.0.9.7. There is extended info in Configure for that. - Make as few rebuilds of the shared libraries as possible. - Still avoid linking the OpenSSL programs with the shared libraries. - When installing, install the shared libraries separately from the static ones.
2000-10-13 23:25:06 +08:00
fi
It was pointed out to me that .pc files are normally stored in ${prefix}/lib/pkgconfig, not ${prefix}/lib/pkginfo.
2002-12-20 01:42:23 +08:00
cp openssl.pc $(INSTALL_PREFIX)$(INSTALLTOP)/lib/pkgconfig
Implement MD5-based "apr1" password hash.
2000-02-12 00:25:44 +08:00
install_docs:
@$(PERL) $(TOP)/util/mkdir-p.pl \
Install manpages below OPENSSLDIR (I think it was meant to be this way?). New variable for man directory.
2000-02-16 02:34:46 +08:00
$(INSTALL_PREFIX)$(MANDIR)/man1 \
$(INSTALL_PREFIX)$(MANDIR)/man3 \
$(INSTALL_PREFIX)$(MANDIR)/man5 \
$(INSTALL_PREFIX)$(MANDIR)/man7
change how pod2man is handled: explicitly invoke '$PERL' only when needed, call 'pod2man' directly if this works PR: 217
2002-08-14 22:04:24 +08:00
@pod2man="`cd util; ./pod2mantest $(PERL)`"; \
Make sure manual pages are properly linked to on systems that have case insensitive file names, as well as those that do not have symlinks. Incidently, both these cases apply on DOS/Windows...
2002-12-15 14:45:43 +08:00
here="`pwd`"; \
filecase=; \
if [ "$(PLATFORM)" = "DJGPP" -o "$(PLATFORM)" = "Cygwin" ]; then \
filecase=-i; \
fi; \
We don't need to find out which pod2man to use more than once
2002-08-02 05:52:56 +08:00
for i in doc/apps/*.pod; do \
Add a couple of forgotten $(PERL), and make the code to run pod2html a tad more readable.
2000-02-15 00:55:23 +08:00
fn=`basename $$i .pod`; \
'||', '&&' and 'test -x' apparently don't work on Ultrix; also 'test' appears to be available as '[' only in 'if' conditions.
2001-04-08 21:49:45 +08:00
if [ "$$fn" = "config" ]; then sec=5; else sec=1; fi; \
Make it so all names mentioned in the NAME section of each manpage becomes a symlink to said manpage. PR: 242
2002-11-29 23:00:58 +08:00
echo "installing man$$sec/$$fn.$$sec"; \
Make perl replacement for dirname, for system that lack the latter. PR: 81
2002-06-05 22:10:59 +08:00
(cd `$(PERL) util/dirname.pl $$i`; \
change how pod2man is handled: explicitly invoke '$PERL' only when needed, call 'pod2man' directly if this works PR: 217
2002-08-14 22:04:24 +08:00
sh -c "$$pod2man \
Apparently, there are still chances we have to deal with buggy pod2man versions. Deal with that by testing any available pod2man and using it if appropriate, and falling back to util/pod2man.pl if none was found.
2002-05-30 23:19:43 +08:00
--section=$$sec --center=OpenSSL \
--release=$(VERSION) `basename $$i`") \
Make it so all names mentioned in the NAME section of each manpage becomes a symlink to said manpage. PR: 242
2002-11-29 23:00:58 +08:00
> $(INSTALL_PREFIX)$(MANDIR)/man$$sec/$$fn.$$sec; \
Make sure manual pages are properly linked to on systems that have case insensitive file names, as well as those that do not have symlinks. Incidently, both these cases apply on DOS/Windows...
2002-12-15 14:45:43 +08:00
$(PERL) util/extract-names.pl < $$i | \
grep -v $$filecase "^$$fn\$$" | \
(cd $(INSTALL_PREFIX)$(MANDIR)/man$$sec/; \
while read n; do \
$$here/util/point.sh $$fn.$$sec $$n.$$sec; \
done); \
We don't need to find out which pod2man to use more than once
2002-08-02 05:52:56 +08:00
done; \
Fix "make install_docs" (and thus "make install").
2002-08-05 04:40:23 +08:00
for i in doc/crypto/*.pod doc/ssl/*.pod; do \
Add a couple of forgotten $(PERL), and make the code to run pod2html a tad more readable.
2000-02-15 00:55:23 +08:00
fn=`basename $$i .pod`; \
'||', '&&' and 'test -x' apparently don't work on Ultrix; also 'test' appears to be available as '[' only in 'if' conditions.
2001-04-08 21:49:45 +08:00
if [ "$$fn" = "des_modes" ]; then sec=7; else sec=3; fi; \
Make it so all names mentioned in the NAME section of each manpage becomes a symlink to said manpage. PR: 242
2002-11-29 23:00:58 +08:00
echo "installing man$$sec/$$fn.$$sec"; \
Make perl replacement for dirname, for system that lack the latter. PR: 81
2002-06-05 22:10:59 +08:00
(cd `$(PERL) util/dirname.pl $$i`; \
change how pod2man is handled: explicitly invoke '$PERL' only when needed, call 'pod2man' directly if this works PR: 217
2002-08-14 22:04:24 +08:00
sh -c "$$pod2man \
Apparently, there are still chances we have to deal with buggy pod2man versions. Deal with that by testing any available pod2man and using it if appropriate, and falling back to util/pod2man.pl if none was found.
2002-05-30 23:19:43 +08:00
--section=$$sec --center=OpenSSL \
--release=$(VERSION) `basename $$i`") \
Make it so all names mentioned in the NAME section of each manpage becomes a symlink to said manpage. PR: 242
2002-11-29 23:00:58 +08:00
> $(INSTALL_PREFIX)$(MANDIR)/man$$sec/$$fn.$$sec; \
Make sure manual pages are properly linked to on systems that have case insensitive file names, as well as those that do not have symlinks. Incidently, both these cases apply on DOS/Windows...
2002-12-15 14:45:43 +08:00
$(PERL) util/extract-names.pl < $$i | \
grep -v $$filecase "^$$fn\$$" | \
(cd $(INSTALL_PREFIX)$(MANDIR)/man$$sec/; \
while read n; do \
$$here/util/point.sh $$fn.$$sec $$n.$$sec; \
done); \
Add a couple of forgotten $(PERL), and make the code to run pod2html a tad more readable.
2000-02-15 00:55:23 +08:00
done
Import of old SSLeay release: SSLeay 0.8.1b
1998-12-21 18:52:47 +08:00
# DO NOT DELETE THIS LINE -- make depend depends on it.
Reference in New Issue Copy Permalink