• Registered: Yesterday
  • Posts: 2

Topic: NOOB: First compile header build order

Good evening.
I've built the WolfSSL and WolfMQTT with Visual Studio 2022.
Now I'm trying to build the "simple" mqtt example.

I get this:

#elif !defined(BUILDING_WOLFSSL) && !defined(WOLFSSL_OPTIONS_H) && \
      !defined(WOLFSSL_NO_OPTIONS_H) && !defined(WOLFSSL_CUSTOM_CONFIG)
    /* This warning indicates that wolfSSL features may not have been properly
     * configured before other wolfSSL headers were included. If you are using
     * an alternative configuration method -- e.g. custom header, or CFLAGS in
     * an application build -- then your application can avoid this warning by
     * defining WOLFSSL_NO_OPTIONS_H or WOLFSSL_CUSTOM_CONFIG as appropriate.
     */
    #warning "No configuration for wolfSSL detected, check header order"

What SSL options do I need to do a basic compile?
What's the correct include header order?

Thanks

Share

2 Reply by embhorn

  • From: Mobile, AL
  • Registered: 2013-12-11
  • Posts: 367

Re: NOOB: First compile header build order

Hi Jay,

Welcome to the wolfSSL Forums! Could you tell us a bit about your project using wolfMQTT?

I'd recommend starting with building the mqttclient example in VS. We did not create a VS project for the mqttsimple example.

The project settings for the example need to have the right pre-proccessor macros and include path set up. You can review the existing example projects to see the required settings.

Thanks,
Eric - wolfSSL Support

embhorn's Website

Share

  • Registered: Yesterday
  • Posts: 2

Re: NOOB: First compile header build order

Good afternoon.

Thanks for the help. I thought the simple example would be the easiest validation.

I switched to the nbclient example and was able to get it to work after updating the include directories.
It posts to my mosquitto mqtt server just fine. Kudos to you and your team.

I think the issue is it relies on definitions created by the autoconfig, which isn't an option on a windows build.
I don't think it really adds much value compared to the other examples so you might consider just removing it from the distribution.

I had the idea I could create a graphics intense IOT console by connecting the Unreal Game Engine and MQTT.
nbclient will be a great starting point.

Share