"Qin, Jiajia" <jiajia....@intel.com> writes: > In the latest week, I was working on the next branch to verify that > whether video hardware acceleration has been supported in > ozone-wayland. The bellow patches which are to fix the compile error > when opening the video hardware acceleration have been merged in > ozone-wayland upstream but not in crosswalk 8. > https://github.com/01org/ozone-wayland/pull/246 > https://github.com/01org/ozone-wayland/pull/249 > > I will send a PR to crosswalk to cherry-pick the above PRs.
Thank you. In case it's not clear, you first have to get those changes backported to ozone-wayland's Milestone-Summer branch and only then roll DEPS.xwalk in Crosswalk. Looking at the changes, though, this applies only to #246: #249 is a patch to Chromium itself, which means you have to send an actual pull request to chromium-crosswalk with the change and then roll DEPS.xwalk -- of course, this also means that in this case your change must also work on the non-Ozone-Wayland case as well. > Another thing is when I was building the crosswalk for tizen, some > issues I met were same with Rapheal. But at that time, I didn't known. > So, we did some repeated work. Such as webrtc issue, we are looking > the same problem. Changbin has submitted a Cl to fix it > (https://webrtc-codereview.appspot.com/13999004/ ). Again, your work > is highly appreciated. If you need any help about > media(audio/video/webrtc), we are happy to provide help. Thank you > very much! That's good to know. My experience trying to contact the WebRTC people has not been a good one so far, so any help with fixing those build system changes is highly appreciated. _______________________________________________ Crosswalk-dev mailing list Crosswalk-dev@lists.crosswalk-project.org https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
