Daniel Pouzzner a3fb5029f8 clean up trailing whitespace and misplaced CRLFs, add missing final newlines, remove stray UTF8 nonprintables (BOMs) and ASCIIfy stray homoglyphs (spaces and apostrophes), guided by expanded coverage in wolfssl-multi-test check-source-text. | 2 tháng trước cách đây | |
---|---|---|
.. | ||
samples | 3 tháng trước cách đây | |
wolfssl | 7 tháng trước cách đây | |
CMakeLists.txt | 2 tháng trước cách đây | |
Kconfig | 4 tháng trước cách đây | |
Kconfig.tls-generic | 6 tháng trước cách đây | |
README.md | 3 tháng trước cách đây | |
include.am | 7 tháng trước cách đây | |
module.yml | 1 năm trước cách đây | |
user_settings-no-malloc.h | 3 tháng trước cách đây | |
user_settings.h | 4 tháng trước cách đây | |
zephyr_init.c | 3 tháng trước cách đây |
This port is for the Zephyr RTOS Project, available here.
It provides the following zephyr code.
Add wolfssl as a project to your west.yml:
manifest:
remotes:
# <your other remotes>
- name: wolfssl
url-base: https://github.com/wolfssl
projects:
# <your other projects>
- name: wolfssl
path: modules/crypto/wolfssl
revision: master
remote: wolfssl
If you are using the Nordic nRF Connect SDK with Zephyr, the sdk-nrf manifest
file is located at: vX.X.X/nrf/west.yml
. On OSX the default installation
location for the nRF Connect SDK is at /opt/nordic/ncs/vX.X.X
.
Update west's modules:
west update
Now west recognizes 'wolfssl' as a module, and will include it's Kconfig and CMakeFiles.txt in the build system.
If using the Nordic nRF Connect SDK, to get access to a terminal with west tool access, open "nRF Connect for Desktop", then "Toolchain Manager", and finally next to the SDK version you are using click the drop down arrow, then "Open Terminal".
If you want to run build apps without running west zephyr-export
then it is
possible by setting the CMAKE_PREFIX_PATH
variable to the location of the
zephyr sdk and building from the zephyr
directory. For example:
CMAKE_PREFIX_PATH=/path/to/zephyr-sdk-<VERSION> west build -p always -b qemu_x86 ../modules/crypto/wolfssl/zephyr/samples/wolfssl_test/
build and execute wolfssl_test
cd [zephyrproject]
west build -p auto -b qemu_x86 modules/crypto/wolfssl/zephyr/samples/wolfssl_test
west build -t run
build and execute wolfssl_benchmark
cd [zephyrproject]
west build -p auto -b qemu_x86 modules/crypto/wolfssl/zephyr/samples/wolfssl_benchmark
west build -t run
wolfssl_tls_sock
cd [zephyrproject]
west build -p auto -b qemu_x86 modules/crypto/wolfssl/zephyr/samples/wolfssl_tls_sock
west build -t run
wolfssl_tls_thread
cd [zephyrproject]
west build -p auto -b qemu_x86 modules/crypto/wolfssl/zephyr/samples/wolfssl_tls_thread
west build -t run
wolfSSL can also be used as the underlying implementation for the default Zephyr TLS socket interface. With this enabled, all existing applications using the Zephyr TLS sockets will now use wolfSSL inside for all TLS operations. This will also enable wolfSSL as the default RNG implementation. To enable this feature, use the patch file and instructions found here: