Re: Linking against static libpq using Visual C++

Thanks for your answer. I was indeed using the static libpq version from
the installer.
I tried to compile my own one with Visual Studio 2010, but this caused a
lot of problems due to the fact that Visual Studio 2010 has changed the
manifest tool.
So I built a static version using Visual C++ 2008, which worked without
problems.
However, when building my application with Visual C++ 2008, the
following errors are lamented:

1>libpq.lib(fe-connect.obj) : error LNK2019: Unresolved external
reference "__imp__WSAIoctl(at)36" in Funktion "_setKeepalivesWin32".
1>libpq.lib(ip.obj) : error LNK2001: Unvresolved external symbol
"__imp__WSAIoctl(at)36".
1>libpq.lib(fe-connect.obj) : error LNK2019: Unresolved external
reference "__imp__DeleteSecurityContext(at)4" in Funktion "_closePGconn".
1>libpq.lib(fe-connect.obj) : error LNK2019: Unresolved external
reference "__imp__FreeCredentialsHandle(at)4" in Funktion "_closePGconn".
1>libpq.lib(ip.obj) : error LNK2019: Unresolved external reference
"__imp__WSASocketA(at)24" in Funktion "_pg_foreach_ifaddr".
1>libpq.lib(fe-auth.obj) : error LNK2019: Unresolved external reference
"_FreeContextBuffer(at)4" in Funktion "_pg_SSPI_continue".
1>libpq.lib(fe-auth.obj) : error LNK2019: Unresolved external reference
"_InitializeSecurityContextA(at)48" in Funktion "_pg_SSPI_continue".
1>libpq.lib(fe-auth.obj) : error LNK2019: Unresolved external reference
"_AcquireCredentialsHandleA(at)36" in Funktion "_pg_SSPI_startup".
1>C:\Users\Julia\Desktop\db_con\Debug\db_con.exe : fatal error LNK1120:
7 Unresolved external references.

Which libraries are missing now?

Am Feb 27, 2011 at 16:18, Magnus Hagander wrote:
> Did you build your own static version of libpq, or use the one that
> comes with the installer? If the latter, then it's probably that it's
> the wrong version of visual studio.
>
> Those imports are from the Visual C runtimes, so that's what you're
> missing for those - or using different versions.