On 31/05/2016 08:10, Tsunakawa, Takayuki wrote:
From: Michael Meskes [mailto:mes...@postgresql.org]
Yes, but Windows users probably don't understand or know it. So, I
suggested explicitly describing the application binary compatibility
policy in the PostgreSQL manual. What do you think about it?
Couldn't you point your customer to the system documentation?
Personally I don't think standard system behavior should be documented for
each application relying on it but ymmv.
I couldn't find appropriate system documentation. Regarding Linux, I remember I saw some
HOWTO on tldp.org website which explains the concept of shared library soname, but it's
not very friendly for users who just want to know the application binary compatibility
policy of PostgreSQL. And I don't think there's suitable documentation on Windows. Even
if there is any, users will not be sure whether PostgreSQL follows those
platform-specific conventions. They may have doubts about it, because even the product
version "PostgreSQL x.y.z" causes misconception that x is the major version and
y is the minor one.
So, I suggested documenting the compatibility policy for clarification and user
friendliness as in the Oracle Database documentation below.
http://docs.oracle.com/database/121/UPGRD/app.htm#UPGRD12547
BTW, although this may be a separate topic, it may be better that we add the
major version in the library names like libpq5.dll and libecpg6.dll, so that
the application can fail to run with the incompatible versions of libpq and
libecpg. FYI:
https://en.wikipedia.org/wiki/Side-by-side_assembly
[Excerpt]
Microsoft Visual C++ 2005 and 2008 employ SxS with all C runtime libraries.
However, runtime libraries in Visual C++ 2010 no longer use this technology;
instead, they include the version number of a DLL in its file name, which means
that different versions of one DLL will technically be completely different
DLLs now.
Any comments on these? If there's no strong objection, I think I'll submit a
documentation patch in the future.
Regards
Takayuki Tsunakawa
Hi,
on cygwin the postgresql binary package already include
the library versions:
/usr/bin/cygecpg-6.dll
/usr/bin/cygecpg_compat-3.dll
/usr/bin/cygpgtypes-3.dll
/usr/bin/cygpq-5.dll
attached the patch used for the build.
Regards
Marco
--- origsrc/postgresql-9.4.2/src/Makefile.shlib 2015-05-20 00:33:58.000000000
+0200
+++ src/Makefile.shlib 2015-05-27 23:01:09.379468300 +0200
@@ -267,7 +267,7 @@ endif
ifeq ($(PORTNAME), cygwin)
LINK.shared = $(CC) -shared
ifdef SO_MAJOR_VERSION
- shlib = cyg$(NAME)$(DLSUFFIX)
+ shlib = cyg$(NAME)-$(SO_MAJOR_VERSION)$(DLSUFFIX)
endif
haslibarule = yes
endif
@@ -359,12 +359,9 @@ ifeq ($(PORTNAME), cygwin)
# Cygwin case
$(shlib): $(OBJS) | $(SHLIB_PREREQS)
- $(CC) $(CFLAGS) -shared -o $@ $(OBJS) $(LDFLAGS) $(LDFLAGS_SL)
$(SHLIB_LINK) $(LIBS) $(LDAP_LIBS_BE)
+ $(CC) $(CFLAGS) -shared -o $@ -Wl,--out-implib=$(stlib) $(OBJS)
$(LDFLAGS) $(LDFLAGS_SL) $(SHLIB_LINK) $(LIBS) $(LDAP_LIBS_BE)
-$(stlib): $(OBJS) | $(SHLIB_PREREQS)
- rm -f $@
- $(LINK.static) $@ $^
- $(RANLIB) $@
+$(stlib): $(shlib) ;
else
--- origsrc/postgresql-9.4.2/src/interfaces/libpq/Makefile 2015-05-20
00:33:58.000000000 +0200
+++ src/interfaces/libpq/Makefile 2015-05-27 22:56:43.193200600 +0200
@@ -45,7 +45,7 @@ OBJS += ip.o md5.o
OBJS += encnames.o wchar.o
ifeq ($(PORTNAME), cygwin)
-override shlib = cyg$(NAME)$(DLSUFFIX)
+override shlib = cyg$(NAME)-$(SO_MAJOR_VERSION)$(DLSUFFIX)
endif
ifeq ($(PORTNAME), win32)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
