PostgreSQL：在Windows 8 64bit上编译C函数

Question

I'm learning how to compile a C trigger to load on PostgreSQL

When compile the "trigf.c" (in the example at http://www.postgresql.org/docs/9.3/interactive/trigger-example.html ), I get some issue related to int64 error (ch header)

#ifdef HAVE_LONG_INT_64
/* Plain "long int" fits, use it */

#ifndef HAVE_INT64
typedef long int int64;
#endif
#ifndef HAVE_UINT64
typedef unsigned long int uint64;
#endif
#elif defined(HAVE_LONG_LONG_INT_64)
/* We have working support for "long long int", use that */

#ifndef HAVE_INT64
typedef long long int int64;
#endif
#ifndef HAVE_UINT64
typedef unsigned long long int uint64;
#endif
#else
/* neither HAVE_LONG_INT_64 nor HAVE_LONG_LONG_INT_64 */
#error must have a working 64-bit integer datatype
#endif

-> [Error] #error must have a working 64-bit integer datatype

I don't know how to solve that problem, because clearly that there is a working 64 bit integer datatype that I can use.

Edit: I installed pgsql from binary. The C compiler I used for compile the C function file is MinGW GCC 4.7.2. (Using the path of Dev-cpp mingw gcc).

The command line is : gcc -fpic -c "D:\\trigf.c"

At the first time, it showed an error that in ch: not found libintl.h (no such file or directory). Then I download the Lib Intl - 0.14.4 (library for native language support). The installation create a folder: C:\\Program Files (x86)\\GnuWin32. I edited the environment variable CPATH, added C:\\Program Files (x86)\\GnuWin32\\include folder, which contained libintl.h.

I ran the command again, and I met with the above error.

Answer 1

Update : It turns out not to be too hard to build extensions stand-alone with MSVC on Windows. I wrote a blog post detailing the process today .

---

The usual way to build extensions on Windows is to do it inside a working PostgreSQL build tree.

See these instructions on the PostgreSQL wiki .

You might be able to do it using MinGW and PGXS using a suitable Makefile instead.

Just trying to compile a standalone .c file is unlikely to work as there are a variety of paths and preprocessor definitions required.

It doesn't help that the current PostgreSQL packages don't include headers for public dependencies, which is really rather frustrating. You can safely compile without ENABLE_NLS defined even if the target PostgreSQL was built with ENABLE_NLS , though, and in this case libintl.h won't be required.