wolfssl: make FIPS config variables overrideable from the project

Switched variable assignments to use "?=" to allow setting them from the
project's configuration file (local.conf) without modifying the bbappend.

This allows for a clean update of meta-wolfssl, as the repository no
longer needs to retain local changes.

Signed-off-by: Javier Viguera <javier.viguera@digi.com>
pull/102/head
Javier Viguera 2025-05-23 14:14:47 +02:00
parent 21795dc628
commit cd6f99c2dd
1 changed files with 5 additions and 5 deletions

View File

@ -1,13 +1,13 @@
#Adjust these as needed
WOLFSSL_VERSION=""
WOLFSSL_VERSION ?= ""
WOLF_LICENSE="WolfSSL_LicenseAgmt_JAN-2022.pdf"
WOLF_LICENSE_MD5="be28609dc681e98236c52428fadf04dd"
WOLF_SRC=""
WOLF_SRC_SHA=""
WOLF_SRC_PASS=""
WOLF_SRC ?= ""
WOLF_SRC_SHA ?= ""
WOLF_SRC_PASS ?= ""
FIPS_HASH="FFBB0434EB0EF2860CBAF6CB29F8F39B4432439EFD2A24C7D6442CBA8E06A4CC"
FIPS_HASH ?= "FFBB0434EB0EF2860CBAF6CB29F8F39B4432439EFD2A24C7D6442CBA8E06A4CC"
#Do not adjust these variables
PR = "commercial.fips"