Questions on dependencies
Peter Danecek
Peter.Danecek at bo.ingv.it
Tue Nov 12 13:52:20 PST 2013
Hi all,
I tried to respect the recommendations here and this is what I came up with: http://trac.macports.org/ticket/41337
I tried to run in trace mode, however, I have not installed base from trunk, so I am not sure if it is already reporting correctly. It would report to a missing libgcc dependency. But the only relation I see here, would be py-scipy, which I consider a runtime dependency only.
Any comments?
~petr
On Nov 11, 2013, at 6:11 , Joshua Root <jmr at macports.org> wrote:
> On 2013-11-10 23:23 , Michael Dickens wrote:
>> On Sun, Nov 10, 2013, at 12:47 AM, Joshua Root wrote:
>>> On 2013-11-10 05:35 , Craig Treleaven wrote:
>>>> Perhaps just the
>>>> documentation for depends_lib should be expanded to say that it
>>>> indicates both compiled and interpreted linkages?
>>>
>>> It doesn't indicate anything about linkage, it indicates that the
>>> dependency is needed at both build time and run time.
>>
>> How does one indicate a runtime dependency that is checked for at
>> configure time and not used for building or linking? I've been using
>> depends_run, but I'm not sure that always works because of the
>> configuration checking. Are these dependencies installed before
>> configuration of the target port? Do we need to redefine (as per this
>> thread) what the depends_* actually mean, to make checking for linkage
>> versus usage, and when the usage is checked for and used (to my count: 3
>> different depends_*, I think as we have now)? - MLD
>
> If it needs to be there at configure time then it's depends_build or
> depends_lib. Since it's also needed at runtime, it's the latter.
>
> - Josh
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1762 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20131112/21b168a2/attachment.p7s>
More information about the macports-dev
mailing list