Re: GPRBuild / RTS question

[Simon Wright <simon@pushface.org>]

alby.gamper@gmail.com writes:

> On Sunday, March 24, 2019 at 8:02:38 PM UTC+11, Simon Wright wrote:
>> Project Search Path:
>>    <Current_Directory>
>>    /opt/gnat-ce-2018/x86_64-apple-darwin16.7.0/native/lib/gnat
>>    /opt/gnat-ce-2018/x86_64-apple-darwin16.7.0/native/share/gpr

In other words, the first place that gprbuild will look for projects is
under $prefix/{machine}/{rts} - assuming that gprbuild applies the same
algorithm as gnatls, of course.

>>    /opt/gnat-ce-2018/x86_64-apple-darwin16.7.0/lib/gnat
>>    /opt/gnat-ce-2018/x86_64-apple-darwin16.7.0/share/gpr
>>    /opt/gnat-ce-2018/share/gpr
>>    /opt/gnat-ce-2018/lib/gnat
>> 
>> So, looks as though you can indeed install under
>> $prefix/{machine}/{rts}; can't immediately see what gprinstall
>> incantation you'd need, but should be possible!

> Thanks for your feedback, much appreciated! I had actually figured out
> that the rts needs to be located under $prefix/(machine)/{rts} as this
> is where gprbuild expects it to be when referenced. However my
> original question was more about where libraries that are dependant on
> {rts} should be installed too
>
> My current approach is to install underneath $prefix/(machine)/{rts}
> rather than $prefix, which in my mind makes sense and reduces the
> likelihood of the dependant library being used by an application that
> does not specifically need or want {rts}

Sorry not to have been clearer. This was exactly what I was trying to
say.