[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Multiple configure-make cycles



Hi,

On Sat, Apr 27, 2002 at 11:06:59AM -0400, Joey Hess wrote:
> That sounds redundant, what's wrong with building once with -g, linking
> shared, stripping, calling that one package, and then linking w/o
> stripping for the -dbg package?

The configure.in has different -D defines for debugging, so you have to
compile twice, one with --enable-release, the other with --enable-debug.
FOX has internal tracing (FXTRACE) and asserts (FXASSERT) macros that
are enabled when DEBUG is defined, disabled otherwise.

Greetings, Bastian

[configure.in snippet]
dnl Debugging turned on
AC_MSG_CHECKING(for debugging)
AC_ARG_ENABLE(debug,[  --enable-debug          compile for debugging])
AC_MSG_RESULT([$enable_debug])
if test "x$enable_debug" = "xyes" ; then
CXXFLAGS="${CXXFLAGS} -g -DDEBUG"
fi

dnl Building for release
AC_MSG_CHECKING(for release build)
AC_ARG_ENABLE(release,[  --enable-release        compile for release])
AC_MSG_RESULT([$enable_release])
if test "x$enable_release" = "xyes" ; then
CXXFLAGS="${CXXFLAGS} -O2 -DNDEBUG"
if test "${GXX}" = "yes" ; then
CXXFLAGS="${CXXFLAGS} -Wuninitialized -ffast-math -finline-functions -fomit-frame-pointer -fexpensive-optimizations"
fi
fi

Attachment: pgpS6gcBy8jvl.pgp
Description: PGP signature


Reply to: