2016-05-11 19:47:19 +08:00
|
|
|
# We can't make any commitment to support the DJGPP platform,
|
|
|
|
|
# and rely entirely on the OpenSSL community to help is fine
|
|
|
|
|
# tune and test.
|
|
|
|
|
|
2017-12-01 22:29:05 +08:00
|
|
|
my %targets = (
|
2016-05-11 19:47:19 +08:00
|
|
|
"DJGPP" => {
|
|
|
|
|
inherit_from => [ asm("x86_asm") ],
|
Make "make variables" config attributes for overridable flags
With the support of "make variables" comes the possibility for the
user to override them. However, we need to make a difference between
defaults that we use (and that should be overridable by the user) and
flags that are crucial for building OpenSSL (should not be
overridable).
Typically, overridable flags are those setting optimization levels,
warnings levels, that kind of thing, while non-overridable flags are,
for example, macros that indicate aspects of how the config target
should be treated, such as L_ENDIAN and B_ENDIAN.
We do that differentiation by allowing upper case attributes in the
config targets, named exactly like the "make variables" we support,
and reserving the lower case attributes for non-overridable project
flags.
Reviewed-by: Andy Polyakov <appro@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5534)
2018-03-07 03:35:30 +08:00
|
|
|
CC => "gcc",
|
|
|
|
|
CFLAGS => "-fomit-frame-pointer -O2 -Wall",
|
|
|
|
|
cflags => "-I/dev/env/WATT_ROOT/inc -DTERMIOS -DL_ENDIAN",
|
2016-05-11 19:47:19 +08:00
|
|
|
sys_id => "MSDOS",
|
2018-01-08 19:28:08 +08:00
|
|
|
lflags => add("-L/dev/env/WATT_ROOT/lib"),
|
|
|
|
|
ex_libs => add("-lwatt"),
|
2016-05-11 19:47:19 +08:00
|
|
|
bn_ops => "BN_LLONG",
|
|
|
|
|
perlasm_scheme => "a.out",
|
|
|
|
|
},
|
|
|
|
|
);
|
