dreid 01/07/07 19:48:54
Modified: . configure.in Log: Add an option to configure to add -pg if we're using gcc to add profiling information to the build. Given that we need to be concerned about performance this sort of useful addition seems like a good idea to me. Should we be leaving -O2 in the build if we're specifying -pg? Revision Changes Path 1.331 +8 -2 apr/configure.in Index: configure.in =================================================================== RCS file: /home/cvs/apr/configure.in,v retrieving revision 1.330 retrieving revision 1.331 diff -u -r1.330 -r1.331 --- configure.in 2001/07/07 07:17:32 1.330 +++ configure.in 2001/07/08 02:48:53 1.331 @@ -149,8 +149,14 @@ ])dnl AC_ARG_ENABLE(assert-memory,[ --enable-assert-memory Turn on asserts in the APR memory code], - [APR_ADDTO(NOTEST_CPPFLAGS,-DAPR_ASSERT_MEMORY) -]) + APR_ADDTO(NOTEST_CPPFLAGS,-DAPR_ASSERT_MEMORY) +)dnl + +AC_ARG_ENABLE(profile,[ --enable-profile Turn on profiling for the build (GCC)], + if test "$GCC" = "yes"; then + APR_ADDTO(CFLAGS, -pg) + fi +)dnl dnl # this is the place to put specific options for platform/compiler dnl # combinations
