Re: Visual Studio 2005, C-language function - avoiding hacks?

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Flanagan <kevin-f(at)linkprior(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Visual Studio 2005, C-language function - avoiding hacks?
Date: 2010-03-09 07:55:09
Message-ID: 20100309165509.99D1.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> >> The existing mechanism
> >> works (as demonstrated by the fact that the contrib modules work on
> >> Windows).
> >
> > Did we use non-standard tools except msvc in the build framework
> > for core code? And what should I do for an external project?
>
> Yes, we use mingw.

Hmmm, it means the existing mechanism can only work on limited environments.
Should we make the code to be more portable for standard developers?

Third party developer might not build the postgres server,
but they would want to build their extension modules without mingw.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-03-09 08:00:21 Re: Visual Studio 2005, C-language function - avoiding hacks?
Previous Message Takahiro Itagaki 2010-03-09 07:47:21 Re: lock mode for ControlFileLock which pg_start_backup uses