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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: What's with this lib suffix?


  • From: Thomas Hallgren <thomas(at)tada(dot)se>
  • To: Peter Eisentraut <peter_e(at)gmx(dot)net>
  • Cc: pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: What's with this lib suffix?
  • Date: Sat, 25 Feb 2006 14:20:36 +0100
  • Message-id: <440059A4(dot)1000701(at)tada(dot)se>

Peter Eisentraut wrote:
Thomas Hallgren wrote:
  # Default shlib naming convention used by the majority of platforms
  shlib		=
lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION).$(SO_MINOR_VERSION)
shlib_major	= lib$(NAME)$(DLSUFFIX).$(SO_MAJOR_VERSION)
  shlib_bare	= lib$(NAME)$(DLSUFFIX)

and sure enough, that's what gets used too. So what goes?

You are confusing the naming convention for shared libraries that are intended to be linked into programs (or other libraries) at build time, which normally have to be named libsomething.so because that is what the compiler/linker flag -lsomething resolves to, with the naming convention for shared libraries that are intended to be loaded at run-time (sometimes called plug-ins), which require no particular naming.

In that case, I'd appreciate some advice on how to use the pgxs package to compile a 'plug-in'. Looks to me it's only designed to compile 'shared libraries'.

Regards,
Thomas Hallgren




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group