Re: Compiling libpq with VC6

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Subject: Re: Compiling libpq with VC6
Date: 2004-08-18 19:35:30
Message-ID: 200408181935.i7IJZUc27307@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Andreas Pflug wrote:
> Tom Lane wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-08-18 19:38:42 Re: Compiling libpq with VC6
Previous Message Andreas Pflug 2004-08-18 19:31:53 Re: Compiling libpq with VC6