On 2018/09/07 12:57, Rafael Sadowski wrote:
> Hi Pascal, Hi ports@,
> 
> last week I worked on boost 1.68.0. It's a long depends path again.
> Long story short. Our yaml-cpp is outdated and use non existing boost
> parts. New yaml-cpp will break our old opencolorio.
> 
> Anyway, please find below an update diff to the latest stable version.
> I don't know which  version is hidden behind 20140911.
> 
> All consumers looks fine on amd64. I see just new symbols in
> OpenColorIO, so I only raised minor.
> 
> OK?
> 
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/graphics/opencolorio/Makefile,v
> retrieving revision 1.8
> diff -u -p -u -p -r1.8 Makefile
> --- Makefile  26 Jul 2017 22:45:24 -0000      1.8
> +++ Makefile  7 Sep 2018 10:49:49 -0000
> @@ -2,16 +2,17 @@
>  
>  COMMENT =            color management library
>  
> -V =                  20140911
> -DISTNAME =           OpenColorIO-$V
> -PKGNAME =            opencolorio-$V
> -REVISION =           1
> +V =          1.1.0
> +GH_ACCOUNT = imageworks
> +GH_PROJECT = OpenColorIO
> +GH_TAGNAME = v${V}
> +DISTNAME =   opencolorio-$V

Untested, but from reading, the version goes backwards -> bump EPOCH.

>  CONFIGURE_ARGS +=    -DPYTHON="${MODPY_BIN}" \
> -                     -DUSE_EXTERNAL_TINYXML=ON \
> -                     -DUSE_EXTERNAL_YAML=ON \
> -                     -DOCIO_USE_SSE=OFF \
> -                     -DOCIO_BUILD_STATIC=OFF \
>                       -DOCIO_BUILD_APPS=OFF \
> +                     -DOCIO_BUILD_JNIGLUE:BOOL=OFF \
> +                     -DOCIO_BUILD_NUKE:BOOL=OFF \
> +                     -DOCIO_BUILD_STATIC=OFF \
> +                     -DOCIO_BUILD_TRUELIGHT:BOOL=OFF \
> +                     -DOCIO_USE_SSE=OFF \
> +                     -DUSE_EXTERNAL_TINYXML:BOOL=ON \
> +                     -DUSE_EXTERNAL_YAML:BOOL=ON \

I don't know cmake all that well, but the mixture of lines with and
without :BOOL seems unusual?

No objection to preparatory work before 6.4-release, but it's too late
in the cycle to get good testing coverage to update boost.

Reply via email to