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 E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDD7@ratbert.vale-housing.co.uk
Whole thread Raw
In response to writing backend extensions using Visual Studio  (Greg Landrum <greg.landrum@gmail.com>)
List pgsql-hackers-win32

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 29 March 2005 16:22
> To: Dave Page
> Cc: Andrew Dunstan; greg.landrum@gmail.com;
> pgsql-hackers-win32@postgresql.org
> Subject: Re: [pgsql-hackers-win32] writing backend extensions
> using Visual Studio
>
> > So, a question to anyone who knows, do we really need to ship *all*
> > headers with the installer, or is there a useful subset?
>
> The reason 'make install-all-headers' went away is that we
> made a policy
> decision to install *all* the headers. I don't think the Windows
> packaging should be second-guessing that.  It would be reasonable to
> have an option to install *none* of the headers, for people who aren't
> going to be doing any software development, but if you do install them
> please don't be selective about it.

Ahh, I see the problem - the build script is only pulling in files in
include/, not include/*/ etc. Will have to look at that.

Thanks Tom.

Ragrds, Dave.

pgsql-hackers-win32 by date:

Previous
From: Tom Lane
Date:
Subject: Re: writing backend extensions using Visual Studio
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] Enhancement: Remove NT/Interactive from Power Users Group