Make libpqxx library setup easy for Windows developers.

[sourcecode84@…]

For developers who are inexperienced, or have problems building the libpqxx library, this website should offer a direct package download for windows developers that includes ready to use compiled DLL's, libraries and header files ready to be used in Visual C++, Metrowerks Codewarrior C++, Borland C++ or any of the other popular Windows compilers. This is the way to make libpqxx more accessible and attractive for developers looking for alternatives to Micro$osft SQL Server 2005, etc.

[jtv]

Packaging and providing binaries for specific systems is properly the job of the package maintainers for those particular systems. What is provided on this site is the "upstream" package, and we don't want to use up space on this server uploading binaries for dozens of platform/compiler combinations.

Moreover, people can expect the upstream package to be up-to-date. I don't have access to a Windows system, let alone any of the compilers mentioned here. Even if I did, I'm not sure the platform supports automation of simple tasks to the extent required to keep those binary packages current with the releases. So the way things stand, any Windows package would run hopelessly behind.

If any Windows user is going to step forward and maintain libpqxx packages for Windows, that would be very nice. We can add a link to the PackageMaintainers page.

[anonymous]

Oh, it's been a paink in the ass to build it...

[jtv]

We need volunteers for this! Is there a Windows user out there who can test and maintain Windows versions?

[fernando.a.gomez.f@…]

Building this stuff is a damn PITA. If I can ever compile it, I'll be glad to help you on this.

[fernando.a.gomez.f@…]

Finally I made it! So tell me, how can I help?

[fernando.a.gomez.f@…]

Finally I made it! So tell me, how can I help?

[jtv]

I think two things are needed:

1. A solid review of win32/INSTALL.txt. It really needs someone to go through this as a whole and not just fix mistakes, but also reorder or reword things where it's not clear.
2. Ways to automate as much of the procedure as possible. Since I'm not a Windows I can't judge how much that would be.

[kirit]

Ok, I'm doing some work on this for version 3 so I'll assign it to myself.

[ccff@…]

I think with the new version it is not so actual anymore. I remember writing a solution in the bugtraq here for building 2.69 on msvc8/x86 with changing sources. I even learnt something about vc ;-)) When you need people to test building it on msvc8 on x64/x86 then contact me. I had no problems at all with 3.0 btw.

[guang.du@…]

For Windows/Visual? Studio 2008 I'm using, it turns out to be the make file problem in win32/vc-test.mak background is my compilation of library with the INSTALL.TXT works well, but the test could not compile with quite a lot of errors there. The problem turns out to be using incorrect or missing library in the vc-test.mak

Solution would be adding manually the corresponding library during linking - that is, libpqxx_staticD.lib for static debug compilation, but not libpqxx.lib for everything.

Hope this helps. Wolfee