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

[MacPorts]

#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:14 RJVB]:
 > Just how hard and extensive is that dependency on QTKit on Mac?
 Evidently that SDK was never available on other platforms. And what if you
 were to provide a `port:QTKit` ... would it be functional on systems where
 it is no longer included?
 >
 > (That last question should be answerable by checking if applications
 using QTKit still run on those newer systems.)
 >
 > Have you looked if anyone wrote a QTKit replacement built on modern
 foundations? Back when the QT SDK was being deprecated (and I was still
 using it) I started looking into QtAV but for this you'd ideally want
 something built on AVFoundation I suppose.
 >
 > CF: https://stackoverflow.com/questions/39735485/opencv-installation-
 failure-due-to-qtkit

 Based on my previous research, the vast majority of suggestions related to
 grabbing the headers from an older SDK, and building against those. So
 that was the approach I settled on, though I'm not married to it.

 And while we could potentially add a 2nd port for the headers, I was
 hoping to avoid that. Particularly if Ryan creates ports for the various
 macOS SDKs, as then we could potentially depend on those (when needed).

 The suggestion relative to QtAV is interesting, for sure. Though it looks
 a bit heavyweight, as we really just need the headers.

 Does that make sense? Your thoughts?

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