1 Reply by fenster

(3 replies, posted in wolfSSL)

So in other words, I will need to rebuild wolfssl using various flags, and for CAAM the required build is even more complicated, correct?

Once it is built, do we need any special parameters when callign wolfssl?

Go to forum: wolfSSL

2 Topic by fenster

(3 replies, posted in wolfSSL)

Does the out of the box wolfssl build have support for hardware acceleration on the IMX8 Cortex A53? If not, how can it be enabled?
Once enabled, how can it be specified for usage in the code?

Go to forum: wolfSSL

3 Topic by fenster

(1 replies, posted in wolfSSL)

Where can I find some examples of using DTLS using the python wrapper?

Go to forum: wolfSSL

4 Reply by fenster

(3 replies, posted in wolfSSL)

Also when running "make deb" after ./configure and a successful "make", I get the following error:
make[1]: Leaving directory '/home/fenster/tmp/z0131/wolfssl-5.7.0-commercial'
fakeroot dh_makeshlibs
dh_shlibdeps
dh_installdeb
fakeroot dh_gencontrol
cp: cannot stat 'debian/copyright': No such file or directory
make: *** [Makefile:9383: deb] Error 1

Go to forum: wolfSSL

5 Reply by fenster

(3 replies, posted in wolfSSL)

The wolfssl-py instructions discuss the usage of USE_LOCAL_WOLFSSL. Can you please clarify it's usage?
Will the wolfssl libraries be included in the resulting package? Is the usage of USE_LOCAL_WOLFSSL to control where the wolfssl-py looks for the wolfssl libraries and as a result does not include them in the build?

Go to forum: wolfSSL

6 Topic by fenster

(3 replies, posted in wolfSSL)

What is the best practice for building (from scratch, given the source code tar ball) a debian package that contains both the wolfssl libraries and the python wrapper?

Go to forum: wolfSSL