From: | Ian Lance Taylor <ian(at)airs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Rename config.h to pg_config.h? |
Date: | 2001-08-13 18:59:11 |
Message-ID: | sipu9zu6ps.fsf@daffy.airs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Another bug report complaining of include file name conflicts came in
> just now. The only solution I can see is to rename config.h to
> something more project-specific. Should we do this, or keep ignoring
> the problem?
I would vote for renaming it. I've run into the problem of getting
the wrong config.h file. config.h is a fine name to use for a
standalone tool. It's not particularly good for a library, and
Postgres does have a library component.
FYI, in BFD (the library used for gdb and the GNU binutils) we jump
through hoops to to generate a bfd.h file which is properly configured
but does not include a config.h file--see, e.g., BFD_ARCH_SIZE and
BFD_HOST_64BIT_LONG in /usr/include/bfd.h on Linux.
Ian
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Ramsey | 2001-08-13 19:31:31 | PostGIS spatial extensions |
Previous Message | Tom Lane | 2001-08-13 18:56:33 | Re: Re: AW: Re: OID wraparound: summary and proposal |