Oops--forgot to send this to the list. On Thu, November 24, 2005 08:17, Tom Bruno wrote:
> I have postgresql built static now, libpqxx won't configure because it > cannot find libpq.dll I'm pretty sure a regular postgres build should produce a libpq.dll *and* a libpq.lib (or libpq.a). But apparently the autotools insist on the dll and that's not very helpful. I looked through the "./configure --help" output but didn't find anything that looked very helpful. This is not libpqxx-specific, so it may be worthwhile to search the Web for other cases of people wanting to get autotools-generated configure scripts to use static instead of shared libraries. > I did the following step before running configure: > export LDFAGS="-lws2_32 /c/mingw/local/lib/libpq.a" That won't work. It might, if the configure script didn't insist on finding the dll, produce a working library with all definitions it needed--but it would probably still *think* it needed a libpq.dll even though all its symbols would be resolved. > I tried --disable-shared=libpq and it says "error: invalid feature name > shared=libpq" Maybe that's something we can implement. These tools are pretty complex, so I'll need some help from a helpful autotools guru! > So i need to figure out how to make libpqxx build static linked to libpq. > Any idea's? As a last resort, you could probably configure with the libpq.dll visible to the configure script, but LDFLAGS set the way you tried earlier. Then move libpq.dll out of the way (just to be sure) and edit the Makefile by hand. You'd certainly have to look for any options -lpq and remove them; probably some others as well. Jeroen _______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
