Re: Compiling libpq with VC6

Andreas Pflug wrote:
> Tom Lane wrote:
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> >
> >>Andreas Pflug wrote:
> >>
> >>>Not really. The backend will still use the reliable pg_ functions.
> >>>Frontends continue to use the libc functions, which are totally
> >>>sufficient in non-concurrent access situations.
> >
> >
> >>I would like to keep full Unix semantics for these functions even in
> >>libpq, if possible.
>
> > libpq doesn't use either rename or unlink AFAIK.  However, if we make
> > the patch be something involving #ifdef FRONTEND, then it will affect
> > other code that might want to use those.
> >
> > One thing that hasn't been real clear to me is why this only affects
> > fe-lobj.c, when we have many other files that include <io.h> after
> > including postgres.h.
>
> Quite simple: mingw includes do *not* conflict.
> Only a minority of tools is object to VC6 compilation, ultimately only
> libpq is needed.

True, only MSVC conflicted.  Maybe no one has compiled anything but
libpq using MSVC, particularly psql.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073