Re: compiler warnings in ODBC - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: compiler warnings in ODBC
Date
Msg-id 3BE51B5D.5ED0FA62@tm.ee
Whole thread Raw
In response to Re: compiler warnings in ODBC  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: compiler warnings in ODBC
Re: compiler warnings in ODBC
List pgsql-hackers
Peter Eisentraut wrote:
> 
> Hiroshi Inoue writes:
> 
> > ISTM neither you nor Philip Warner would use the driver
> > in reality. I'm suspicious if --enable-odbc has a meaning
> > without the environment. We could have 3 kind of ODBC
> > drivers under unix now.
> > 1) stand-alone driver made with --enable-odbc.
> > 2) iODBC driver made with --with-iodbc.
> > 3) unixODBC driver made with --with-unixODBC.
> >
> > Because they are exclusive, it seems to have little meaning
> > to make 1) in advance. In addition it seems misleading if
> > people would regard 1) as the standard PG driver.
> 
> It probably doesn't make the greatest possible sense, but it's backward
> compatible and consistent with typical configure options.
> 
> Btw., to get the iODBC driver, you need both options --with-iodbc and
> --enable-odbc.  If you only use the former, you get nothing at all.
> Again, this could conceivably be done differently.

--enable-odbc=standalone
--enable-odbc=iODBC
--enable-odbc=unixODBC

could be the logical way to do it ?

----------------
Hannu


pgsql-hackers by date:

Previous
From: "Dave Cramer"
Date:
Subject: Re: Licensing issues including another projects source code into the jdbc driver
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql/ oc/src/sgml/client-auth.sgml oc/src/sgm ...