Hi stroebeljc,

Thanks for contacting wolfSSL!

We have made some improvements in our CMake build and that feature was likely missed.

I'll discuss this "enhancement" request with my colleague next week and get back to you.

Thanks,
Tesfa

Hi John,

Could you give the changes in this pull request a try and see if it gets you what you need? https://github.com/wolfSSL/wolfssl/pull/3617/files

Thanks,

Hayden

We strive to keep the CMake and autotools builds roughly equivalent, although the CMake build currently supports far fewer features than the autotools one. Enabling user settings in the autotools build still defines -DHAVE_CONFIG_H, hence why it's the same in the CMake build.

I can add an option to disable both generation of config.h and the defining of HAVE_CONFIG_H. It'll be off by default, for the reason stated above, but you can turn it on at the command line to get the behavior you want. I'll edit this post with the PR once it's up, as well as the command line option to use.

Thanks, @hayden.  That does work.

I found an issue with a missing define in my user_settings.h file that accounted for the compile problems.  However, the switch you added provides us with more confidence that the build configuration is as expected.