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

Re: Extracting client code

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Jon Earle <jepg(at)kronos(dot)honk(dot)org>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Extracting client code
Date: 2006-09-28 16:52:14
Message-ID: 200609281652.k8SGqEi00631@momjian.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
Jon Earle wrote:
> Tom Lane wrote:
> > "Jon Earle" <jepg(at)kronos(dot)honk(dot)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
> 
> I noticed the makefile in the libpq dir made symlinks to a handful of .c
> files in src/port and references one .h.  Aside from those, which I could
> simply copy into the libpq dir, is there anything inside the libpq dir that
> is changed by the configure script that I can't manage myself?  Honestly,

Yes, include/pg_config.h is used by libpq, for example.

-- 
  Bruce Momjian   bruce(at)momjian(dot)us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-interfaces by date

Next:From: erkan kolemenDate: 2006-09-28 18:33:09
Subject: Re: PGExec returns error without any comment
Previous:From: Jon EarleDate: 2006-09-28 16:49:30
Subject: Re: Extracting client code

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group