From: | "Cyril VELTER" <cyril(dot)velter(at)libertysurf(dot)fr> |
---|---|
To: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Path to PostgreSQL portabiliy |
Date: | 2002-05-09 18:00:03 |
Message-ID: | 00ee01c1f783$5b357110$6901a8c0@cvfixe |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: "Jan Wieck" <janwieck(at)yahoo(dot)com>
> 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.
I have a 7.1.3 install with cygwin and I'm using pl/pgsql and a custom
type (with accessor written in a C dll). It never cause me any problem.
My custom dll is not using global var in the backend though.
cyril
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 2002-05-09 18:02:02 | Re: pgaccess |
Previous Message | Jan Wieck | 2002-05-09 17:51:29 | Re: Issues tangential to win32 support |