Re: Path to PostgreSQL portabiliy

From: Jan Wieck <janwieck(at)yahoo(dot)com>
To: Joel Burton <joel(at)joelburton(dot)com>
Cc: Paul Ramsey <pramsey(at)refractions(dot)net>, mlw <markw(at)mohawksoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Path to PostgreSQL portabiliy
Date: 2002-05-09 17:09:24
Message-ID: 200205091709.g49H9OW01742@saturn.janwieck.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joel Burton wrote:
> Certainly, we don't need all of cygwin (eg bison, gcc, perl, et al). We'd
> need the dll, sh, rm, and few other things. I'm not sure if it would need to
> be in the standard cygwin file structure; I know that you can reconfigure
> this when you use cygwin (I used to). In any event, instead of having to
> have a novice pick & guess which of >100 packages they need, we could put
> together the 5 or 6 they need.

Oh, BTW, had anyone luck with loading of user defined C
functions or the PL handlers under CygWin? I remember having
had trouble with that. When the C function uses global
variables in the backend, things get a bit messy.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2002-05-09 17:24:03 Re: How much work is a native Windows application?
Previous Message Jan Wieck 2002-05-09 17:05:58 Re: Path to PostgreSQL portabiliy