From: | Greg Landrum <greg(dot)landrum(at)gmail(dot)com> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: writing backend extensions using Visual Studio |
Date: | 2005-03-29 15:05:12 |
Message-ID: | 60825b0f0503290705146a3b52@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
On Tue, 29 Mar 2005 15:54:54 +0100, Dave Page <dpage(at)vale-housing(dot)co(dot)uk> wrote:
>
>
> > -----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!
For what it's worth, if I zip up the $PGSRC/include directory, the
archive is about 500K. That seems like a pretty minimal bump to the
17MB installer.
-greg
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-03-29 15:07:43 | Re: writing backend extensions using Visual Studio |
Previous Message | Magnus Hagander | 2005-03-29 15:05:00 | Re: writing backend extensions using Visual Studio |