Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: writing backend extensions using Visual Studio


  • 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: Tue, 29 Mar 2005 15:54:54 +0100
  • Message-id: <E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDD1(at)ratbert(dot)vale-housing(dot)co(dot)uk>

 

> -----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.



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group