• Registered: 2024-12-16
  • Posts: 2

Topic: Building for Integrity

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?

Share

  • Registered: 2021-07-06
  • Posts: 156

Re: Building for Integrity

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

Share

  • Registered: 2024-12-16
  • Posts: 2

Re: Building for Integrity

If I wanted to manually define INTEGRITY where would that go? I'm new to this so I'm doing a bit of bumbling.

Share

  • Registered: 2021-07-06
  • Posts: 156

Re: Building for Integrity

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.

Share