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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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. +
From | Date | Subject | |
---|---|---|---|
Next Message | erkan kolemen | 2006-09-28 18:33:09 | Re: PGExec returns error without any comment |
Previous Message | Jon Earle | 2006-09-28 16:49:30 | Re: Extracting client code |