Re: autoconf issue

[David Durham]

Marcelo Dalmas wrote:

> The header defined by AM_CONFIG_HEADER should be included only in source
> files or in internal header files...
>
> On Thu, 7 Mar 2002, David Durham wrote:
>
> > Hey, I realized something while having my package autoconfiscated.
> > CommonC++ has two macros called, VERSION and PACKAGE created which are
> > the default names used by autotools, but any other package also using
> > autotools will create these by default.  Now, it is our reponsibility to
> > change ours from VERSION and PACKAGE to SOMETHING_VERSION and
> > SOMETHING_PACKAGE, shouldn't CommonC++ do it also?
> >
> > Am I confused about this?  I do know that right now our VERSION and
> > PACKAGE could be getting confused when include CommonC++ header files.
> >
> > -- Davy
Okay.. I sent your message to my autoconfiscator guy and here's what he 
said.... (BTW- our package's name is 'ReZound')

"...

>> The header defined by AM_CONFIG_HEADER should be included only in
>source
>> files or in internal header files...

  Well my question is whose AM_CONFIG_HEADER ? AM_CONFIG_HEADER is what 
defines PACKAGE and VERSION, on both ReZound and commonc++. But we 
should be able to use that anywhere we want in our own package.
  It seems to me that he's saying that cc++/config.h shouldn't be 
included in our files, but it's my understanding that all the cc++ 
headers include it.  But maybe he doesn't realize that it's being 
included through the use of any commonc++ header file.
...
Anthony

..."

So.... if you look in commonc++'s headers, most all of them contain  ... 
#include <cc++/config.h> ...   So everyone is including it who is using 
commonc++... And this is fine assuming that the contents of that 
config.h won't terribly conflict with other autoconfiscated packages 
also using an AM_CONFIG_HEADER file.  

The conflict in our case is the define of PACKAGE and VERSION....

And any other package using commonc++ should have this problem unless 
they've also prefixed something to be beginning of these two identifiers 
(which I believe every autoconf-ed package should be doing....)  
Now I'm brand new to acually developing with autotools so I could be 
missing something... not seeing something correctly...

-- Davy