2016-01-30 06:33:10 +08:00
|
|
|
LIBS=../../libcrypto
|
2019-06-17 03:20:43 +08:00
|
|
|
|
|
|
|
|
$BFASM=bf_enc.c
|
|
|
|
|
IF[{- !$disabled{asm} -}]
|
|
|
|
|
$BFASM_x86=bf-586.s
|
|
|
|
|
|
|
|
|
|
# Now that we have defined all the arch specific variables, use the
|
|
|
|
|
# appropriate one
|
|
|
|
|
IF[$BFASM_{- $target{asm_arch} -}]
|
|
|
|
|
$BFASM=$BFASM_{- $target{asm_arch} -}
|
|
|
|
|
ENDIF
|
|
|
|
|
ENDIF
|
|
|
|
|
|
|
|
|
|
SOURCE[../../libcrypto]=bf_skey.c bf_ecb.c bf_cfb64.c bf_ofb64.c $BFASM
|
2016-01-30 10:25:40 +08:00
|
|
|
|
2018-01-23 20:54:55 +08:00
|
|
|
GENERATE[bf-586.s]=asm/bf-586.pl \
|
Harmonize the make variables across all known platforms families
The make variables LIB_CFLAGS, DSO_CFLAGS and so on were used in
addition to CFLAGS and so on. This works without problem on Unix and
Windows, where options with different purposes (such as -D and -I) can
appear anywhere on the command line and get accumulated as they come.
This is not necessarely so on VMS. For example, macros must all be
collected and given through one /DEFINE, and the same goes for
inclusion directories (/INCLUDE).
So, to harmonize all platforms, we repurpose make variables starting
with LIB_, DSO_ and BIN_ to be all encompassing variables that
collects the corresponding values from CFLAGS, CPPFLAGS, DEFINES,
INCLUDES and so on together with possible config target values
specific for libraries DSOs and programs, and use them instead of the
general ones everywhere.
This will, for example, allow VMS to use the exact same generators for
generated files that go through cpp as all other platforms, something
that has been impossible to do safely before now.
Reviewed-by: Andy Polyakov <appro@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5357)
2018-02-14 03:32:42 +08:00
|
|
|
$(PERLASM_SCHEME) $(LIB_CFLAGS) $(LIB_CPPFLAGS) $(PROCESSOR)
|
2016-03-07 22:13:01 +08:00
|
|
|
DEPEND[bf-586.s]=../perlasm/x86asm.pl ../perlasm/cbc.pl
|