Re: writing backend extensions using Visual Studio

Dave Page said:
>
>
>> -----Original Message-----
>> From: Greg Landrum [mailto:[email protected]]
>> Sent: 28 March 2005 23:31
>> To: Dave Page; [email protected]
>> Subject: Re: [pgsql-hackers-win32] writing backend extensions
>> using Visual Studio
>>
>> On Mon, 28 Mar 2005 22:05:58 +0100, Dave Page
>> <[email protected]> wrote:
>> >
>> > >
>> > > it seems that the development
>> > > files distributed with the win32 installer aren't
>> sufficient to the
>> > > task.
>> >
>> > They should be - what did we miss?
>>
>> Looking at a fresh installation, the libpostgres.a distributed with
>> pginstaller seems to match the one I built, but the header files
>> required for building backend apps are missing.  (These are the
>> "internal to Postgres" headers, to use the terminology of
>> postgres_ext.h)
>
> We install the following:
>
> $ ls c:/program\ files/postgresql/8.0/include
> ecpg_informix.h  libpq-fe.h          pgtypes_date.h
> pgtypes_timestamp.h
> ecpgerrno.h      pg_config.h         pgtypes_error.h     postgres_ext.h
> ecpglib.h        pg_config_manual.h  pgtypes_interval.h  sql3types.h
> ecpgtype.h       pg_config_os.h      pgtypes_numeric.h   sqlca.h
>
> Which is what is installed by PostgreSQL's build system. Do backend
> extensions need to be built in the source tree?
>

Don't you need the (fairly large) tree that is normally rooted at
include/postgresql/server? This will contain things like funcapi.h and
fmgr.h.
cheers

andrew



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