-- Boost python support not found -- will not build python components!
[...]
install -s -m 0644 /wrkdirs/usr/ports/graphics/py-openimageio/work/.build/src/python/OpenImageIO.so /wrkdirs/usr/ports/graphics/py-openimageio/work/stage/usr/local/lib/python2.7/site-packages
install: /wrkdirs/usr/ports/graphics/py-openimageio/work/.build/src/python/OpenImageIO.so: No such file or directory
PR: 227427
Reported by: antoine (via exp-run)
While here, fix libIlmImfUtil_la_LDFLAGp so that when linking libIlmImfUtil,
the locally built libIlmImf gets precedence over the one in /usr/local,
to permit upgrades in a running system with the older version installed.
This changes the library's SONAME, so bump PORTREVISION of all dependees.
Unfortunately, this looks a bit too intrusive for an MFH to 2017Q4.
Security: CVE-2017-9110
Security: CVE-2017-9111
Security: CVE-2017-9112
Security: CVE-2017-9113
Security: CVE-2017-9114
Security: CVE-2017-9115
Security: CVE-2017-9116
Security: 803879e9-4195-11e7-9b08-080027ef73ec
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
While here, add patch for blender to fix it's build with this new version of
openimageio.
PR: 216601
Submitted by: Shane <FreeBSD@ShaneWare.Biz> (maintainer)
Renaming didn't help to unblock 3.x progress as co-existence with 2.x
was no less complex than simply fixing consumers. This commit also
restores directory-level history accidentally lost via git-svn.
PR: 210505
Pointy hat to: jbeich (should've discussed first)
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
- Complete conversion to options helpers
- Add options for JPEG and JASPER support
- Side note: This had a dependency on jpeg before, so the JPEG
option default is ON. However, the configure script wasn't
detecting it previously.
- Silence MKDIRs
- Take maintainership
- Chase shared library bump
Changes: http://www.libraw.org/download#changelog
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
To avoid confusion, the main port is to track the latest release.
Whether to rename includes/libraries as well making it possible to
install 2.x and 3.x side-by-side remains to be investigated.
PR: 210505 (for tracking)
Inspired by: PkgSrc
- Turn off FFMPEG option by default; fix spelling of "FFmpeg" and "Color"
- Make sure that `graphics/py-openimageio' slave port remains optionless
- While here, wrap couple of long lines and beautify port description text
OpenCV and FFMPEG are heavy dependencies, while these features might not even
be used in consumer ports (e.g. blender, luxrender, and appleseed). More to
it, OpenCV is broken on PowerPC, which prevents building any consumer ports.
Approved by: maintainer
- While here, minor port cleanup, switch to options helpers
- Bump PORTREVISIONs of consumers as soversion has changed
PR: 204553
Submitted by: graham@menhennitt.com.au
Instead of defining a variable that is almost always based on CONFIGURE_ENV,
just use CONFIGURE_ENV directly.
This also matches the behavior of other ports that do not use autotools (so
most ports can just worry about CONFIGURE_ENV). Additionally, the fact that
we do not use ?= means we do not have problems if another file in Uses/
needs to set CONFIGURE_ENV (with CMAKE_ENV, the order of the arguments to
USES would matter).
Ports which set CMAKE_ENV have been adjusted accordingly. In most cases,
CMAKE_ENV was just replaced with CONFIGURE_ENV, the exceptions being:
* databases/sqliteman: CMAKE_ENV line removed; setting QMAKESPEC there has
no effect on the build system.
* devel/freeocl: CMAKE_ENV line removed; FREEOCL_CXX_COMPILER is already
retrieved from the CMAKE_CXX_COMPILER variable in the build
system.
* graphics/openimageio: CMAKE_ENV line removed; setting Qt variables there
has no effect on the build system.
Reviewed by: makc
Differential Revision: https://reviews.freebsd.org/D3403
OpenImageIO 1.5 comes with many new features and bug fixes:
* lots of new functions for image handling (API and command line tools),
such as rotations, median filters, matrix transformations
* new filters (cubic, rifman, simon, ...)
* image metadata support (EXIF)
* SIMD (SSE) instruction support to speed up processing images
* basic movie file support via ffmpeg
Changelog: https://github.com/OpenImageIO/oiio/blob/RB-1.5/CHANGES
PR: 200818
Submitted by: Shane Ambler <FreeBSD@ShaneWare.Biz>
This is no longer needed after the same thing was removed from OpenEXR, and moreover it breaks opencolorio-tools on 9.x
PR: 197907
Approved by: portmgr blanket, maitainer timeout
dependencies do that now and the old GCC 4.2 system compiler fails to
link with those.
PR: 197907, 196712
Submitted by: FreeBSD@ShaneWare.Biz (maintainer)
