current tip does not honor build_ext -I -L flags

[GoogleCodeExporter]

To build pyodbc against a custom odbc library, you must either do:

    export CFLAGS='-I/path/to/custom/include -L/path/to/custom/lib'

or use build_ext flags:

    python setup.py build_ext -I/path/to/custom/include -L/path/to/custom/lib

as of the latest tip, the latter method is impossible because setup.py is 
calling a "sub" setup for the "pyodbcconf" utility, which it builds 
unconditionally against the wrong libraries.   I'd reconsider a build arch like 
this as it's highly complicated for the build to depend on another native 
library build *within* it just to configure.

Original issue reported on code.google.com by zzz...@gmail.com on 15 Oct 2011 at 11:03

[GoogleCodeExporter]

Good point.  However, I'd like to keep pyodbcconf so I can use the size of 
wchar, sqlwchar, and Py_UNICODE with the preprocessor.  There are 3 different 
unicode types now and keeping them straight is a pain.

I will have to make sure that all parameters / configurations are passed to it.

Original comment by mkleehammer on 16 Oct 2011 at 12:34

• Changed state: Investigating

[GoogleCodeExporter]

Removed pyodbcconf in 3.0.1

Original comment by mkleehammer on 3 Nov 2011 at 1:47

• Changed state: Complete