[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to install "config.h"

From: Assar Westerlund
Subject: Re: How to install "config.h"
Date: 30 Oct 2000 03:07:50 +0100
User-agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.6

Robert Boehne <address@hidden> writes:
> I have a massive set of C++ libraries that use
> CVS libtool, autoconf and automake to build and install.
> Since users then need to have _all_ the header files
> they also need to have the configure generated config.h
> What is the "best" way to coerce Automake into installing
> config.h in $(prefix) ?

I must caution against installing config.h.  You will collide with the
potential same config.h and HAVE* et al defines that the application
using your header files has figured out for itself.

It's much preferable to make sure that the installed include-files do
not depend on the autoconf'd parameters in any way.  If you really
need to use the definitions that configure has figured out for you,
it's much better, I think, to partial-evaluate so that instead of:


#ifdef HAVE_FOO_H
#include <foo.h>

you make it unconditional (empty or just with the include).  This will
make that file machine-dependent, but you can most likely limit this
to one file and have all the other header files be shared.

And if you install config.h, it should be as PACKAGE-config.h.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]