opencv version 3 vs. 2

David Evans devans at macports.org
Sat Jun 20 18:06:56 PDT 2015


On 6/20/15 11:57 AM, "Marko Käning" wrote:
> Hi Ryan,
>
>> If fixing those two ports is more complicated than just updating them to a
>> newer version, or copying an existing patch from upstream, then yes, it
>> would be fine to create an opencv2 port.
> ok, I'll wait a bit until I have feedback from the digikam developer, but
> I have no idea about VLC-devel and the other hidden cases of conflicts.
>
>
>
The opencv video input plugin for VLC-devel was disabled in r137661 
<https://trac.macports.org/changeset/137661> so it at least builds now.
Similarly the opencv plugin for gstreamer1-gst-plugins-bad was disabled 
in r137657. <https://trac.macports.org/changeset/137657>
auto-multiple-choice was patched by maintainer to build with opencv 3 in 
r137787. <https://trac.macports.org/changeset/137787>
gmic accidentally survived because it doesn't configure to build with 
opencv on darwin in spite of depending on it #48084.

digikam remains unresolved as you mentioned.

I think that leaves the following dependents of opencv that need to be 
checked for compatibility with opencv 3 or at least have their
revision incremented to rebuild with the new library version.

caffe
gerbil
nomacs
objectmarker
orfeotoolbox

Dave



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150620/0eac2c87/attachment.html>


More information about the macports-dev mailing list