-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebuild package chromium-dev with vaapi patch? if possible =)) (Included: a rough sample of a new PKGBUILD) #283
Comments
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:
|
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. |
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. |
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: saiarcot895/chromium-ubuntu-build#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:
|
I wrote something wrong for the sed syntax. Just fixed, hope it works. If On Thu, Oct 6, 2016 at 1:25 AM, Qijiang Fan fqj1994@gmail.com wrote:
|
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 =))
The text was updated successfully, but these errors were encountered: