|
|
|
|
include_directories(../../include)
|
|
|
|
|
|
Avoid double-expanding variables in CMake.
CMake's language is rather fragile and unsound. For the most part, it is
a shell script with more parentheses. That is, it simply expands command
arguments into a list of strings and then evaluates it, complete with
shell-style differences between "${FOO}" and ${FOO}.
The if() command is special and internally also expands variables. That
is why things like if(FOO STREQUAL "BAR") work. CMake interprets "FOO"
as a variable if it can find a variable, or a string otherwise. In
addition to getting very confused on typos, it means that
if("${FOO}" STREQUAL "BAR") will double-expand, and it will do strange
things if BAR is a variable.
CMP0054 patches this (which we set by minimum version) so that if() only
expands if the token was unquoted. This fixes
if("${FOO}" STREQUAL "BAR"). However, if(${FOO} STREQUAL "BAR")
continues to double-expand FOO.
We had a mix of all three of FOO, ${FOO}, and "${FOO}". It's not clear
which is the canonical spelling at this point, but CMake own files
(mostly) use FOO, as do most of our lines, so I've standardized on that.
It's a little unsatisfying if we typo a variable, but I suppose ${FOO}
also silently ignores unset variables.
Bug: 423
Change-Id: Ib6baa27f4065eed159e8fb28820b71a0c99e0db0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48705
Reviewed-by: Adam Langley <agl@google.com>
4 years ago
|
|
|
if(ARCH STREQUAL "x86_64")
|
|
|
|
|
set(
|
|
|
|
|
BCM_ASM_SOURCES
|
|
|
|
|
|
|
|
|
|
aesni-gcm-x86_64.${ASM_EXT}
|
|
|
|
|
aesni-x86_64.${ASM_EXT}
|
|
|
|
|
ghash-ssse3-x86_64.${ASM_EXT}
|
|
|
|
|
ghash-x86_64.${ASM_EXT}
|
|
|
|
|
md5-x86_64.${ASM_EXT}
|
|
|
|
|
p256-x86_64-asm.${ASM_EXT}
|
|
|
|
|
p256_beeu-x86_64-asm.${ASM_EXT}
|
|
|
|
|
rdrand-x86_64.${ASM_EXT}
|
|
|
|
|
rsaz-avx2.${ASM_EXT}
|
|
|
|
|
sha1-x86_64.${ASM_EXT}
|
|
|
|
|
sha256-x86_64.${ASM_EXT}
|
|
|
|
|
sha512-x86_64.${ASM_EXT}
|
|
|
|
|
vpaes-x86_64.${ASM_EXT}
|
|
|
|
|
x86_64-mont5.${ASM_EXT}
|
|
|
|
|
x86_64-mont.${ASM_EXT}
|
|
|
|
|
)
|
|
|
|
|
endif()
|
|
|
|
|
|
Avoid double-expanding variables in CMake.
CMake's language is rather fragile and unsound. For the most part, it is
a shell script with more parentheses. That is, it simply expands command
arguments into a list of strings and then evaluates it, complete with
shell-style differences between "${FOO}" and ${FOO}.
The if() command is special and internally also expands variables. That
is why things like if(FOO STREQUAL "BAR") work. CMake interprets "FOO"
as a variable if it can find a variable, or a string otherwise. In
addition to getting very confused on typos, it means that
if("${FOO}" STREQUAL "BAR") will double-expand, and it will do strange
things if BAR is a variable.
CMP0054 patches this (which we set by minimum version) so that if() only
expands if the token was unquoted. This fixes
if("${FOO}" STREQUAL "BAR"). However, if(${FOO} STREQUAL "BAR")
continues to double-expand FOO.
We had a mix of all three of FOO, ${FOO}, and "${FOO}". It's not clear
which is the canonical spelling at this point, but CMake own files
(mostly) use FOO, as do most of our lines, so I've standardized on that.
It's a little unsatisfying if we typo a variable, but I suppose ${FOO}
also silently ignores unset variables.
Bug: 423
Change-Id: Ib6baa27f4065eed159e8fb28820b71a0c99e0db0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48705
Reviewed-by: Adam Langley <agl@google.com>
4 years ago
|
|
|
if(ARCH STREQUAL "x86")
|
|
|
|
|
set(
|
|
|
|
|
BCM_ASM_SOURCES
|
|
|
|
|
|
|
|
|
|
aesni-x86.${ASM_EXT}
|
|
|
|
|
bn-586.${ASM_EXT}
|
|
|
|
|
co-586.${ASM_EXT}
|
|
|
|
|
ghash-ssse3-x86.${ASM_EXT}
|
|
|
|
|
ghash-x86.${ASM_EXT}
|
|
|
|
|
md5-586.${ASM_EXT}
|
|
|
|
|
sha1-586.${ASM_EXT}
|
|
|
|
|
sha256-586.${ASM_EXT}
|
|
|
|
|
sha512-586.${ASM_EXT}
|
|
|
|
|
vpaes-x86.${ASM_EXT}
|
|
|
|
|
x86-mont.${ASM_EXT}
|
|
|
|
|
)
|
|
|
|
|
endif()
|
|
|
|
|
|
Avoid double-expanding variables in CMake.
CMake's language is rather fragile and unsound. For the most part, it is
a shell script with more parentheses. That is, it simply expands command
arguments into a list of strings and then evaluates it, complete with
shell-style differences between "${FOO}" and ${FOO}.
The if() command is special and internally also expands variables. That
is why things like if(FOO STREQUAL "BAR") work. CMake interprets "FOO"
as a variable if it can find a variable, or a string otherwise. In
addition to getting very confused on typos, it means that
if("${FOO}" STREQUAL "BAR") will double-expand, and it will do strange
things if BAR is a variable.
CMP0054 patches this (which we set by minimum version) so that if() only
expands if the token was unquoted. This fixes
if("${FOO}" STREQUAL "BAR"). However, if(${FOO} STREQUAL "BAR")
continues to double-expand FOO.
We had a mix of all three of FOO, ${FOO}, and "${FOO}". It's not clear
which is the canonical spelling at this point, but CMake own files
(mostly) use FOO, as do most of our lines, so I've standardized on that.
It's a little unsatisfying if we typo a variable, but I suppose ${FOO}
also silently ignores unset variables.
Bug: 423
Change-Id: Ib6baa27f4065eed159e8fb28820b71a0c99e0db0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48705
Reviewed-by: Adam Langley <agl@google.com>
4 years ago
|
|
|
if(ARCH STREQUAL "arm")
|
|
|
|
|
set(
|
|
|
|
|
BCM_ASM_SOURCES
|
|
|
|
|
|
|
|
|
|
aesv8-armx.${ASM_EXT}
|
|
|
|
|
armv4-mont.${ASM_EXT}
|
|
|
|
|
bsaes-armv7.${ASM_EXT}
|
|
|
|
|
ghash-armv4.${ASM_EXT}
|
|
|
|
|
ghashv8-armx.${ASM_EXT}
|
|
|
|
|
sha1-armv4-large.${ASM_EXT}
|
|
|
|
|
sha256-armv4.${ASM_EXT}
|
|
|
|
|
sha512-armv4.${ASM_EXT}
|
|
|
|
|
vpaes-armv7.${ASM_EXT}
|
|
|
|
|
)
|
|
|
|
|
endif()
|
|
|
|
|
|
Avoid double-expanding variables in CMake.
CMake's language is rather fragile and unsound. For the most part, it is
a shell script with more parentheses. That is, it simply expands command
arguments into a list of strings and then evaluates it, complete with
shell-style differences between "${FOO}" and ${FOO}.
The if() command is special and internally also expands variables. That
is why things like if(FOO STREQUAL "BAR") work. CMake interprets "FOO"
as a variable if it can find a variable, or a string otherwise. In
addition to getting very confused on typos, it means that
if("${FOO}" STREQUAL "BAR") will double-expand, and it will do strange
things if BAR is a variable.
CMP0054 patches this (which we set by minimum version) so that if() only
expands if the token was unquoted. This fixes
if("${FOO}" STREQUAL "BAR"). However, if(${FOO} STREQUAL "BAR")
continues to double-expand FOO.
We had a mix of all three of FOO, ${FOO}, and "${FOO}". It's not clear
which is the canonical spelling at this point, but CMake own files
(mostly) use FOO, as do most of our lines, so I've standardized on that.
It's a little unsatisfying if we typo a variable, but I suppose ${FOO}
also silently ignores unset variables.
Bug: 423
Change-Id: Ib6baa27f4065eed159e8fb28820b71a0c99e0db0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48705
Reviewed-by: Adam Langley <agl@google.com>
4 years ago
|
|
|
if(ARCH STREQUAL "aarch64")
|
|
|
|
|
set(
|
|
|
|
|
BCM_ASM_SOURCES
|
|
|
|
|
|
|
|
|
|
aesv8-armx.${ASM_EXT}
|
|
|
|
|
armv8-mont.${ASM_EXT}
|
|
|
|
|
ghash-neon-armv8.${ASM_EXT}
|
|
|
|
|
ghashv8-armx.${ASM_EXT}
|
|
|
|
|
sha1-armv8.${ASM_EXT}
|
|
|
|
|
sha256-armv8.${ASM_EXT}
|
|
|
|
|
sha512-armv8.${ASM_EXT}
|
|
|
|
|
vpaes-armv8.${ASM_EXT}
|
|
|
|
|
)
|
|
|
|
|
endif()
|
|
|
|
|
|
Avoid double-expanding variables in CMake.
CMake's language is rather fragile and unsound. For the most part, it is
a shell script with more parentheses. That is, it simply expands command
arguments into a list of strings and then evaluates it, complete with
shell-style differences between "${FOO}" and ${FOO}.
The if() command is special and internally also expands variables. That
is why things like if(FOO STREQUAL "BAR") work. CMake interprets "FOO"
as a variable if it can find a variable, or a string otherwise. In
addition to getting very confused on typos, it means that
if("${FOO}" STREQUAL "BAR") will double-expand, and it will do strange
things if BAR is a variable.
CMP0054 patches this (which we set by minimum version) so that if() only
expands if the token was unquoted. This fixes
if("${FOO}" STREQUAL "BAR"). However, if(${FOO} STREQUAL "BAR")
continues to double-expand FOO.
We had a mix of all three of FOO, ${FOO}, and "${FOO}". It's not clear
which is the canonical spelling at this point, but CMake own files
(mostly) use FOO, as do most of our lines, so I've standardized on that.
It's a little unsatisfying if we typo a variable, but I suppose ${FOO}
also silently ignores unset variables.
Bug: 423
Change-Id: Ib6baa27f4065eed159e8fb28820b71a0c99e0db0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48705
Reviewed-by: Adam Langley <agl@google.com>
4 years ago
|
|
|
if(ARCH STREQUAL "ppc64le")
|
|
|
|
|
set(
|
|
|
|
|
BCM_ASM_SOURCES
|
|
|
|
|
|
|
|
|
|
aesp8-ppc.${ASM_EXT}
|
|
|
|
|
ghashp8-ppc.${ASM_EXT}
|
|
|
|
|
)
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
perlasm(aesni-gcm-x86_64.${ASM_EXT} modes/asm/aesni-gcm-x86_64.pl)
|
|
|
|
|
perlasm(aesni-x86_64.${ASM_EXT} aes/asm/aesni-x86_64.pl)
|
|
|
|
|
perlasm(aesni-x86.${ASM_EXT} aes/asm/aesni-x86.pl)
|
|
|
|
|
perlasm(aesp8-ppc.${ASM_EXT} aes/asm/aesp8-ppc.pl)
|
|
|
|
|
perlasm(aesv8-armx.${ASM_EXT} aes/asm/aesv8-armx.pl)
|
|
|
|
|
perlasm(armv4-mont.${ASM_EXT} bn/asm/armv4-mont.pl)
|
|
|
|
|
perlasm(armv8-mont.${ASM_EXT} bn/asm/armv8-mont.pl)
|
|
|
|
|
perlasm(bn-586.${ASM_EXT} bn/asm/bn-586.pl)
|
|
|
|
|
perlasm(bsaes-armv7.${ASM_EXT} aes/asm/bsaes-armv7.pl)
|
|
|
|
|
perlasm(co-586.${ASM_EXT} bn/asm/co-586.pl)
|
|
|
|
|
perlasm(ghash-armv4.${ASM_EXT} modes/asm/ghash-armv4.pl)
|
|
|
|
|
perlasm(ghashp8-ppc.${ASM_EXT} modes/asm/ghashp8-ppc.pl)
|
|
|
|
|
perlasm(ghashv8-armx.${ASM_EXT} modes/asm/ghashv8-armx.pl)
|
|
|
|
|
perlasm(ghash-neon-armv8.${ASM_EXT} modes/asm/ghash-neon-armv8.pl)
|
|
|
|
|
perlasm(ghash-ssse3-x86_64.${ASM_EXT} modes/asm/ghash-ssse3-x86_64.pl)
|
|
|
|
|
perlasm(ghash-ssse3-x86.${ASM_EXT} modes/asm/ghash-ssse3-x86.pl)
|
|
|
|
|
perlasm(ghash-x86_64.${ASM_EXT} modes/asm/ghash-x86_64.pl)
|
|
|
|
|
perlasm(ghash-x86.${ASM_EXT} modes/asm/ghash-x86.pl)
|
|
|
|
|
perlasm(md5-586.${ASM_EXT} md5/asm/md5-586.pl)
|
|
|
|
|
perlasm(md5-x86_64.${ASM_EXT} md5/asm/md5-x86_64.pl)
|
|
|
|
|
perlasm(p256-x86_64-asm.${ASM_EXT} ec/asm/p256-x86_64-asm.pl)
|
|
|
|
|
perlasm(p256_beeu-x86_64-asm.${ASM_EXT} ec/asm/p256_beeu-x86_64-asm.pl)
|
|
|
|
|
perlasm(rdrand-x86_64.${ASM_EXT} rand/asm/rdrand-x86_64.pl)
|
|
|
|
|
perlasm(rsaz-avx2.${ASM_EXT} bn/asm/rsaz-avx2.pl)
|
|
|
|
|
perlasm(sha1-586.${ASM_EXT} sha/asm/sha1-586.pl)
|
|
|
|
|
perlasm(sha1-armv4-large.${ASM_EXT} sha/asm/sha1-armv4-large.pl)
|
|
|
|
|
perlasm(sha1-armv8.${ASM_EXT} sha/asm/sha1-armv8.pl)
|
|
|
|
|
perlasm(sha1-x86_64.${ASM_EXT} sha/asm/sha1-x86_64.pl)
|
|
|
|
|
perlasm(sha256-586.${ASM_EXT} sha/asm/sha256-586.pl)
|
|
|
|
|
perlasm(sha256-armv4.${ASM_EXT} sha/asm/sha256-armv4.pl)
|
|
|
|
|
perlasm(sha256-armv8.${ASM_EXT} sha/asm/sha512-armv8.pl)
|
|
|
|
|
perlasm(sha256-x86_64.${ASM_EXT} sha/asm/sha512-x86_64.pl)
|
|
|
|
|
perlasm(sha512-586.${ASM_EXT} sha/asm/sha512-586.pl)
|
|
|
|
|
perlasm(sha512-armv4.${ASM_EXT} sha/asm/sha512-armv4.pl)
|
|
|
|
|
perlasm(sha512-armv8.${ASM_EXT} sha/asm/sha512-armv8.pl)
|
|
|
|
|
perlasm(sha512-x86_64.${ASM_EXT} sha/asm/sha512-x86_64.pl)
|
|
|
|
|
perlasm(vpaes-armv7.${ASM_EXT} aes/asm/vpaes-armv7.pl)
|
|
|
|
|
perlasm(vpaes-armv8.${ASM_EXT} aes/asm/vpaes-armv8.pl)
|
|
|
|
|
perlasm(vpaes-x86_64.${ASM_EXT} aes/asm/vpaes-x86_64.pl)
|
|
|
|
|
perlasm(vpaes-x86.${ASM_EXT} aes/asm/vpaes-x86.pl)
|
|
|
|
|
perlasm(x86_64-mont5.${ASM_EXT} bn/asm/x86_64-mont5.pl)
|
|
|
|
|
perlasm(x86_64-mont.${ASM_EXT} bn/asm/x86_64-mont.pl)
|
|
|
|
|
perlasm(x86-mont.${ASM_EXT} bn/asm/x86-mont.pl)
|
|
|
|
|
|
|
|
|
|
function(cpreprocess dest src)
|
|
|
|
|
set(TARGET "")
|
|
|
|
|
if(CMAKE_ASM_COMPILER_TARGET)
|
|
|
|
|
set(TARGET "--target=${CMAKE_ASM_COMPILER_TARGET}")
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
add_custom_command(
|
|
|
|
|
OUTPUT ${dest}
|
|
|
|
|
COMMAND ${CMAKE_ASM_COMPILER} ${TARGET} $CMAKE_ASM_FLAGS -E ${src} -I${PROJECT_SOURCE_DIR}/include > ${dest}
|
|
|
|
|
DEPENDS
|
|
|
|
|
${src}
|
|
|
|
|
${PROJECT_SOURCE_DIR}/include/openssl/arm_arch.h
|
|
|
|
|
WORKING_DIRECTORY .
|
|
|
|
|
)
|
|
|
|
|
endfunction()
|
|
|
|
|
|
|
|
|
|
if(FIPS_DELOCATE)
|
|
|
|
|
if(FIPS_SHARED)
|
|
|
|
|
error("Can't set both delocate and shared mode for FIPS build")
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
if(OPENSSL_NO_ASM)
|
|
|
|
|
# If OPENSSL_NO_ASM was defined then ASM will not have been enabled, but in
|
|
|
|
|
# FIPS mode we have to have it because the module build requires going via
|
|
|
|
|
# textual assembly.
|
|
|
|
|
enable_language(ASM)
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
add_library(
|
|
|
|
|
bcm_c_generated_asm
|
|
|
|
|
|
|
|
|
|
STATIC
|
|
|
|
|
|
|
|
|
|
bcm.c
|
|
|
|
|
)
|
|
|
|
|
|
Avoid double-expanding variables in CMake.
CMake's language is rather fragile and unsound. For the most part, it is
a shell script with more parentheses. That is, it simply expands command
arguments into a list of strings and then evaluates it, complete with
shell-style differences between "${FOO}" and ${FOO}.
The if() command is special and internally also expands variables. That
is why things like if(FOO STREQUAL "BAR") work. CMake interprets "FOO"
as a variable if it can find a variable, or a string otherwise. In
addition to getting very confused on typos, it means that
if("${FOO}" STREQUAL "BAR") will double-expand, and it will do strange
things if BAR is a variable.
CMP0054 patches this (which we set by minimum version) so that if() only
expands if the token was unquoted. This fixes
if("${FOO}" STREQUAL "BAR"). However, if(${FOO} STREQUAL "BAR")
continues to double-expand FOO.
We had a mix of all three of FOO, ${FOO}, and "${FOO}". It's not clear
which is the canonical spelling at this point, but CMake own files
(mostly) use FOO, as do most of our lines, so I've standardized on that.
It's a little unsatisfying if we typo a variable, but I suppose ${FOO}
also silently ignores unset variables.
Bug: 423
Change-Id: Ib6baa27f4065eed159e8fb28820b71a0c99e0db0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48705
Reviewed-by: Adam Langley <agl@google.com>
4 years ago
|
|
|
if(ARCH STREQUAL "aarch64")
|
|
|
|
|
# Perlasm output on Aarch64 needs to pass through the C preprocessor before
|
|
|
|
|
# it can be parsed by delocate.
|
|
|
|
|
foreach(asm ${BCM_ASM_SOURCES})
|
|
|
|
|
cpreprocess(${asm}.s ${asm})
|
|
|
|
|
list(APPEND BCM_ASM_PROCESSED_SOURCES "${asm}.s")
|
|
|
|
|
endforeach()
|
|
|
|
|
else()
|
|
|
|
|
# No preprocessing is required on other platforms.
|
|
|
|
|
set(BCM_ASM_PROCESSED_SOURCES ${BCM_ASM_SOURCES})
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
add_dependencies(bcm_c_generated_asm global_target)
|
|
|
|
|
|
|
|
|
|
set_target_properties(bcm_c_generated_asm PROPERTIES COMPILE_OPTIONS "-S")
|
|
|
|
|
set_target_properties(bcm_c_generated_asm PROPERTIES POSITION_INDEPENDENT_CODE ON)
|
|
|
|
|
|
|
|
|
|
go_executable(delocate boringssl.googlesource.com/boringssl/util/fipstools/delocate)
|
|
|
|
|
add_custom_command(
|
|
|
|
|
OUTPUT bcm-delocated.S
|
|
|
|
|
COMMAND ./delocate -a $<TARGET_FILE:bcm_c_generated_asm> -o bcm-delocated.S ${BCM_ASM_PROCESSED_SOURCES}
|
|
|
|
|
DEPENDS bcm_c_generated_asm delocate ${BCM_ASM_PROCESSED_SOURCES}
|
|
|
|
|
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_library(
|
|
|
|
|
bcm_hashunset
|
|
|
|
|
|
|
|
|
|
STATIC
|
|
|
|
|
|
|
|
|
|
bcm-delocated.S
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_dependencies(bcm_hashunset global_target)
|
|
|
|
|
|
|
|
|
|
set_target_properties(bcm_hashunset PROPERTIES POSITION_INDEPENDENT_CODE ON)
|
|
|
|
|
set_target_properties(bcm_hashunset PROPERTIES LINKER_LANGUAGE C)
|
|
|
|
|
|
|
|
|
|
set(MAYBE_INJECT_HASH_SHA256_FLAG "")
|
|
|
|
|
# If building with OPENSSL_NO_ASM then ARCH will be "generic", but we still
|
|
|
|
|
# need to use SHA-256. Since this only matters for FIPS, we only need to
|
|
|
|
|
# worry about the Linux spelling of AArch64.
|
Avoid double-expanding variables in CMake.
CMake's language is rather fragile and unsound. For the most part, it is
a shell script with more parentheses. That is, it simply expands command
arguments into a list of strings and then evaluates it, complete with
shell-style differences between "${FOO}" and ${FOO}.
The if() command is special and internally also expands variables. That
is why things like if(FOO STREQUAL "BAR") work. CMake interprets "FOO"
as a variable if it can find a variable, or a string otherwise. In
addition to getting very confused on typos, it means that
if("${FOO}" STREQUAL "BAR") will double-expand, and it will do strange
things if BAR is a variable.
CMP0054 patches this (which we set by minimum version) so that if() only
expands if the token was unquoted. This fixes
if("${FOO}" STREQUAL "BAR"). However, if(${FOO} STREQUAL "BAR")
continues to double-expand FOO.
We had a mix of all three of FOO, ${FOO}, and "${FOO}". It's not clear
which is the canonical spelling at this point, but CMake own files
(mostly) use FOO, as do most of our lines, so I've standardized on that.
It's a little unsatisfying if we typo a variable, but I suppose ${FOO}
also silently ignores unset variables.
Bug: 423
Change-Id: Ib6baa27f4065eed159e8fb28820b71a0c99e0db0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48705
Reviewed-by: Adam Langley <agl@google.com>
4 years ago
|
|
|
if (ARCH STREQUAL "aarch64" OR CMAKE_SYSTEM_PROCESSOR STREQUAL "aarch64")
|
|
|
|
|
set(MAYBE_INJECT_HASH_SHA256_FLAG "-sha256")
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
go_executable(inject_hash
|
|
|
|
|
boringssl.googlesource.com/boringssl/util/fipstools/inject_hash)
|
|
|
|
|
add_custom_command(
|
|
|
|
|
OUTPUT bcm.o
|
|
|
|
|
COMMAND ./inject_hash -o bcm.o -in-archive $<TARGET_FILE:bcm_hashunset> ${MAYBE_INJECT_HASH_SHA256_FLAG}
|
|
|
|
|
DEPENDS bcm_hashunset inject_hash
|
|
|
|
|
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
# The outputs of add_custom_command cannot be referenced outside of the
|
|
|
|
|
# CMakeLists.txt that defines it. Thus we have to wrap bcm.o in a custom target
|
|
|
|
|
# so that crypto can depend on it.
|
|
|
|
|
add_custom_target(bcm_o_target DEPENDS bcm.o)
|
|
|
|
|
|
|
|
|
|
add_library(
|
|
|
|
|
fipsmodule
|
|
|
|
|
|
|
|
|
|
OBJECT
|
|
|
|
|
|
|
|
|
|
fips_shared_support.c
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_dependencies(fipsmodule global_target)
|
|
|
|
|
|
|
|
|
|
set_target_properties(fipsmodule PROPERTIES LINKER_LANGUAGE C)
|
|
|
|
|
elseif(FIPS_SHARED)
|
|
|
|
|
if(NOT BUILD_SHARED_LIBS)
|
|
|
|
|
error("FIPS_SHARED set but not BUILD_SHARED_LIBS")
|
|
|
|
|
endif()
|
|
|
|
|
|
|
|
|
|
add_library(
|
|
|
|
|
fipsmodule
|
|
|
|
|
|
|
|
|
|
OBJECT
|
|
|
|
|
|
|
|
|
|
fips_shared_support.c
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_dependencies(fipsmodule global_target)
|
|
|
|
|
|
|
|
|
|
add_library(
|
|
|
|
|
bcm_library
|
|
|
|
|
|
|
|
|
|
STATIC
|
|
|
|
|
|
|
|
|
|
bcm.c
|
|
|
|
|
|
|
|
|
|
${BCM_ASM_SOURCES}
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_dependencies(bcm_library global_target)
|
|
|
|
|
|
|
|
|
|
add_custom_command(
|
|
|
|
|
OUTPUT bcm.o
|
|
|
|
|
COMMAND ${CMAKE_LINKER} -r -T ${CMAKE_CURRENT_SOURCE_DIR}/fips_shared.lds -o bcm.o --whole-archive $<TARGET_FILE:bcm_library>
|
|
|
|
|
DEPENDS bcm_library fips_shared.lds
|
|
|
|
|
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_custom_target(bcm_o_target DEPENDS bcm.o)
|
|
|
|
|
else()
|
|
|
|
|
add_library(
|
|
|
|
|
fipsmodule
|
|
|
|
|
|
|
|
|
|
OBJECT
|
|
|
|
|
|
|
|
|
|
bcm.c
|
|
|
|
|
fips_shared_support.c
|
|
|
|
|
|
|
|
|
|
${BCM_ASM_SOURCES}
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_dependencies(fipsmodule global_target)
|
|
|
|
|
endif()
|
