<![CDATA[wolfSSL - Embedded SSL Library — cmake feature request]]> https://www.wolfssl.com/forums/topic1654-cmake-feature-request.html Mon, 11 Jan 2021 18:48:05 +0000 PunBB <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5697.html#p5697 Glad to hear it's working!

]]> Mon, 11 Jan 2021 18:48:05 +0000 https://www.wolfssl.com/forums/post5697.html#p5697 <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5695.html#p5695 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.

]]> Mon, 11 Jan 2021 17:40:11 +0000 https://www.wolfssl.com/forums/post5695.html#p5695 <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5694.html#p5694 I've added another CMake option, WOLFSSL_CONFIG_H, to the PR I linked above. Add -DWOLFSSL_CONFIG_H=no to your cmake command to turn off generation of config.h and the definition of HAVE_CONFIG_H.

]]> Mon, 11 Jan 2021 16:48:34 +0000 https://www.wolfssl.com/forums/post5694.html#p5694 <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5684.html#p5684 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.

]]> Fri, 08 Jan 2021 18:01:01 +0000 https://www.wolfssl.com/forums/post5684.html#p5684 <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5679.html#p5679 I still see -DHAVE_CONFIG_H in my compile command line, which is causing build errors.  How do I remove it?

]]> Thu, 07 Jan 2021 14:42:13 +0000 https://www.wolfssl.com/forums/post5679.html#p5679 <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5674.html#p5674 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

]]> Mon, 04 Jan 2021 15:44:23 +0000 https://www.wolfssl.com/forums/post5674.html#p5674 <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5673.html#p5673 Hi John,

I recently overhauled wolfSSL's CMake, and Tesfa is correct, what you describe hasn't been added, yet. I'll take a look at it today; it shouldn't be very complex.

Thanks,

Hayden

]]> Mon, 04 Jan 2021 15:19:42 +0000 https://www.wolfssl.com/forums/post5673.html#p5673 <![CDATA[Re: cmake feature request]]> https://www.wolfssl.com/forums/post5671.html#p5671 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

]]> Thu, 31 Dec 2020 19:41:07 +0000 https://www.wolfssl.com/forums/post5671.html#p5671 <![CDATA[cmake feature request]]> https://www.wolfssl.com/forums/post5670.html#p5670 Would it be possible to provide an easy way to disable all default settings and only enable the compiler define
-DWOLFSSL_USER_SETTINGS?

This would make it easier to make quick changes to features and settings without having to use a complicated cmake command every time.

Regards,
John

]]> Thu, 31 Dec 2020 15:34:23 +0000 https://www.wolfssl.com/forums/post5670.html#p5670