Generally, whenever there is a local copy already available on the system
of a library that is to be be compiled.  In that case, it prevents the
final binaries and libraries from referencing the custom library that
exists in a custom location on your system.

Also, it is used when linking libraries that exist in the build directory,
to avoid the relinking process at the end of the build.

Tim

> When is disable-rpath necessary? I never used that option, but if there
> are times when that is necessary or advisable, then something should be in
> the wiki.
>
> Darrell
>
>
> --- On Sat, 10/2/10, Timothy Pearson <kb9vqf@...> wrote:
>
>> From: Timothy Pearson <kb9vqf@...>
>> Subject: Re: [trinity-devel] question about building trinity from
>> scratch
>> To: trinity-devel@...
>> Date: Saturday, October 2, 2010, 2:13 PM
>> disable-rpath disables the hard
>> coding of library paths within built
>> libraries and binaries, instead relying on standard library
>> search paths
>> to locate needed library files.
>>
>> I do not know what enable-final does.
>>
>> Tim
>>
>> > Is there any documentation notes we can add to the
>> wiki about
>> > "--enable-final"? How about "--disable-rpath"?
>> >
>> > Darrell
>> >
>> >
>> > --- On Sat, 10/2/10, Nicolas Kalkhof <nkalkhof@...>
>> wrote:
>> >
>> >> From: Nicolas Kalkhof <nkalkhof@...>
>> >> Subject: Re: [trinity-devel] question about
>> building trinity from
>> >> scratch
>> >> To: trinity-devel@...
>> >> Date: Saturday, October 2, 2010, 6:35 AM
>> >> Hi Timothy,
>> >>
>> >> thanks for the hint. Explicitly adding
>> --enable-final did
>> >> the job.
>> >>
>> >> My complete configuration:
>> >>
>> >> ./configure --disable-dnssd --without-arts
>> --without-ssl
>> >> --without-xinerama --disable-rpath --enable-final
>> >> --prefix=/opt/kde-3.5.12
>> >
>> >
>> >
>> >
>> >
>>
>>
>>
>
>
>
>