hostap: Fix crypto=none compilation
If CONFIG_WIFI_NM_WPA_SUPPLICANT_CRYPTO_NONE is enabled, there are lot of missing functions reported during linking. Add missing C files to the compilation to fix this. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
This commit is contained in:
parent
e9ec7a23a3
commit
980a352d39
1 changed files with 21 additions and 0 deletions
|
|
@ -243,6 +243,27 @@ zephyr_library_compile_definitions_ifdef(CONFIG_WIFI_NM_HOSTAPD_AP
|
||||||
zephyr_library_sources_ifdef(CONFIG_WIFI_NM_WPA_SUPPLICANT_CRYPTO_NONE
|
zephyr_library_sources_ifdef(CONFIG_WIFI_NM_WPA_SUPPLICANT_CRYPTO_NONE
|
||||||
${HOSTAP_SRC_BASE}/crypto/crypto_none.c
|
${HOSTAP_SRC_BASE}/crypto/crypto_none.c
|
||||||
${HOSTAP_SRC_BASE}/crypto/tls_none.c
|
${HOSTAP_SRC_BASE}/crypto/tls_none.c
|
||||||
|
|
||||||
|
# FIXME: why do we need these when crypto is not selected?
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/aes-wrap.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/aes-internal.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/aes-internal-enc.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/aes-omac1.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/md5.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/md5-internal.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha1.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha1-internal.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha1-pbkdf2.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha1-prf.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha256.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha256-internal.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha256-prf.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha384.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha384-internal.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha384-prf.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha512.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/sha512-internal.c
|
||||||
|
${HOSTAP_SRC_BASE}/crypto/rc4.c
|
||||||
)
|
)
|
||||||
|
|
||||||
zephyr_library_compile_definitions_ifdef(CONFIG_WIFI_NM_WPA_SUPPLICANT_CRYPTO_NONE
|
zephyr_library_compile_definitions_ifdef(CONFIG_WIFI_NM_WPA_SUPPLICANT_CRYPTO_NONE
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue