Re: [Cin] OpenEXR 2.4 - try3!

В сообщении от Thursday 19 March 2020 06:30:14 Phyllis Smith написал(а): > This OpenEXR package is a "bag of worms" -- weird, hard, and worse package > to integrate in Cinelerra. GG has taken your patches, made quite a few > changes, and got it to work at 2.4.1. Tomorrow he will test to see how

Re: [Cin] OpenEXR 2.4 - try3!

This OpenEXR package is a "bag of worms" -- weird, hard, and worse package to integrate in Cinelerra. GG has taken your patches, made quite a few changes, and got it to work at 2.4.1. Tomorrow he will test to see how it does on the 18+ distros to see if it will work for the monthly builds.

[Cin] OpenCV no-gphoto2 patch re-send

Hopefully THIS ONE should be safe problem only affects system where OLD Gphoto2 installed But disabling stuff shouldn't break builds ... I hope! -- diff --git a/cinelerra-5.1/opencv_build b/cinelerra-5.1/opencv_build index 20d6ea1..1e4c777 100644 --- a/cinelerra-5.1/opencv_build +++

[Cin] Now trying to make my x265-multilib patches in more upstreamable form

Oh, because I wrestle with buildsystem anyway ... I created three x265 patches, to be put in thirdparty/src alongside x265 tarball patch 1 basically adds empty (/bin/true) pseudo configure patch 2 adds Makefile - it will do some library copying work patch 3 adds miltilib.sh, adapted from x265's

Re: [Cin] Checked in tweaked patches from Andrew - EXR, PNG, and TIFF

В сообщении от Wednesday 18 March 2020 18:57:25 Phyllis Smith написал(а): > Andrew: > > > Also, minor bug: > > > > If I render OpenEXR sequence, load it, play it, > > and then delete main image files but NOT index *.exrs > > - and try to load file from "recent files" sub-menu in main menu - Cin

Re: [Cin] Checked in tweaked patches from Andrew - EXR, PNG, and TIFF

Andrew: > Also, minor bug: > > If I render OpenEXR sequence, load it, play it, > and then delete main image files but NOT index *.exrs > - and try to load file from "recent files" sub-menu in main menu - Cin > will terminate > > Easily reproduced here. GG says OpenExr is doing a "throw" and

Re: [Cin] OpenEXR 2.4 - try3!

В сообщении от Wednesday 18 March 2020 18:00:06 Good Guy написал(а): > These changes look good. Thanks. > and now the inevitable "but"..., these are just suggestions, > but they are based on my past experiences. > > 1) don't leave dead code in the product unless you think it may be useful >

Re: [Cin] OpenEXR 2.4 - try3!

В сообщении от Wednesday 18 March 2020 18:00:06 Good Guy написал(а): > These changes look good. Thanks. > and now the inevitable "but"..., these are just suggestions, > but they are based on my past experiences. > > 1) don't leave dead code in the product unless you think it may be useful > in

Re: [Cin] OpenEXR 2.4 - try3!

These changes look good. Thanks. and now the inevitable "but"..., these are just suggestions, but they are based on my past experiences. 1) don't leave dead code in the product unless you think it may be useful in the future. examples: the configure script is already sort of trashy, since it

[Cin] Try2: OpenEXR 2.4 patches

Forgot to add main patch for .configure.ac :/ Thing is, even after ./autogen.sh && ./configure resulted cin file still links to system's *shared* ilmbase/openexr libs :/ diff --git a/cinelerra-5.1/configure.ac b/cinelerra-5.1/configure.ac index f10af67..11d527b 100644 ---

[Cin] OpenEXR 2.4 patches

diff --git a/cinelerra-5.1/thirdparty/Makefile b/cinelerra-5.1/thirdparty/Makefile index 5315237..50b9358 100644 --- a/cinelerra-5.1/thirdparty/Makefile +++ b/cinelerra-5.1/thirdparty/Makefile @@ -195,9 +195,9 @@ audiofile.mak_params?=LIBS="-lm -lstdc++" flac.cfg_params?= --enable-shared=no

[Cin] UPD:Thirdparty buildsystem - absolute paths?

x:/dev/shm/tmp/cinelerra-goodguy-20200318/cinelerra-5.1/thirdparty# rm build/openexr.source root@slax:/dev/shm/tmp/cinelerra-goodguy-20200318/cinelerra-5.1/thirdparty# rm -rf openexr-2.4.1/ root@slax:/dev/shm/tmp/cinelerra-goodguy-20200318/cinelerra-5.1/thirdparty# setarch i686 make -j 5 tar -xzf s