Renaming a shared library in the port-framework to match FreeBSD
ohartman at zedat.fu-berlin.de
Fri Nov 19 14:03:58 UTC 2010
On 11/19/10 13:46, Koop Mast wrote:
> On Fri, 19 Nov 2010 12:32:33 +0100
> "O. Hartmann"<ohartman at zedat.fu-berlin.de> wrote:
>> Trying to do my first port and run into trouble.
>> The software package (Xerces-c 3.1.1) comes with a full autotoll
>> environment and so far building and installing works.
>> But the libarary name is "libxerces-c-3.1.so" and I need to change this
>> to respect the FreeBSD nameing schemes to "libxerces-c.so.31". I'm
>> looking for a way avoiding some "post-install:" stuff.
> There isn't any problem with the libxerces-c-3.1.so name.
> From http://www.freebsd.org/doc/en/books/porters-handbook/special.html
> Try to keep shared library version numbers in the libfoo.so.0 format.
> Our runtime linker only cares for the major (first) number.
Well, this is the problem. The automated installation process installes
>> Is it possible to manipulate the library name via some variables passed
>> through the port-framework to the build-enviroment?
> There isn't. We leave the library name just like upstream/author wants it to be. We only hack the library version if needed.
This implies having a post-install: target in the Makefile where I'm
supposed to move libxerces-c-3.1.so libbxerces-c.so.31?
>> Well, I'm very new to porting and this may seem to be a very easy task
>> for experienced porters, so please excuse possible bothering ...
>> Thanks in advance,
>> freebsd-ports at freebsd.org mailing list
>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
More information about the freebsd-ports