09.10.2020, 14:45
Ok, got it. From some point of view it is more accurate arranegement, but same time it may produce confusion if someone in future decide to update .dylibs without knowing that they require customized paths.
So seems .dylib structure was adjusted in same way in new Hybrid version:
libboost_filesystem.dylib and libboost_system.dylib now located only in "Frameworks" folder
libfreetype.6.dylib, libpng16.16.dylib, libx265.195.dylib moved to "lib" folder
libz.1.dylib and libbz2.1.0.dylib no more used at all?
Will xvid_encraw work with legacy Hybrid UI versions?
So seems .dylib structure was adjusted in same way in new Hybrid version:
libboost_filesystem.dylib and libboost_system.dylib now located only in "Frameworks" folder
libfreetype.6.dylib, libpng16.16.dylib, libx265.195.dylib moved to "lib" folder
libz.1.dylib and libbz2.1.0.dylib no more used at all?
Will xvid_encraw work with legacy Hybrid UI versions?
Quote:Will xvid_encraw work with legacy Hybrid UI versions?Probably it will not because there is no xvid_encraw in Config-Tools in legacy versions of Hybrid UI.