Re: writing backend extensions using Visual Studio

"Dave Page" <[email protected]> Tue, 29 Mar 2005 16:45:29 +0100
Newsgroups gmane.comp.db.postgresql.devel.win32
Message-ID <E7F85A1B5FF8D44C8A1AF6885BC9A0E472BDD7@ratbert.vale-housing.co.uk>
 

> -----Original Message-----
> From: Tom Lane [mailto:[email protected]] 
> Sent: 29 March 2005 16:22
> To: Dave Page
> Cc: Andrew Dunstan; [email protected]; 
> [email protected]
> 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.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match