Date: Tue, 23 Feb 2010 02:57:46 -0800 From: Stephen Hurd <shurd@sasktel.net> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: Ronald <followait@163.com>, "Freebsd-Chat@Freebsd.Org" <freebsd-chat@freebsd.org> Subject: Re: Where to put private lib files? Message-ID: <4B83B4AA.3030405@sasktel.net> In-Reply-To: <868wak2sv5.fsf@ds4.des.no> References: <DD958BBC52D94F79855244E6890704DB@jqslaptop> <868wak2sv5.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Sm=C3=B8rgrav wrote:
> "Ronald" <followait@163.com> writes:
> =20
>> I think the global lib directories is not so good, because it should
>> be for public libs.
>>
>> The libs private to one application, where to put them?
>> =20
>
> The canonical location for ports is ${LIBDIR}/${PORTNAME}, but remember=
> that unless these are run-time loadable modules, this directory must be=
> in the library search path when you run the app. This means that you
> either have to ldconfig the directory using an rc_subr script (which
> defeats the purpose of having a private library directory) or install a=
> wrapper that sets LD_LIBRARY_PATH before execing the real binary.
> =20
You can also compile in a search path.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B83B4AA.3030405>