Jason Tishler writes:
> Peter,
>
> On Thu, Apr 05, 2001 at 11:26:50PM +0200, Peter Eisentraut wrote:
> > Jason Tishler writes:
> >
> > > include/lib
> > > include/libpq
> >
> > What do you put into these two?
>
> $ find lib libpq++
> lib
> lib/dllist.h
> libpq++
> libpq++/pgconnection.h
> libpq++/pgcursordb.h
> libpq++/pgdatabase.h
> libpq++/pglobject.h
> libpq++/pgtransdb.h
I see, my fault. I thought the libpq was for the client side library, but
it's of course the backend's directory. Everything's great.
>
> > It's not necessarily a good idea to
> > divert from the standard layout under include because people might start
> > relying on `pg_config --includedir` to configure their packages. But if
> > there is some standard that requires you to do this...
>
> My intention was *not* to deviate from the standard PostgreSQL layout.
> I got the previously mentioned directory structure by just configuring
> as follows:
>
> configure --prefix=/usr/pgsql --with-CXX
>
> Did I do something wrong? How should I configure?
This is good, but before long users will pester you for stuff like
--enable-locale, --enable-multibyte, --with-perl, etc. ;-)
I don't know about the Cygwin file system conventions, but do people have
to alter their PATH and MANPATH (and LD_LIBRARY_PATH?) setting for each
new package they install? No shared installation locations?
--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
