browser status on "pure wayland"

[Andrea Giammarchi]

I popped it yesterday in freenode but everyone was probably busy :-)

Meanwhile, I've discovered that depot_tools to build chrome and chrome on
ozone including GYP and not sure about ninja requires GTK2 for some reason
so I am again back to the same problem: I really would like to build in the
machine itself without polluting the env with anything X11 related ... how
come this is such strong dependency even to GYP ?

I wonder if anyone managed to manually build ozone/chromium without using
Chrome tools ... like some manual kilometric instruction on the how to and
what's really needed would be awesome, thanks!





On Wed, Jun 18, 2014 at 11:24 AM, Tiago Vignatti <
tiago.vignatti at linux.intel.com> wrote:

> It's not about Wayland per se that made VDA on Linux possible... in short,
> Chromium devs couldn't afford maintenance of different decoding libraries
> on Linux for different hw vendors so they preferred to only maintain
> whatever comes on ChromeOS and its devices:
>
> https://code.google.com/p/chromium/issues/detail?id=137247
>
> maybe I should blog about that and explain in more details.
>
> Tiago
>
>
> On 06/18/2014 03:12 PM, Yomi Ogunwumi wrote:
>
>> What made adding video decoding acceleration in Chromium on Wayland
>> possible?
>>
>> Would I be correct in guessing that Chromium on X11 doesn't have this
>> functionality?
>>
>> Yomi
>>
>> On Jun 17, 2014 9:36 AM, "Tiago Vignatti"
>> <tiago.vignatti at linux.intel.com <mailto:tiago.vignatti at linux.intel.com>>
>>
>> wrote:
>>
>>     yup, Ozone-Wayland enables a bunch of Chromium based targets
>>     including the Chromium Browser.
>>
>>     I have it daily running on my testing machines and the state is
>>     quite good, with most of expected functionalities in place. In fact
>>     yesterday I've added video decoding acceleration support (through
>>     libva) to it, so on this aspect Chromium on Linux is more advanced
>>     on Wayland than on X11 :)
>>
>>     You're welcome to join #ozone-wayland at freenode to chat with
>>     developers and other users.
>>
>>     Tiago
>>
>>     On 06/17/2014 05:23 AM, Caner Altinbasak wrote:
>>
>>         You can check ozone-wayland(wayland port of chromium):
>>         https://github.com/01org/__ozone-wayland
>>
>>         <https://github.com/01org/ozone-wayland>
>>
>>
>>         On 17 June 2014 01:34, Andrea Giammarchi
>>         <andrea.giammarchi at gmail.com <mailto:andrea.giammarchi at gmail.com>
>>         <mailto:andrea.giammarchi at __gmail.com
>>
>>         <mailto:andrea.giammarchi at gmail.com>>> wrote:
>>
>>              Hello There!
>>
>>              Apologies if this has been discussed for years now but I've
>>         managed
>>              to build weston on wayland without any X11 dependency and
>>         miserably
>>              failed to build a WebKitGTK even forcing GTK3 which does
>> build
>>              without problems on X-less systems.
>>
>>              in WebKit2 --gtk=3.0 GTK2 is still required for some reason
>>         behind
>>              the scene but GTK2 won't build without xorg libraries which
>>         is kinda
>>              a fail since I had to bring in X related stuff that messed
>>         up with
>>              all other autogen.sh builds ^_^
>>
>>              Qt would probably be my best bet but AFAIK they are moving
>> from
>>              QtWebkit to QtWebEngine and I'm not sure what's the status
>>         there (is
>>              this still the case?)
>>
>>              Long story short: I'd like to have a pure wayland browser
>>         but I've
>>              no idea how to build one without bringing X libraries in.
>>
>>              Can anyone please point me to a previous discussion or give
>>         me hints
>>              for a possible solution/repo/build instructions?
>>
>>              Thanks a lot and most of all, thanks for Wayland, it's
>>         amazing so far!
>>
>>              _________________________________________________
>>              wayland-devel mailing list
>>         wayland-devel at lists.__freedesktop.org
>>         <mailto:wayland-devel at lists.freedesktop.org>
>>              <mailto:wayland-devel at lists.__freedesktop.org
>>         <mailto:wayland-devel at lists.freedesktop.org>>
>>         http://lists.freedesktop.org/__mailman/listinfo/wayland-devel
>>         <http://lists.freedesktop.org/mailman/listinfo/wayland-devel>
>>
>>
>>
>>
>>         _________________________________________________
>>         wayland-devel mailing list
>>         wayland-devel at lists.__freedesktop.org
>>         <mailto:wayland-devel at lists.freedesktop.org>
>>         http://lists.freedesktop.org/__mailman/listinfo/wayland-devel
>>         <http://lists.freedesktop.org/mailman/listinfo/wayland-devel>
>>
>>
>>     _________________________________________________
>>     wayland-devel mailing list
>>     wayland-devel at lists.__freedesktop.org
>>     <mailto:wayland-devel at lists.freedesktop.org>
>>     http://lists.freedesktop.org/__mailman/listinfo/wayland-devel
>>
>>     <http://lists.freedesktop.org/mailman/listinfo/wayland-devel>
>>
>>
>>
>> _______________________________________________
>> wayland-devel mailing list
>> wayland-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/wayland-devel
>>
>>
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20140618/4ca33085/attachment.html>