From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_config.h.win32 |
Date: | 2001-11-23 02:38:43 |
Message-ID: | 3BFDB6B3.4C92A6D1@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > It's pretty painful and risky to
> > change pg_config.h.win32 and the original pg_config.h.
> > How about including pg_config.h.win32 in pg_config.h e.g.
>
> What? I thought pg_config.h.win32 was a substitute pg_config.h
> to use for native-windows builds (where you can't run autoconf).
> Under cygwin I think you should just run configure and expect it
> to produce a correct pg_config.h by itself. If it doesn't, we
> need to fix the configure script.
Must I double the source tree for cygwin and native
Windows ? I'm using the common source tree for ODBC
and there's no problem for compilation. It seems
pretty absurd to have the whole source tree only
for native-windows clients but it's pretty annoying
to download only necessary files.
regards,
Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2001-11-23 02:48:28 | Re: pg_config.h.win32 |
Previous Message | Tom Lane | 2001-11-23 02:38:04 | Re: pg_config.h.win32 |