From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Greg Landrum" <greg(dot)landrum(at)gmail(dot)com>, <pgsql-hackers-win32(at)postgresql(dot)org> |
Subject: | Re: writing backend extensions using Visual Studio |
Date: | 2005-03-29 14:54:54 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDD1@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
> -----Original Message-----
> From: Greg Landrum [mailto:greg(dot)landrum(at)gmail(dot)com]
> Sent: 29 March 2005 15:52
> To: Dave Page; pgsql-hackers-win32(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2005-03-29 15:05:00 | Re: writing backend extensions using Visual Studio |
Previous Message | Greg Landrum | 2005-03-29 14:51:48 | Re: writing backend extensions using Visual Studio |