2010-01-15 10:19:10 +01:00
|
|
|
#-------------------------------------------------------------------------
|
|
|
|
#
|
|
|
|
# Makefile--
|
2010-01-20 10:16:24 +01:00
|
|
|
# Makefile for src/backend/replication/libpqwalreceiver
|
2010-01-15 10:19:10 +01:00
|
|
|
#
|
|
|
|
# IDENTIFICATION
|
2010-09-20 22:08:53 +02:00
|
|
|
# src/backend/replication/libpqwalreceiver/Makefile
|
2010-01-15 10:19:10 +01:00
|
|
|
#
|
|
|
|
#-------------------------------------------------------------------------
|
|
|
|
|
2010-01-20 21:34:51 +01:00
|
|
|
subdir = src/backend/replication/libpqwalreceiver
|
2010-01-15 10:19:10 +01:00
|
|
|
top_builddir = ../../../..
|
|
|
|
include $(top_builddir)/src/Makefile.global
|
|
|
|
|
2010-01-20 10:16:24 +01:00
|
|
|
override CPPFLAGS := -I$(srcdir) -I$(libpq_srcdir) $(CPPFLAGS)
|
2010-01-15 21:45:42 +01:00
|
|
|
|
2019-11-05 23:41:07 +01:00
|
|
|
OBJS = \
|
|
|
|
$(WIN32RES) \
|
|
|
|
libpqwalreceiver.o
|
Prevent accidental linking of system-supplied copies of libpq.so etc.
We were being careless in some places about the order of -L switches in
link command lines, such that -L switches referring to external directories
could come before those referring to directories within the build tree.
This made it possible to accidentally link a system-supplied library, for
example /usr/lib/libpq.so, in place of the one built in the build tree.
Hilarity ensued, the more so the older the system-supplied library is.
To fix, break LDFLAGS into two parts, a sub-variable LDFLAGS_INTERNAL
and the main LDFLAGS variable, both of which are "recursively expanded"
so that they can be incrementally adjusted by different makefiles.
Establish a policy that -L switches for directories in the build tree
must always be added to LDFLAGS_INTERNAL, while -L switches for external
directories must always be added to LDFLAGS. This is sufficient to
ensure a safe search order. For simplicity, we typically also put -l
switches for the respective libraries into those same variables.
(Traditional make usage would have us put -l switches into LIBS, but
cleaning that up is a project for another day, as there's no clear
need for it.)
This turns out to also require separating SHLIB_LINK into two variables,
SHLIB_LINK and SHLIB_LINK_INTERNAL, with a similar rule about which
switches go into which variable. And likewise for PG_LIBS.
Although this change might appear to affect external users of pgxs.mk,
I think it doesn't; they shouldn't have any need to touch the _INTERNAL
variables.
In passing, tweak src/common/Makefile so that the value of CPPFLAGS
recorded in pg_config lacks "-DFRONTEND" and the recorded value of
LDFLAGS lacks "-L../../../src/common". Both of those things are
mistakes, apparently introduced during prior code rearrangements,
as old versions of pg_config don't print them. In general we don't
want anything that's specific to the src/common subdirectory to
appear in those outputs.
This is certainly a bug fix, but in view of the lack of field
complaints, I'm unsure whether it's worth the risk of back-patching.
In any case it seems wise to see what the buildfarm makes of it first.
Discussion: https://postgr.es/m/25214.1522604295@sss.pgh.pa.us
2018-04-03 22:26:05 +02:00
|
|
|
SHLIB_LINK_INTERNAL = $(libpq)
|
|
|
|
SHLIB_LINK = $(filter -lintl, $(LIBS))
|
2010-11-12 21:15:16 +01:00
|
|
|
SHLIB_PREREQS = submake-libpq
|
2014-07-14 20:07:52 +02:00
|
|
|
PGFILEDESC = "libpqwalreceiver - receive WAL during streaming replication"
|
2010-01-20 10:16:24 +01:00
|
|
|
NAME = libpqwalreceiver
|
2010-01-15 10:19:10 +01:00
|
|
|
|
2010-11-12 21:15:16 +01:00
|
|
|
all: all-shared-lib
|
2010-01-15 10:19:10 +01:00
|
|
|
|
|
|
|
include $(top_srcdir)/src/Makefile.shlib
|
|
|
|
|
|
|
|
install: all installdirs install-lib
|
|
|
|
|
|
|
|
installdirs: installdirs-lib
|
|
|
|
|
|
|
|
uninstall: uninstall-lib
|
|
|
|
|
|
|
|
clean distclean maintainer-clean: clean-lib
|
|
|
|
rm -f $(OBJS)
|