| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | darrenk(at)insightdist(dot)com (Darren King) |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Removing PORTNAME from libpq/Makefile |
| Date: | 1998-04-23 16:11:29 |
| Message-ID: | 22422.893347889@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
darrenk(at)insightdist(dot)com (Darren King) writes:
> So to summarize a little, in libpq/Makefile, make a libpq.o and then
> in Makefile.$(PORTNAME), make the shared libpq. Seem reasonable?
Close, but no cigar. What happens when we have two, or three, or ten
shared libs to make?
The right thing to do is to have makefiles/Makefile.PLATFORM contain
some sort of generic shared-library-making rule that can then be
applied in libpq/Makefile and any other module makefile that wants
to produce a shared library.
I'm a little out of practice on generic rules in gmakefiles, but
since we already assume that gmake is being used, it shouldn't be
too hard to do it this way.
I'll be glad to help with the HPUX version of the rule.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 1998-04-23 16:26:36 | Re: [INTERFACES] retrieving varchar size |
| Previous Message | Tom Lane | 1998-04-23 15:58:39 | HP-UX porting strategy (moved from PATCHES) |