--
You received this message because you are subscribed to the Google Groups "Ozone-Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ozone-dev+unsubscribe@chromium.org.
Le 12/10/2016 à 15:40, 'Kyle Charbonneau' via Ozone-Dev a écrit :
Does building Ozone wayland require any additional libraries? Running Ozone wayland does but if there are no build time dependencies then it might be possible to add ozone_platform_wayland=true to linux_chromium_chromeos_ozone_rel_ng. That would ensure the Ozone wayland compile doesn't get broken at least.
Hi Kyle, Yes, I think the minimum we want is to have ozone_platform_wayland=true so that at least the code is built. I think this requires installing the wayland development files. Also by default use_wayland_egl=true and I believe we do want to test EGL support too. So this requires installing additional wayland EGL development files. (BTW, an additional Ozone platform that we "unbreak" recently and that we might want to build is caca. You need ozone_platform_caca = true and also the caca development files.)
All of the tests on linux_chromium_chromeos_ozone_rel_ng run with --ozone-platform=headless right now. I've done a bit of work to make it possible to run tests using Ozone X11 but it's blocked right now. I'd imagine running tests using Ozone wayland isn't feasible. It would require a trybot with a wayland environment which we don't have.
I see. So obviously this will require more runtime libraries. Also you can also use weston (or even weston-launch) to run a Wayland environment, but I guess this will be a bit more config work on the buildbot. Probably, we should try and see the current status of existing Wayland tests before and come back to this later. Thanks,
Le 12/10/2016 à 15:40, 'Kyle Charbonneau' via Ozone-Dev a écrit :Does building Ozone wayland require any additional libraries? Running Ozone wayland does but if there are no build time dependencies then it might be possible to add ozone_platform_wayland=true to linux_chromium_chromeos_ozone_rel_ng. That would ensure the Ozone wayland compile doesn't get broken at least.Hi Kyle, Yes, I think the minimum we want is to have ozone_platform_wayland=true so that at least the code is built. I think this requires installing the wayland development files.
Also by default use_wayland_egl=true and I believe we do want to test EGL support too. So this requires installing additional wayland EGL development files.
(BTW, an additional Ozone platform that we "unbreak" recently and that we might want to build is caca. You need ozone_platform_caca = true and also the caca development files.)
All of the tests on linux_chromium_chromeos_ozone_rel_ng run with --ozone-platform=headless right now. I've done a bit of work to make it possible to run tests using Ozone X11 but it's blocked right now. I'd imagine running tests using Ozone wayland isn't feasible. It would require a trybot with a wayland environment which we don't have.I see. So obviously this will require more runtime libraries. Also you can also use weston (or even weston-launch) to run a Wayland environment, but I guess this will be a bit more config work on the buildbot.
Probably, we should try and see the current status of existing Wayland tests before and come back to this later.
For the sake of completeness, I think it is worth mentioning that
ozone_platform_wayland=true only builds for me when I use
use_sysroot=false.
Basically the sysroot lacks 'wayland-egl' installed:
Package wayland-egl was not found in the pkg-config search path.
Perhaps you should add the directory containing `wayland-egl.pc'
to the PKG_CONFIG_PATH environment variable
No package 'wayland-egl' found
For the sake of completeness, I think it is worth mentioning that
ozone_platform_wayland=true only builds for me when I use
use_sysroot=false.
Basically the sysroot lacks 'wayland-egl' installed:
> email to ozone-dev+unsubscribe@chromium.org.
--
--Antonio Gomes
You should file a bug and work with thomasanderson@ to get things updated and building.
-- Dirk
On Thu, Oct 13, 2016 at 2:17 PM, Robert Kroeger <rjkr...@chromium.org> wrote:
On Thursday, October 13, 2016, Antonio Gomes <toni...@gmail.com> wrote:
For the sake of completeness, I think it is worth mentioning that
ozone_platform_wayland=true only builds for me when I use
use_sysroot=false.
Basically the sysroot lacks 'wayland-egl' installed:
On 10/13/2016 02:26 PM, Dirk Pranke wrote:
Looks like the wayland-egl package doesn't exist on wheezy. Unfortunately that means building with use_sysroot=true is blocked on updating the sysroot to jessie, which is blocked on updating the builders from Precise to Trusty.You should file a bug and work with thomasanderson@ to get things updated and building.
-- Dirk
On Thu, Oct 13, 2016 at 2:17 PM, Robert Kroeger <rjkr...@chromium.org> wrote:
On Thursday, October 13, 2016, Antonio Gomes <toni...@gmail.com> wrote:
For the sake of completeness, I think it is worth mentioning that
ozone_platform_wayland=true only builds for me when I use
use_sysroot=false.
Basically the sysroot lacks 'wayland-egl' installed:
--
--Antonio Gomes
On Friday, October 14, 2016, Antonio Gomes <toni...@gmail.com> wrote:On Fri, Oct 14, 2016 at 2:00 AM, Frédéric Wang <fw...@igalia.com> wrote:
> Le 14/10/2016 à 03:42, 'Tom Anderson' via Ozone-Dev a écrit :
>> Ok I take this back. I've added the wayland dev files to the wheezy,
>> jessie, and precise sysroots. https://codereview.chromium.org/2415933004/
>>
>> I can build with use_ozone = true, ozone_platform_wayland=true,
>> target_os = "chromeos"
>>
>> However, desktop Linux builds are giving me some linker errors:
>
> Thank you everybody for the progress on this!
>
> @Tom: yes, chromeos is supported but desktop Linux is not yet. For the
> latter, you can currently build target "ozone" and there is a CL here to
> allow at least to build target "chrome":
>
> https://codereview.chromium.org/2408803002/
Thank you, Tom. It tested it locally, and ozone x11/wayland build
worked for both chromeos (ToT) and linux (with
https://codereview.chromium.org/2408803002/).
I believe once it https://codereview.chromium.org/2408803002/ gets
approved/merged, we should consider an extra non-chromeos ozone
buildbot (build only for now).My impression is that it's generally hard to find machine resources for CQ and builders for a new combination of build flags.
If we don't want to add a brand new builder/CQ stack, then I see two choices (but maybe I'm missing some?)* add ozone=true, ozone_x11=true, mus configuration to Linux Chrome and it runs in this mode when enabled by a command line flag.* add a new no-ash external-window mode to CrOS Chrome enabled by a sibling flag to --mash.It's not clear to me which of these is better. I think Antonio's current patch is better aligned with the second option. Ash would still get compiled in this case but (thanks to mustash) wouldn't necessarily need to execute. And when mustash is complete, CrOS Chrome and Linux Chrome ought to be almost entirely the same.
Rob.--
--Antonio Gomes
Hi all,
Just to follow-up on this:
* The wayland packages were added to sysroot in
https://codereview.chromium.org/2415933004 and the use_wayland_egl flag
removed in https://codereview.chromium.org/2431383002/
* The wayland platform is enabled by default in
https://codereview.chromium.org/2423833002/
So I believe the ozone chromeos try bot now builds the Wayland platform
and runs the existing tests. This will hopefully that reduce the number
of breakages we have encountered recently. I guess it would still be
nice to have some simple test running chrome in a Wayland environment,
but I understand it might not be so easy to setup.
I don't know if some people are interested in doing the same for the
caca platform that was discussed in this thread...
If so, it seems like the way to go would be to addan optional trybot configuration and a FYI builder to support a different build configuration until such time as wehad the single unified build.WDYT?
I wanted to provide an update on this thread. The Ozone Linux FYI builder went green for the first time last night.
I think the next step here is to add builders to the CQ and
the main waterfall. We would also want to try rebasing/landing
this CL
so we at least have something working on Ozone/Wayland. Also,
just as an FYI, Fedora 25 shipped yesterday, and it uses Wayland
by default.
I wanted to provide an update on this thread. The Ozone Linux FYI builder went green <https://build.chromium.org/p/chromium.fyi/builders/Ozone%20Linux?numbuilds=100> for the first time last night.Yeah! Thanks for your help on this!
I think the next step here is to add builders to the CQ and the main waterfall. We would also want to try rebasing/landing this CL <https://codereview.chromium.org/2027943002/> so we at least have something working on Ozone/Wayland. Also, just as an FYI, Fedora 25 shipped yesterday, and it uses Wayland by default.As discussed in a previous thread, it's not clear we want to follow the approach in this CL. Anyway, most of the work is now merged to be able to run some minimal chrome under Wayland. The only bit missing is about ash resources https://codereview.chromium.org/2485673002/. With that last patch, the following should work (maybe one need do something with https://chromium.googlesource.com/chromium/src/+/master/docs/linux_sandboxing.md):
The bot is compile-only for now, but we will definitely want
a linux_chromium_ozone_rel_ng in the future. Not sure exactly
how far-off that is atm.