Re: [Cppunit-devel] config.h proposal

[Bastiaan B. <bas...@li...>]

Baptiste Lepilleur wrote:

> > > In this scenario, if HAVE_CONFIG_H is defined we include <config.h> in
> > > <cppunit/Portability.h> ...
> >
> > If you are suggesting that an installed header has
> >
> > #if HAVE_CONFIG_H
> > #include <config.h>
> > #endif
> >
> > then I am completely against it.  I need to be able to use CppUnit
> > in other projects, some of which use autoconf and therefore define
> > HAVE_CONFIG_H.  The behaviour of CppUnit should not change based on
> > whether or not I use autoconf in my project.
>

It should change behaviour, but only detect potential problems, due to
differences between the CppUnit config and the application config. But as I
said the idea is broken, so please forget it.

>
>     I don't really see a need for HAVE_CONFIG_H:
>     If we don't detect VC++ 6.0, C++ builder..., then we default to
> <config.h>.
>     If needed, anoher project specific symbol such as CPPUNIT_HAVE_CONFIG_H
> could be used to force the use of config.h. This symbol would need to be
> defined in each user project.
>

When autconf builds it defines HAVE_CONFIG_H to indicate the availability of
<config.h>. We don't use this macro for CppUnit compilation.  Please forget
about it.

Bastiaan