[MacPorts] #49670: OpenCV 2.x (please re-instate or provide a new opencv2 port)

MacPorts noreply at macports.org
Sun Oct 31 14:38:58 UTC 2021


#49670: OpenCV 2.x (please re-instate or provide a new opencv2 port)
--------------------------+----------------------
  Reporter:  macports@…   |      Owner:  mascguy
      Type:  enhancement  |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  opencv       |
--------------------------+----------------------

Comment (by mascguy):

 Replying to [comment:11 mascguy]:
 > But there's one fly in the ointment: It depends on QTKit headers not
 available on newer MacOS releases. And thus far, I haven't found an
 acceptable workaround.
 >
 > Grabbing those headers from an older MacOS SDK, and copying them into
 the port's source tree, fixes the problem. But that's not a great
 solution. (And could be problematic from a licensing perspective, though
 that's not confirmed.)

 I'm interested in folks' thoughts/guidance on this. In particular, can the
 QTKit headers be included in the port - perhaps via a compressed tar file
 - and used during the build phase?

 I'm not asking from a technical perspective, as that's the easy part.
 Instead, I'm concerned about the legality of doing that. Can we include
 those with the port - and use them at build time - without issue?

-- 
Ticket URL: <https://trac.macports.org/ticket/49670#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list