<![CDATA[wolfSSL - Embedded SSL Library — Building for Integrity]]> https://www.wolfssl.com/forums/topic2260-building-for-integrity.html Tue, 15 Apr 2025 20:04:09 +0000 PunBB <![CDATA[Re: Building for Integrity]]> https://www.wolfssl.com/forums/post8308.html#p8308 I've got --enable-cryptonly --disable-opensslextra set and wolfssl/ssl.h on line 2845 is still trying to include stdarg.h. What am I missing?

]]> Tue, 15 Apr 2025 20:04:09 +0000 https://www.wolfssl.com/forums/post8308.html#p8308 <![CDATA[Re: Building for Integrity]]> https://www.wolfssl.com/forums/post8203.html#p8203 wolfSSL will attempt to include stdarg.h if OPENSSL_EXTRA is defined, you'll need to remove this define if you don't have this header available on your system.

]]> Thu, 06 Feb 2025 18:59:07 +0000 https://www.wolfssl.com/forums/post8203.html#p8203 <![CDATA[Re: Building for Integrity]]> https://www.wolfssl.com/forums/post8202.html#p8202 Okay I've made a bit of progress, but WolfSSL is still attempting to include stdarg.h when it is not available in ssl.h. Is there a way to disable this?

]]> Thu, 06 Feb 2025 18:25:57 +0000 https://www.wolfssl.com/forums/post8202.html#p8202 <![CDATA[Re: Building for Integrity]]> https://www.wolfssl.com/forums/post8181.html#p8181 This define will go in your user_settings.h, you can find more information on and some examples of user_settings here: https://github.com/wolfSSL/wolfssl/tree … es/configs
I would recommend starting with user_settings_template.h and adjusting it to your use case.

]]> Fri, 17 Jan 2025 18:08:52 +0000 https://www.wolfssl.com/forums/post8181.html#p8181 <![CDATA[Re: Building for Integrity]]> https://www.wolfssl.com/forums/post8178.html#p8178 If I wanted to manually define INTEGRITY where would that go? I'm new to this so I'm doing a bit of bumbling.

]]> Thu, 16 Jan 2025 23:41:30 +0000 https://www.wolfssl.com/forums/post8178.html#p8178 <![CDATA[Re: Building for Integrity]]> https://www.wolfssl.com/forums/post8177.html#p8177 Hi Bryce,

Thank you for your interest in wolfSSL and great question.  For Integrity OS, you will need to define __INTEGRITY or INTEGRITY, this define should be set by default by your toolchain.
We have various IDE example projects here which you may find helpful: https://github.com/wolfSSL/wolfssl/tree/master/IDE

May I ask what kind of project you are using wolfSSL in and whether it is personal or commercial?  You are welcome to email us at support [AT] wolfssl [DOT] com if these details are sensitive.

Thanks,
Kareem

]]> Thu, 16 Jan 2025 23:14:14 +0000 https://www.wolfssl.com/forums/post8177.html#p8177 <![CDATA[Building for Integrity]]> https://www.wolfssl.com/forums/post8176.html#p8176 I'm currently trying to get WolfSSL to build on the Integrity OS and beyond using

NO_FILESYSTEM
USER_TIME
USER_TICKS

I'm not sure what options I need to enable to get it to port over to Integrity?

Any ideas?

]]> Thu, 16 Jan 2025 23:10:23 +0000 https://www.wolfssl.com/forums/post8176.html#p8176