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

What's with this lib suffix?


  • From: Thomas Hallgren <thomas(at)tada(dot)se>
  • To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
  • Subject: What's with this lib suffix?
  • Date: Sat, 25 Feb 2006 13:17:56 +0100
  • Message-id: <44004AF4(dot)8000608(at)tada(dot)se>

I have a PL/Java bug entry from Peter E. that reads "It is customary in PostgreSQL land and elsewhere, that dynamically loadable modules do not have a lib prefix (compare plpgsql.so, pltcl.so, etc.). So I suggest that the shared object installed by PL/Java also be called exactly pljava.so.".

I'd like to follow customary practices but as it turns out, I'm not the one adding the 'lib' prefix. It's done by the Makefile.shlib that comes bundled with pgxs. Here you can read things like:

 # 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?

Personally, I'd prefer to keep the 'lib' prefix since it really *is* the default naming convention on all *n[iu]x platforms I've been in contact with. Not so on Windows though so perhaps that should change in Makefile.shlib?

I'm confused.

Kind 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