Russ Allbery <[EMAIL PROTECTED]> writes:
> I'd be curious to hear some elaboration on this.
Basically, to avoid problems like the one mentioned. You have two
problems:
a. you might have to define HAVE_* to get an installed header-file to
compile.
b. the definitions might collide with autoconf-ed stuff that the
program using the library is defining.
> What's the preferred way to handle a package where various things in
> the package header files depend on things that are figured out by
> configure?
My take of this is that you have to generate a (installation-specific)
header-file. In other words, go from:
#ifdef HAVE_FOO_H
#include <foo.h>
#endif
to just:
#include <foo.h>
or nothing at all.
I've not found any other reasonable way of doing this. I also have
some code for this in case somebody is interested.
/assar
