 |
A fix for "cinelerra-5.1/msg/txt" is ready to go on the next GIT checkin. |
 |
cinelerra-5.1/msg/txt +September 2019 New Features of note: + Libraries x265 and openexr have been upgraded. |
|
|
Bad news here. When doing the monthly builds we had to "revert openexr-2.4.0, breaks most builds, req cmake past baseline, bad configure fallbacks". The CMAKE program on almost all the distros on which we build CinelerraGG, is not up to the requirement set by the openexr programmer. For example Ubuntu 14 is one of the oldest distros, but even the later distros do not have the required cmake version. In addition the C compiler has a version level required too. The configure fallbacks did not work either. Not sure what the programmer had in mind by using cmake instead of make as it was originally and then putting such version restrictions on usage. Very disappointing. In addition, it does not appear that the developer made any code changes that enhance Cinelerra usage but rather their goal was to switch to cmake and get rid of SEGVs (always a high priority goal). I will probably email the programmer and ask for clarification and help. We will probably not upgrade cmake on all of the build machines just to "fix" this. |
|
|
A note for people like me who are not software developers, "--enable-openexr" must be used to access "thirdparty", otherwise the system files will be used. If several versions of "(lib)openexr" are installed at the same time, the one whose "-dev" package is installed wins. $ ./configure --help G -i openexr --enable-openexr build openexr (auto) --with-openexr use openexr (auto) |
|
|
This update has been checked into GIT. They switched from Make to CMake and we did a successful static and system build, tested render, and tested load of that render for single frame and for sequences. I do not think this is heavily used, but it is good to keep it up to date and to make sure it works. |
|
|
It looks like 2.4.0 is officially out of BETA and was released on the 19th. Will test tomorrow to see if any issues and if not, then probably it will go in. |
|
|
Will try to get this updated today also. Update - looked at it but it is still Beta so I will keep track of it and wait for official release. Only 1 commit has been made since Beta, so I am guessing that that will be fairly soon. We don't want to put in 2.3.0 and then just have to upgrade to 2.4.0 shortly after. |
- Anonymous
