From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Library names on Unix |
Date: | 2006-01-03 08:41:22 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7ECD2@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Peter Eisentraut
> Sent: 02 January 2006 16:30
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] Library names on Unix
>
> Maybe one could discuss whether the -a or the -w
> variant provides the
> most faithful backward compatibility, but I tend to think
> that users are
> perhaps better served if they are forced to stop and decide
> with which
> variant they want to proceed. Ideas?
Agreed. That was the approach I took on Windows - rename 'em both and
force users to decide which one to use themselves.
BTW, if you're hacking the build system, would you mind adding a
--with-pgsql= option to configure? The current code you wrote relies on
pg_config being in the path which it certainly isn't on many of my
systems. I don't object to that being the default behaviour, but it
would be handy to override it when necessary.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-01-03 08:45:17 | Re: odbc.postgresql.org misdirected |
Previous Message | Dave Page | 2006-01-03 08:35:16 | Re: odbc.postgresql.org misdirected |