Skip site navigation (1) Skip section navigation (2)

Re: Compiling libpq with VC6

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>,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 20:27:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Tom Lane wrote:
> Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> >> 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.
> Hm.  Given that we now support a native Windows port, do we care about
> building libpq with VC6 anymore?  Why wouldn't you just use the library
> as built with mingw?
> If we were moving in the direction of making the whole project buildable
> with VC6, that would be one thing; but as far as I know that is
> explicitly not part of the plan.  So why should we continue to support a
> partially-baked port when we have a full port?

VC seems broken only in the very minor way of io.h.  I don't know of any
other issues.  Doesn't seem like enough of a reason to abandon the build

  Bruce Momjian                        |
  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

pgsql-patches by date

Next:From: Andreas PflugDate: 2004-08-18 20:43:56
Subject: PGPASSWORD and client tools
Previous:From: Andreas PflugDate: 2004-08-18 19:58:18
Subject: Re: Compiling libpq with VC6

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group