| 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: | 2006-02-25 13:20:36 |
| Message-ID: | 440059A4.1000701@tada.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-02-25 15:00:26 | Re: Resurrecting some old patches |
| Previous Message | Peter Eisentraut | 2006-02-25 13:02:15 | Re: What's with this lib suffix? |