[MacPorts] #64353: opencv3 has undocumented dependencies
MacPorts
noreply at macports.org
Mon Jan 10 04:08:18 UTC 2022
#64353: opencv3 has undocumented dependencies
-------------------------+----------------------
Reporter: mouse07410 | Owner: mascguy
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: opencv3 |
-------------------------+----------------------
Comment (by mouse07410):
> whatever you want. macports-clang-13 to build everything by default: put
it first. xcode clang to build everything by default: put it first.
To clarify: {{{port}}} will try entries in {{{default_compilers}}} line
until it finds one that fits specific port's constraints - then it will
try to build that port with that compiler?
I.e., if my line says {{{default_compilers clang macports-clang-13
macports-gcc-11}}}, it will try to fit Xcode clang first, if cannot -
macports-clang-13, if that doesn't fit either - macports-gcc-11, and if
that one fails too- {{{port}}} will refuse to build the given port,
complaining that it cannot find a suitable compiler?
>> it doesn't even have {{{macports-clang-13}}}
>
> feel free to add it! MacPorts can always use some help, if you know what
you're doing
Well,**that** one fix doesn't seem too complicated to me - done. Thanks!
> > if something fails to build with macports-clang-13 - wouldn't you want
to know...?
>
> Use your discretion
Understand perfectly. No worries here.
Currently, my {{{macports.conf}}} only adds proxy settings to its default
content. If I add {{{default_compilers}}} - I don't need to reload
anything, or refresh whatever cache, or such - right? And to revert to the
original behavior, I can just comment that line out, and maybe {{{port
clean ...}}} the port that fails to build with that line present?
Thanks!
--
Ticket URL: <https://trac.macports.org/ticket/64353#comment:28>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list