You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR# 6018 introduced the capability of "no setup" wolfSSL for the Espressif ESP-IDF projects. The examples now all use this feature. The code that runs is the code that is in the project. Not only does this make wolfSSL development significantly easier, but it also makes the Getting Started experience much better by eliminating the install process that copied wolfSSL files into the ESP-IDF components directory.
In the current configuration, a single wolfssl user_settings.h is created in the root of the wolfssl clone and shared amongst all projects: "${WOLFSSL_ROOT}/include/user_settings.h".
@PaulMartinsen and @LizardM4 have both suggested having the capability of a project-specific user_settings.h file. This is a great idea! I've tested this and it seems to work just fine. The new file location would be in a new local project wolfssl/include directory.
Version
Latest master branch
Description
PR# 6018 introduced the capability of "no setup" wolfSSL for the Espressif ESP-IDF projects. The examples now all use this feature. The code that runs is the code that is in the project. Not only does this make wolfSSL development significantly easier, but it also makes the Getting Started experience much better by eliminating the install process that copied wolfSSL files into the ESP-IDF
components
directory.In the current configuration, a single wolfssl
user_settings.h
is created in the root of the wolfssl clone and shared amongst all projects:"${WOLFSSL_ROOT}/include/user_settings.h"
.@PaulMartinsen and @LizardM4 have both suggested having the capability of a project-specific
user_settings.h
file. This is a great idea! I've tested this and it seems to work just fine. The new file location would be in a new local projectwolfssl/include
directory.See also espressif/esp-wolfssl#17
See #6234 for a roadmap of Espressif updates.
The text was updated successfully, but these errors were encountered: