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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: 8.4 TODO item: make src/port support libpq and ecpg directly
Date: 2007-10-04 21:33:43
Message-ID: 21737.1191533623@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

			regards, tom lane

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-10-04 21:40:48
Subject: Re: ecpg build now breaks mingw
Previous:From: Alvaro HerreraDate: 2007-10-04 21:33:42
Subject: Re: First steps with 8.3 and autovacuum launcher

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