Closed kj-sh604 closed 7 years ago
I'll try set it to 1 in evening (Central European Summer Time).
nice, it compiles on my system.. so i think enabling the vaapi patch won't cause it to not build anymore... Thanks =)) expecting to get chromium-dev with the vaapi patch from this repo again =))
Returned home late. Probably I have to wait until Tuesday.
2016/10/02 午後11:56 "Aedriel Javier" notifications@github.com:
nice, it compiles on my system.. so i think enabling the vaapi patch won't cause it to not build anymore... Thanks =)) expecting to get chromium-dev with the vaapi patch from this repo again =))
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/archlinuxcn/repo/issues/283#issuecomment-250998951, or mute the thread https://github.com/notifications/unsubscribe-auth/ABXq-ukFkr1-nisGhraQ-lf2gNQnrwO6ks5qwCingaJpZM4KLxqi .
Thanks for providing the patch, this package has been a bit of a bear lately. Looking forward to seeing if the next build has fixed vaapi.
I updated this manually, and it's building now. I'll upload it to archlinuxcn/ tomorrow (Europe Central Time) if the build succeded. And updated to code to replace _vaapi to 1 by default. but before aur fixes the problem the file name in noextract= (L115), the preprare (L397) function and the downloaded url (L90) are not consistent, the automatic build will fail for further updates.
The problem is not about build or not build, the problem is, in my system, if I apply the pacth, i get segfault in the vaapi part and lost the HW acceleration (i'm nvidia user).
without patch, the HW acceleration working (again, for me) with zero issues.
for this, the apply or not the patch, need active by the user if set the variable _patch_vaapi (L17 as said @BigEars431) to 1
no need edit nothing about the patch. except when @saiarcot895 release the new version of their patch
I don't have nvidia gpu to test this. I'll start to provide two binary builds to gain more feedback from the repo users since tomorrow. @sl1pkn07 can you update your PKGBUILD to make the file name in L90, L115, and L397 consistent? Or setting _patch_vaapi=1 will fail the makepkg due to file not found.
done
The new builds that were pushed today still aren't working for me to enable h264 again, but there's been some activity creating a new patch: https://github.com/saiarcot895/chromium-ubuntu-build/issues/2
chromium-dev doesn't include the vaapi patch for now.
It looks either the build or the script failed for chromium-dev-vaapi
On Thu, Oct 6, 2016 at 1:15 AM, axfelix notifications@github.com wrote:
The new builds that were pushed today still aren't working for me to enable h264 again, but there's been some activity creating a new patch: saiarcot895/chromium-ubuntu-build#2 https://github.com/saiarcot895/chromium-ubuntu-build/issues/2
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/archlinuxcn/repo/issues/283#issuecomment-251826529, or mute the thread https://github.com/notifications/unsubscribe-auth/ABXq-iftZXIfrpWBrVqthEQ-_qZRb27cks5qxC-KgaJpZM4KLxqi .
I wrote something wrong for the sed syntax. Just fixed, hope it works. If yes, chromium-dev-vaapi will be pushed in less than 1 hour.
On Thu, Oct 6, 2016 at 1:25 AM, Qijiang Fan fqj1994@gmail.com wrote:
chromium-dev doesn't include the vaapi patch for now.
It looks either the build or the script failed for chromium-dev-vaapi
On Thu, Oct 6, 2016 at 1:15 AM, axfelix notifications@github.com wrote:
The new builds that were pushed today still aren't working for me to enable h264 again, but there's been some activity creating a new patch: saiarcot895/chromium-ubuntu-build#2 https://github.com/saiarcot895/chromium-ubuntu-build/issues/2
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/archlinuxcn/repo/issues/283#issuecomment-251826529, or mute the thread https://github.com/notifications/unsubscribe-auth/ABXq-iftZXIfrpWBrVqthEQ-_qZRb27cks5qxC-KgaJpZM4KLxqi .
Tested working on Intel!!
Hi,
Again, thank you for maintaining this really awesome repo. Really helps me alot as a web-developer.
Chromium-dev in the AUR used to be compiled with the VAAPI patch; however; ever since the 55.0.XXXX.Y-Z release the patch is disabled by default as indicated by the maintainer, sl1pkn07
"Now pushed the option for enable the vaapi patch (disabled by default, to enable, you need set 1 the option _patch_vaapi in the PKGBUILD)"
I believe that's in line 17
The VAAPI patch is something, I believe, will benefit the people downloading chromium-dev from this repo, including me of course
New PKGBUILD should look something like this... Hope it compiles =))