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 E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDD1@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>)
List pgsql-hackers-win32

> -----Original Message-----
> From: Greg Landrum [mailto:greg.landrum@gmail.com]
> Sent: 29 March 2005 15:52
> To: Dave Page; pgsql-hackers-win32@postgresql.org
> Subject: Re: [pgsql-hackers-win32] writing backend extensions
> using Visual Studio
>
> Maybe a good solution to this is to add an extra option in the
> installer's development category to include header files for backend
> development?  That way most people (even those who do front-end
> development) don't have to deal with having that whole include tree
> installed, but those who want to do backend work can still get
> everything required without doing their own build/source installation.

Yeah, that's quite straightforward to do - although, there are that many
files that it would probably be easier to do a wildcard include anyway
unless it's a fairly well defined set that's required. In reality I
doubt most people would care whats in the include/ directory anyway -
it's the download size I'm more worried about!

Regards, Dave.

pgsql-hackers-win32 by date:

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