> On 18 Aug 2023, at 23:59, Joseph Myers <jos...@codesourcery.com> wrote:
>
> On Fri, 18 Aug 2023, Iain Sandoe via Gcc-patches wrote:
>
>> There is quite extensive Apple Developer documentation on delivering
>> packages with co-installed libraries using @rpath (that is the intended
>> mechanism for delivery since it allows drag-and-drop installation and
>> moving of built applications).
>>
>> The revised compiler has libraries already built in a suitable manner
>> for that distribution model.
>>
>> I would not propose that we repeated such information - but we could
>> refer to it?
>>
>> Generally, I’d prefer we suggested searching for such documentation,
>> rather than linking to it, since links can expire - does that seem
>> reasonable?
>
> I suppose the key thing is to note that, if building a program for
> distribution, you shouldn't build it to embed
> /path/to/compiler/install/lib, but instead should do <something else,
> possibly referring to relevant Apple documentation>.
right, exactly - there are special runpath roots like @executable_path and
@loader_path that provide for packages that are fully relocatable (we
actually use some of this to allow GCC runtimes to find their dependent
runtimes without needing an absolute runpath).
OK. We just need to find a suitable place to put this - perhaps in documenting
-nodefaultrpaths (since that’s usually used together with specifying something
different).
thanks,
Iain
>
> --
> Joseph S. Myers
> jos...@codesourcery.com
