Re: Compiling libpq with VC6

Tom Lane wrote:
> Andreas Pflug <pgadmin@pse-consulting.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
environment.

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