Re: Installing via pip under Win7 + virtualenv + VC++2008

On Sat, Jun 4, 2011 at 4:47 PM, Daniele Varrazzo
<daniele(dot)varrazzo(at)gmail(dot)com> wrote:

> 1) You use gcc to build python extension with prebuilt PG binaries

I have given a go at building psycopg with mingw. I've made a couple
of patches, one about dropping warnings, another to support Python 3
in autodetect_pg_config_path_windows(). Stephen, you may want to merge
it as it is in the area you are hacking on.

It works good enough, but as Jason says it builds a pyd depending on
the libpq.dll, which in turn depends on 4-5 dlls found in the
Postgres/bin directory. So the product still requires some care to be
deployed, but if the static lib is not installed by the postgres
package I guess there's little that can be done. An option would be to
copy all the dlls in the psycopg2 dir... would it be ugly?

Another problem I've had was caused by the problem described in
http://bugs.python.org/issue3308 due to an old msvcr90.lib I had in my
build system. With the buggy lib it wasn't possible to build for
Python 2.6 and 3.1.

Both the missing localtime in msvcr90.lib and the dll dependencies
have been easy to debug using the tool at
http://www.dependencywalker.com/ - without it the error messages are
painfully unhelpful.

Apart from the patches already committed in my devel, I think I'm fine
with the scenario mingw/win. I will see to add a web page about the
tools used.

-- Daniele