Where does the -DNDEBUG normally come from?

Question

Our build system has somehow changed such that optimized builds are no longer getting the -DNDEBUG added to the compile line. I searched our makefiles and don't find this.

So the question is, where does -DNDEBUG originate for most people and how might that have changed? Before we did have -DNDEBUG and I don't think this was removed from any of our makefiles.

Thanks.

-William

Solution 1

Since the compiler can't decide on its own when to add the NDEBUG define and when not to, the flag is always set by either the makefile or project file (depending on your build system).

Solution 2

It is really difficult to answer this since you didn't specify the build system you are using. If you're using autoconf, then either the user is expected to put -DNDEBUG in CPPFLAGS manually (or perhaps you were setting it from a CONFIG_SITE file that has changed), or the configure.ac might set up a custom variable for setting NDEBUG, or configure.ac may invoke AC_HEADER_ASSERT, in which case adding --disable-assert to the invocation of configure will define NDEBUG in config.h. There are lots of ways it can happen.

Solution 3

In my experience, -DNDEBUG has been passed manually, i.e. the makefiles have been written in such a way that the flag is passed when building in release mode.

Comments

[Anycorn]

may want to check your configure or configure.ac if you are using GNU build tools, i.e. autoconf and friends

[WilliamKF]

I'm not using config, just GNU makefiles.

[peschü]

If I need to choose between doing AC_DEFINE(NDEBUG,[],[]) and CPPFLAGS="$CPPFLAGS -DNDEBUG" in configure.ac, what should I do? Is it a disadvantage to have #define NDEBUG in config.h? If I do both I get lots of "NDEBUG duplicate definition" warnings that I would like to avoid.

[William Pursell]

If you are maintaining the autoconf metadata files, you should use AC_HEADER_ASSERT and let the user specify --disable-assert at configure time. The user is responsible for ensuring that -DNDEBUG is passed to the compiler if they so desire. It is not appropriate to define NDEBUG by default; that's not the package maintainer's prerogative.

[peschü]

What if -DNDEBUG is not enabled by default but by an option --enable-release? Would this be appropriate? And how would I activate -DNDEBUG in that case?

[William Pursell]

Regarding --enable-release, please read stackoverflow.com/questions/4553735/…