CPPFLAGS used for C sources

[wolfssl]

CPPFLAGS used for C sources

[ejohnstown]

@dgarske, this is due to AX_HARDEN_CC_COMPILER_FLAGS stepping on CFLAGS. By default, AC_PROG_CC sets CFLAGS to "-g -O2". In wolfSSL's configure.ac we are using the line ${CFLAGS=""} to initialize CFLAGS to an empty string if not provided on the configure command line to stop AC_PROG_CC from doing that and so we can add those options later. Unfortunately, the harden macro has the line "CFLAGS=" to zap the variable. (wolfSSL's C_EXTRA_FLAGS was an attempt to work around this until I fixed the harden macro.)

IMO, the harden macro should be adding its flags to AM_CFLAGS, but I haven't spent the time to change that.

[dgarske]

Hi denravonska,

I've pushed an update to PR #71 to resolve this.

Commit: 1d05050

• Fix to handle CFLAGS, CPPFLAGS and C_EXTRA_FLAGS.
• Added generation of configuration options in wolfmqtt/options.h.
• Cleanup of the configure.ac to use AM_CFLAGS and remove AX_PTHREAD.

Also in your description did you mean CPPFLAGS?

Thanks,
David Garske, wolfSSL

[denravonska]

@dgarske Ooops, I did. I'll try it out in the morning.

[denravonska]

That seems to be working, thanks.