cppunit-devel

[Cppunit-devel] 2. configure.in queries

[Steve M. R. <ste...@vi...>]

Would anyone object to the following two changes to configure.in?

1. remove AM_DISABLE_STATIC

Rationale: libtool-based packages typically build both shared and
static libs by default (configure has --disable-static &
--disable-shared flags for the installer to customize to her taste).
The principle of "least surprise" dictates that we stick to that
unless there is a compelling reason for NOT building static
libcppunit.a.  Is there such a reason?

2. bump the version string to 1.5.6

Rationale: to differentiate CVS cppunit from the last released
version.  


-Steve



-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants

[Cppunit-devel] another configure.in change

[Steve M. R. <ste...@vi...>]

I just noticed another oddity in configure.in that violates
the principle of "least surprise".  I propose we do away
with the following:

AC_ARG_ENABLE(debug-mode,   
[  --enable-debug-mode     enable debugging mode],
  [
    CFLAGS="-D_DEBUG -g3 -Wall"
    CXXFLAGS="-D_DEBUG -g3 -Wall"
  ],[
    CFLAGS="-O2 "
    CXXFLAGS="-O2"
  ]) 

Rationale: besides surprising me that "-g" is omitted by default, it
is clearly wrong that --enable-debug-mode sets GCC-specific flags like
"-Wall".  The builder always has the option to set the flags themself,
so this difference is completely gratuitous.

-Steve


-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants