2015-11-24 05:44:58 +00:00
|
|
|
## -*- mode: perl; -*-
|
2015-02-24 22:40:22 +00:00
|
|
|
## Build configuration targets for openssl-team members
|
|
|
|
|
2017-12-01 14:29:05 +00:00
|
|
|
my %targets = (
|
2015-03-10 23:58:50 +00:00
|
|
|
"purify" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix' ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "purify gcc",
|
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-06 19:35:30 +00:00
|
|
|
CFLAGS => "-g -Wall",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "(unknown)",
|
2016-02-27 10:37:33 +00:00
|
|
|
ex_libs => add(" ","-lsocket -lnsl"),
|
2015-03-10 23:58:50 +00:00
|
|
|
},
|
|
|
|
"debug" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix' ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "gcc",
|
2016-01-30 17:04:25 +00:00
|
|
|
cflags => "-DBN_DEBUG -DREF_DEBUG -DCONF_DEBUG -DBN_CTX_DEBUG -DOPENSSL_NO_ASM -ggdb -g2 -Wformat -Wshadow -Wmissing-prototypes -Wmissing-declarations -Werror",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "(unknown)",
|
2015-03-10 23:58:50 +00:00
|
|
|
},
|
|
|
|
"debug-erbridge" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix', "x86_64_asm" ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "gcc",
|
2019-05-27 12:40:25 +00:00
|
|
|
cflags => combine(join(' ', @gcc_devteam_warn),
|
2019-02-26 08:32:52 +00:00
|
|
|
"-DBN_DEBUG -DCONF_DEBUG -m64 -DL_ENDIAN -DTERMIO -g",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
threads("-D_REENTRANT")),
|
2016-02-27 10:37:33 +00:00
|
|
|
ex_libs => add(" ","-ldl"),
|
2016-01-27 23:43:25 +00:00
|
|
|
bn_ops => "SIXTY_FOUR_BIT_LONG",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "pthreads",
|
2015-03-10 23:58:50 +00:00
|
|
|
perlasm_scheme => "elf",
|
|
|
|
dso_scheme => "dlfcn",
|
|
|
|
shared_target => "linux-shared",
|
|
|
|
shared_cflag => "-fPIC",
|
|
|
|
shared_ldflag => "-m64",
|
|
|
|
multilib => "64",
|
|
|
|
},
|
|
|
|
"debug-linux-pentium" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix', "x86_elf_asm" ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "gcc",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
cflags => combine("-DBN_DEBUG -DREF_DEBUG -DCONF_DEBUG -DBN_CTX_DEBUG -DL_ENDIAN -g -mcpu=pentium -Wall",
|
|
|
|
threads("-D_REENTRANT")),
|
2016-02-27 10:37:33 +00:00
|
|
|
ex_libs => add(" ","-ldl"),
|
2016-01-28 00:16:38 +00:00
|
|
|
bn_ops => "BN_LLONG",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "pthreads",
|
2015-03-10 23:58:50 +00:00
|
|
|
dso_scheme => "dlfcn",
|
|
|
|
},
|
|
|
|
"debug-linux-ppro" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix', "x86_elf_asm" ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "gcc",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
cflags => combine("-DBN_DEBUG -DREF_DEBUG -DCONF_DEBUG -DBN_CTX_DEBUG -DL_ENDIAN -g -mcpu=pentiumpro -Wall",
|
|
|
|
threads("-D_REENTRANT")),
|
2016-02-27 10:37:33 +00:00
|
|
|
ex_libs => add(" ","-ldl"),
|
2016-01-28 00:16:38 +00:00
|
|
|
bn_ops => "BN_LLONG",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "pthreads",
|
2015-03-10 23:58:50 +00:00
|
|
|
dso_scheme => "dlfcn",
|
|
|
|
},
|
|
|
|
"debug-linux-ia32-aes" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix' ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "gcc",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
cflags => combine("-DL_ENDIAN -O3 -fomit-frame-pointer -Wall",
|
|
|
|
threads("-D_REENTRANT")),
|
2016-02-27 10:37:33 +00:00
|
|
|
ex_libs => add(" ","-ldl"),
|
2016-01-28 00:16:38 +00:00
|
|
|
bn_ops => "BN_LLONG",
|
2016-01-29 18:45:51 +00:00
|
|
|
cpuid_asm_src => "x86cpuid.s",
|
|
|
|
bn_asm_src => "bn-586.s co-586.s x86-mont.s",
|
|
|
|
des_asm_src => "des-586.s crypt586.s",
|
|
|
|
aes_asm_src => "aes_x86core.s aes_cbc.s aesni-x86.s",
|
|
|
|
bf_asm_src => "bf-586.s",
|
|
|
|
md5_asm_src => "md5-586.s",
|
|
|
|
sha1_asm_src => "sha1-586.s sha256-586.s sha512-586.s",
|
|
|
|
cast_asm_src => "cast-586.s",
|
|
|
|
rc4_asm_src => "rc4-586.s",
|
|
|
|
rmd160_asm_src => "rmd-586.s",
|
|
|
|
rc5_asm_src => "rc5-586.s",
|
|
|
|
wp_asm_src => "wp_block.s wp-mmx.s",
|
|
|
|
modes_asm_src => "ghash-x86.s",
|
|
|
|
padlock_asm_src => "e_padlock-x86.s",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "pthreads",
|
2015-03-10 23:58:50 +00:00
|
|
|
perlasm_scheme => "elf",
|
|
|
|
dso_scheme => "dlfcn",
|
|
|
|
shared_target => "linux-shared",
|
|
|
|
shared_cflag => "-fPIC",
|
|
|
|
},
|
|
|
|
"debug-test-64-clang" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix', "x86_64_asm" ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "clang",
|
2019-05-27 12:40:25 +00:00
|
|
|
cflags => combine(join(' ', @gcc_devteam_warn),
|
2019-02-26 08:32:52 +00:00
|
|
|
"-Wno-error=overlength-strings -Wno-error=extended-offsetof -Wno-error=language-extension-token -Wno-error=unused-const-variable -Wstrict-overflow -Qunused-arguments -DBN_DEBUG -DCONF_DEBUG -DDEBUG_SAFESTACK -DDEBUG_UNUSED -g3 -O3 -pipe",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
threads("${BSDthreads}")),
|
2016-01-27 23:43:25 +00:00
|
|
|
bn_ops => "SIXTY_FOUR_BIT_LONG",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "pthreads",
|
2015-03-10 23:58:50 +00:00
|
|
|
perlasm_scheme => "elf",
|
|
|
|
dso_scheme => "dlfcn",
|
|
|
|
shared_target => "bsd-gcc-shared",
|
|
|
|
shared_cflag => "-fPIC",
|
|
|
|
},
|
|
|
|
"darwin64-debug-test-64-clang" => {
|
2018-01-27 12:06:39 +00:00
|
|
|
inherit_from => [ 'BASE_unix', "x86_64_asm" ],
|
2015-03-10 23:58:50 +00:00
|
|
|
cc => "clang",
|
2019-02-26 08:32:52 +00:00
|
|
|
cflags => combine("-arch x86_64 -DL_ENDIAN",
|
2019-05-27 12:40:25 +00:00
|
|
|
join(' ', @gcc_devteam_warn),
|
2019-02-26 08:32:52 +00:00
|
|
|
"-Wno-error=overlength-strings -Wno-error=extended-offsetof -Wno-error=language-extension-token -Wno-error=unused-const-variable -Wstrict-overflow -Qunused-arguments -DBN_DEBUG -DCONF_DEBUG -DDEBUG_SAFESTACK -DDEBUG_UNUSED -g3 -O3 -pipe",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
threads("${BSDthreads}")),
|
2015-03-10 23:58:50 +00:00
|
|
|
sys_id => "MACOSX",
|
2016-01-27 23:43:25 +00:00
|
|
|
bn_ops => "SIXTY_FOUR_BIT_LONG",
|
Configure - Get rid of the special thread_cflag, replace with thread_scheme
The thread_cflag setting filled a double role, as kinda sorta an
indicator of thread scheme, and as cflags. Some configs also added
lflags and ex_libs for multithreading regardless of if threading would
be enabled or not.
Instead of this, add threading cflags among in the cflag setting,
threading lflags in the lflag setting and so on if and only if threads
are enabled (which they are by default).
Also, for configs where there are no special cflags for threading (the
VMS configs are of that kind), this makes it possible to still clearly
mention what thread scheme is used.
The exact value of thread scheme is currently ignored except when it's
"(unknown)", and thereby only serves as a flag to tell if we know how
to build for multi-threading in a particular config. Yet, the
currently used values are "(unknown)", "pthreads", "uithreads" (a.k.a
solaris threads) and "winthreads".
Reviewed-by: Andy Polyakov <appro@openssl.org>
2016-02-27 15:51:34 +00:00
|
|
|
thread_scheme => "pthreads",
|
2015-03-10 23:58:50 +00:00
|
|
|
perlasm_scheme => "macosx",
|
|
|
|
dso_scheme => "dlfcn",
|
|
|
|
shared_target => "darwin-shared",
|
|
|
|
shared_cflag => "-fPIC -fno-common",
|
|
|
|
shared_ldflag => "-arch x86_64 -dynamiclib",
|
2017-07-19 08:13:41 +00:00
|
|
|
shared_extension => ".\$(SHLIB_VERSION_NUMBER).dylib",
|
2015-03-10 23:58:50 +00:00
|
|
|
},
|
2015-02-24 22:40:22 +00:00
|
|
|
);
|