Re: Extracting client code
От | Bruce Momjian |
---|---|
Тема | Re: Extracting client code |
Дата | |
Msg-id | 200609281652.k8SGqEi00631@momjian.us обсуждение исходный текст |
Ответ на | Re: Extracting client code ("Jon Earle" <jepg@kronos.honk.org>) |
Список | pgsql-interfaces |
Jon Earle wrote: > Tom Lane wrote: > > "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 > > 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@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-interfaces по дате отправления: