• https://github.com/opencv/opencv/archive/4.5.2/ (Download)

• no_java

• (2021-04-24) Updated to version: opencv-4.5.2
• (2020-12-24) Updated to version: opencv-4.5.1
• (2020-10-26) Updated to version: opencv-4.5.0
• (2020-09-04) Updated to version: opencv-4.4.0
• (2020-01-19) Updated to version: opencv-4.2.0
• (2019-09-27) Updated to version: opencv-3.4.7
• (2019-03-23) Updated to version: opencv-3.4.2
• (2017-11-04) Updated to version: opencv-2.4.13.4
• (2016-11-29) Updated to version: opencv-2.4.13
• (2015-11-24) Updated to version: opencv-2.4.12.3

Log message:
Bump revision on all 1.8+ ports since now they will build with jdk
1.8 on aarch64 and their run depends will also change. okay ian@

Log message:
enable filesystem support which is just basic Unix primitives.
okay rsadowski@

Log message:
Update opencv to 4.5.2

Log message:
have opencv generate a pc file, 'cause some software (gmic) is looking
for that.
no obvious fallout in a bulk (saw the remaining -fno-common stuff, but
nothing seemed to pick it up).
okay rsadowski@

Log message:
Reverse the polarity of MODPY_VERSION; default is now 3.x,
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.

Log message:
regen PLISTs for python ports with .so files that end up renamed due to
the EXT_SUFFIX change in Python 3.8.7

Log message:
OpenCV included both py2 and py3 bindings in one package with an awkward
construct (MODPY_VERSION=2.7 and some hand-rolled 3.x pieces). Nothing in
ports uses them. Remove the (deprecated) py2 bindings leaving just the py3
ones with a more standard ports setup. ok rsadowski@ (maintainer).

Log message:
Update opencv to 4.5.1
https://github.com/opencv/opencv/wiki/ChangeLog#version451

Log message:
Update opencv to 4.5.0

Log message:
Update opencv to 4.4.0

Log message:
Bump for py3.7 -> py3.8

Log message:
Add missing run depends math/py-numpy,python3, spotted by sthen@

Log message:
Enable python3 libs in opencv
Requested and tested by solene@

Log message:
Fix WANTLIB after openexr update.

Log message:
opencv: don't require `-latomic' anymore on powerpc, since
this arch has been switched to clang
OK rsadowski@ (maintainer)

Log message:
Upbreak opencv 4.2
- Remove deprecated option ENABLE_SSE3.
- Disable ADE (gapi) support because this requires to download ADE
during configure.
Spotted my sthen@ and neddy@, thanks for your support

Log message:
Update opencv to 4.2
CMake renames like off to OFF and so one.

Log message:
Regen DEPENDS and WANTLIB after recent openexr update.

Log message:
opencv: needs atomics on macppc (and probably hppa)
OK rsadowski@ (maintainer)

Log message:
Unbreak:
- fix bogus WANTLIB
- remove bogus LDEP on graphics/libgphoto2

Log message:
Update opencv to 3.4.7
Notable port changes:
- Remove -docs to avoid java conflicts with JDK 8 and 11.
- Upstream switched completely to github
- Sort CONFIGURE_ARGS
- Add patch to install licenses files at the old location.
- ONLY_FOR_ARCHS-java = aarch64 amd64 i386
ok kurt@

Log message:
Drop the clang module, not needed
While here, strip base-gcc from COMPILER (a recent c++ compiler is
required) and move to PERMIT_PACKAGE.  ok rsadowski@ (maintainer)

Log message:
Revision bump all java ports for the jre package removal and java.port.mk
changes.

Log message:
set png16 WANTLIB entries back to png following the change in soname
part done by portbump, part by hand (it is easily confused)

Log message:
Update opencv to 3.4.2
OK kn@ Thanks! Big Thanks!

Log message:
Preemptive build fix for newer FFmpeg, from Brad.

Log message:
Add COMPILER lines to c++ ports which currently use the default. Adjust
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.

Log message:
Fix clang6 build

Log message:
bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports.

Log message:
use COMPILER_LIBCXX where applicable

Log message:
fixes clang, forgotten commit

Log message:
Add ${CLANG_ARCHS} to "ONLY_FOR_ARCHS = ${GCC4_ARCHS}" lines to give them
a chance on aarch64.

Log message:
use LIBCXX

Log message:
zap zero-byte files, list from rsadowski

Log message:
update to opencv-2.4.13, from maintainer Rafael Sadowski with a few tweaks by me
and ok with him.

Log message:
Unbreak after py-sphinx update to 1.4

Log message:
drop SHARED_ONLY from python and ruby ports

Log message:
Update OpenCV to 2.4.12.3.
This fixes library naming in pkg-config files, as it was reported on ports@.
Also, it'd be last update before OpenCV 3.0, which is WIP (in openbsd-wip).
From maintainer Rafael Sadowski, thanks!

Log message:
Fix two build problems in OpenCV, triggered after recent changes in
ports tree (that doesn't meant that those problems come from lands other
than OpenCV itself):
1. Stop exporting opencv_java target: noone links to the libopencv_java.so,
anyway, and it breaks find_package(OpenCV) when opencv-java is absent.
The actual broken port was Digikam on i386 (yes, due to some funny
reasons, this didn't trigger on amd64).
2. Switch to gstreamer1 since OpenCV picks it up nowadays, if the former
is found. WANTLIB updates included.
Initial report and testing by sthen@.
Okays:
(1) by dcoppa@, sthen@ (implicit) and Rafael Sadowski (MAINTAINER).
(2) by sthen@ (implicit).

Log message:
Completely disable offending part of CPU features detection for i386.
It came between OpenCV 2.4.9 and 2.4.10, and continues to break on at least
sthen@'s build system. In other words, this unbreaks OpenCV 2.4.10 on i386.
requested by sthen@

Log message:
Put back i386 to the list of ONLY_FOR_ARCHS-java. To be removed if problems
will arise again.

Log message:
Update OpenCV to 2.4.10, mostly from Rafael Sadowski (MAINTAINER).
This switches the whole package to PIC (from PIE) due to problems with
inline assembly and build system specifics. Since OpenCV is used mostly
as a library, this shouldn't be a big problem.

Log message:
pch don't really work
in fact, it causes an ICE while building the port on amd64,
so patch it out, and bump.

Log message:
Fix build with png-1.5.
All fixes from/via NetBSD pkgsrc.  The people there did a lot of
heavy lifting.