вс, 17 дек. 2023 г., 18:13 Andrew Randrianasulu <[email protected]>:
> Sadly, libaom 3.8.0 broken quite hard on cmake 3.5 not sure if I will able > to fix it. > ah, this one https://aomedia.googlesource.com/aom/+/a250c26cade747ead5ff434ba4c69ca012115e5b%5E%21/#F0 may be I'll able to adapt code back to old way of building nasm objects ... it fails to find includes. > вс, 17 дек. 2023 г., 17:10 Andrew Randrianasulu <[email protected]>: > >> >> >> вс, 17 дек. 2023 г., 16:46 Andrew Randrianasulu <[email protected] >> >: >> >>> >>> >>> вс, 17 дек. 2023 г., 16:13 Andrea paz <[email protected]>: >>> >>>> I tried to compile CinGG with your patches. I had problems applying >>>> the opencv one >>> >>> >>> Most likely because it already upstream in our git ? >>> >>> >>> and the x265 one however, by passing the paths >>>> manually, I think I was able to apply them (apologies, apparently my >>>> brain refuses to understand how patches work). >>> >>> >>> was "git am" failing for some reason? You always can inspect patches >>> visually (say with "less patch.diff") and see if they from git or plain >>> patches .... >>> >> >> >> Ah, fired up ubuntu 16 VM, patch really fails to apply because I put my >> changes on top of another experimental patch (attached). >> >> So you can try to apply it first, and then two other patches from folder. >> >> Do not forgot to mv thirdparty/src/x265_3.5.tar.xz to another location >> and move both xz tarballs to thirdparty/src ! >> >> Sorry for inconvenience .... >> >> >>> The compilation however >>>> fails immediately, I think with an error about x265. I attach the >>>> cin5.log >>>> >>> >>> /bin/bash: riga 1: cd: x265*: File o directory non esistente >>> >>> >>> are you sure you have both x265-17122023.tar.xz in thirdparty/src and it >>> also correctly named in configure.ac (in case patching failed) AND >>> your run ./autogen.sh ? >>> >>>
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
