> -----Original Message-----
> From: Peter Eisentraut [mailto:[EMAIL PROTECTED]] 
> Sent: 01 October 2002 21:05
> To: Dave Page
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [HACKERS] psqlODBC *nix Makefile (new 7.3 open item?)
> 
> 
> Dave Page writes:
> 
> > > > majority of you!) knock up a makefile so the driver will build 
> > > > standalone on *nix systems please? There should be no
> > > dependencies on
> > > > any of the rest of the code - certainly there isn't for 
> the Win32 
> > > > build.
> > >
> > > I'm working something out.  I'll send it to you tomorrow.
> 
> Hah.  I tried to put something together based on Automake and 
> Libtool, but I must conclude that Libtool is just completely 
> utterly broken.  I also considered copying over 
> Makefile.shlib, but that would draw in too many auxiliary 
> files and create a different kind of mess.  So what I would 
> suggest right now as the course of action is to copy your 
> local psqlodbc subtree to its old location under interfaces/ 
> and try to hook things together that way.
> 
> Perhaps one of these days we should convert Makefile.shlib 
> into a shell script that we can deploy more easily to 
> different projects.

I have added README.unix to the psqlODBC CVS containing the following
text:

I assume the odbc options haven't been removed from the autoconf stuff?

Regards, Dave.

psqlODBC README for *nix Systems
================================

Since psqlODBC has be moved from the main PostgreSQL source tree, we
have yet
to create a new build system for the driver. Currently, in order to
build under
*nix systems, it is recommended that you copy the files in this
directory to
src/interfaces/odbc in your PostgreSQL source tree, then re-run
configure with
the required options from the top of the tree. The driver can then be
built
using make as per normal.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Reply via email to