Ok, re "building with the win32 configuration" ... that sounds like just the thing I should know about. All I've done
isdownloaded and installed the 1-click installer for Windows from
http://www.enterprisedb.com/products/pgdownload.do#windows... so while I'm sure it knows it's running on Win32, is
theresome other configuration change I should make for dev purposes to indicate that it's "the win32 configuration"? Or
does"building with the win32 configuration" refer to those who are building the server from source, or something?
Thanks
Kevin
-----Original Message-----
From: Craig Ringer [mailto:craig@postnewspapers.com.au]
Sent: 05 March 2010 04:02
To: Kevin Flanagan
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Visual Studio 2005, C-language function - avoiding hacks?
Kevin Flanagan wrote:
> the compiler
> complained about various missing include files, starting with
> ‘libintl.h’. Having read the post at
> http://archives.postgresql.org/pgsql-general/2009-03/msg00332.php I
> created an empty libint.h in an include dir
NFI why Pg for win32 doesn't bundle a copy of the libintl it was built
against. I should poke the EDB guys about it, actually.
> along with a bunch of other
> empty dummy files that were expected: netdb.h, pwd.h, netinet/in.h and
> arpa/inet.h.
Those I wouldn't expect to be included if you're building for win32.
Are you sure you're building with the win32 configuration?
> The code then compiles ok, but gives ‘inconsistent dll linkage’ on the
> line with PG_FUNCTION_INFO_V1 and the one with PG_MODULE_MAGIC.
This would suggest that the macros that insert appropriate
__declspec(dllimport) and __declspec(dllexport) attributes aren't being
triggered - so again, it makes me wonder if Pg knows it's building for
win32.
--
Craig Ringer