Update wolfcrypt settings.h for Espressif ESP-IDF, template update #7953
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Building on the capabilities introduced in #7936, #7893, #7866 this PR moves some of the common Espressif Kconfig settings and feature detection from
user_settings.h
to the wolfcryptsettings.h
file.Included is a minor update & code sync to the reference
template
application. See the respectiveuser_settings.h
for an example of howKconfig
settings (viasdkconfig.h
) are used.I'm planning on updates to all of the other Espressif examples (test, benchmark, client, server) very soon, hopefully in time for the next release.
The intention is for all wolfSSL examples and reference code to have exactly the same component
user_settings.h
,Kconfig
, andCMakeLists.txt
files. All the application-specific settings can then be assigned via the respectivesdkconfig.defaults
files and/or changed viaidf.py menuconfig
rather than manual edits touser_settings.h
. This is important for the wolfssl Managed Component that doesn't like source code edits, including changes to theuser_settings.h
.There's no adverse effect for non-Managed Component apps. The
user_settings.h
can still be edited. There's still a peripheral benefit of having consistent files throughout all the examples.Fixes zd# n/a
Testing
How did you test?
Primarily tested in the Espressif environment, with a quick
make clean
andmake test
before PR submission.Checklist