Re: writing backend extensions using Visual Studio - Mailing list pgsql-hackers-win32

From Dave Page
Subject Re: writing backend extensions using Visual Studio
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDC2@ratbert.vale-housing.co.uk
Whole thread Raw
In response to writing backend extensions using Visual Studio  (Greg Landrum <greg.landrum@gmail.com>)
Responses Re: writing backend extensions using Visual Studio  (Greg Landrum <greg.landrum@gmail.com>)
Re: writing backend extensions using Visual Studio  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers-win32

> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew@dunslane.net]
> Sent: 29 March 2005 12:34
> To: Dave Page
> Cc: greg.landrum@gmail.com; pgsql-hackers-win32@postgresql.org
> Subject: Re: [pgsql-hackers-win32] writing backend extensions
> using Visual Studio
>
>
> Don't you need the (fairly large) tree that is normally rooted at
> include/postgresql/server? This will contain things like funcapi.h and
> fmgr.h.

Yeah - these used to be installed by 'make install-all-headers' iirc,
however that has gone now. I can't see anything in /INSTALL or the docs
on what to use instead other than the source tree (which doesn't ship
with pgInstaller of course).

So, a question to anyone who knows, do we really need to ship *all*
headers with the installer, or is there a useful subset?

Regards, Dave

pgsql-hackers-win32 by date:

Previous
From: "Andrew Dunstan"
Date:
Subject: Re: writing backend extensions using Visual Studio
Next
From: Greg Landrum
Date:
Subject: Re: writing backend extensions using Visual Studio