pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jon Earle <jepg@kronos.honk.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Extracting client code
Date: Thu, 28 Sep 2006 10:55:11 -0400
Message-ID: <25730.1159455311@sss.pgh.pa.us> (raw)
In-Reply-To: <4347.142.46.208.244.1159452491.squirrel@kronos.honk.org>
References: <4347.142.46.208.244.1159452491.squirrel@kronos.honk.org>

"Jon Earle" <jepg@kronos.honk.org> writes:
> Can I just take the src/interface/libpq dir
> contents, parachute them into the same dir as my app, then just compile it
> all together (after making the appropriate changes to my own app, of course)?

No.  At minimum you're going to need the configure script and src/port/
as well.  My inclination would just be to ship the unmodified tarball
and do

	unpack tarball
	cd top-dir
	configure ...
	cd src/interfaces/libpq
	make
	make install

Obviously you could strip large parts of the tarball out, but then you'd
have to redo that work every time we update.

Also keep in mind the possibility that libpq is already installed on the
machine you're on.

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <25730.1159455311@sss.pgh.pa.us>
Permalink:  ../25730.1159455311@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/25730.1159455311@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jepg@kronos.honk.org
  Subject: Re: Extracting client code
  In-Reply-To: <25730.1159455311@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox