Espressif Update wolfSSL component CMakeLists.txt #6877
Merged
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
wolfssl_benchmark
,wolfssl_test
, (as well as TLS Client/Server) examples using wolfssl as an Espressif component. Only aCMakeLists.txt
file is local to the component; it searches for wolfSSL source.user_settings.h
.${WOLFSSL_ROOT}/include/user_settings.h
.partitions_singleapp_large.csv
for consistency across project examples.#6844 is currently failing Jenkins tests as the respective
CMakeLists.txt
checks for both a wolfSSL/include/user_settings.h
and a[project]/components/wolfssl/include/user_settings.h
. Since those TLS examples support (and in fact, prefer) per-projectuser_settings.h
, the build process fails due to the prior copy of theuser_settings.h
into/include/user_settings.h
by the wolfssl_benchmark build.user_settings.h
(error if also in root/include
), and half expecting shared (TLS Client/Server, not yet updated, see #6844, (Error if also found locally): This update now changes theCmakeLists.txt
for all 4 primary examples.See #6234 for a roadmap of Espressif updates.
Fixes zd# n/a
Testing
How did you test?
manually tested locally
Checklist