Re: doxygen @short directive in comments

[Federico Montesino Pouzols]

On Wed, Jan 08, 2003 at 06:05:42PM +0200, Albert Strasheim wrote:
> 
> Here's a more general question: how is any autoconf/automake project 
> supposed to use the config.h file?
> 
> It seems to be as if the right way to go about things is to have 
> autoconf generate a config.h header which you include with your 
> installed headers (which seems to be what Common C++ does), and always 
> include if you need configuration info in your other headers.
> 

        Yes, that way, you have in config.h all the information that
the autools guessed for your system when you run configure.

> BTW, with autoconf 2.57, reconfig prints the following warning message 
> when you generate the files for the build system:
> 
> address@hidden:~/work/commoncpp2> ./reconfig
> Putting files in AC_CONFIG_AUX_DIR, `config'.
> WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
> WARNING: and `config.h.top', to define templates for `config.h.in'
> WARNING: is deprecated and discouraged.
> 
> WARNING: Using the third argument of `AC_DEFINE' and
> WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
> WARNING: `acconfig.h':
> 
> WARNING:   AC_DEFINE([NEED_MAIN], 1,
> WARNING:             [Define if a function `main' is needed.])
> 
> WARNING: More sophisticated templates can also be produced, see the
> WARNING: documentation.
> 

        The autotools files of cc++ use the syntax of old autotools
releases, which now is somewhat deprecated. However, as long as
backwards compatibility is kept in the autotools, this has the
advantage that we do not impose the requirement of having an updated
autotools suite in order to use the CVS version of cc++.

        Perhaps, we should update these files for 1.1, in particular
to avoid the use of acconfig.h.

> Cheers,
> 
> Albert
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp