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

Re: 8.4 TODO item: make src/port support libpq and ecpg directly

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: 8.4 TODO item: make src/port support libpq and ecpg directly
Date: 2007-10-04 22:16:13
Message-ID: 4705662D.10501@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> This business with having libpq and ecpg pull in src/port modules
> manually is getting unmaintainable.  I wonder whether we could persuade
> src/port to generate three versions of libpgport.a --- backend,
> frontend, and frontend-shlib-ready --- and then just -l the appropriate
> one in libpq and ecpg.  This'd waste a few cycles building modules that
> would never be used, but on the other hand we'd buy some of that back
> by not building the same object files three or four times.
>
>
>   
Works for me.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Islam HegazyDate: 2007-10-04 23:02:27
Subject: code documentation
Previous:From: Tom LaneDate: 2007-10-04 21:40:48
Subject: Re: ecpg build now breaks mingw

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