[oe] [meta-qt5][PATCH] Add armv7ve in the supported MACHINES for qtwebengine
ARM CortexA7 is now defined as armv7ve. Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr <mailto:herve.jourd...@neuf.fr> > --- --- a/recipes-qt/qt5/qtwebengine_git.bb +++ b/recipes-qt/qt5/qtwebengine_git.bb @@ -47,6 +47,7 @@ COMPATIBLE_MACHINE_x86 = "(.*)" COMPATIBLE_MACHINE_x86-64 = "(.*)" COMPATIBLE_MACHINE_armv6 = "(.*)" COMPATIBLE_MACHINE_armv7a = "(.*)" +COMPATIBLE_MACHINE_armv7ve = "(.*)" inherit qmake5 inherit gettext PGP.sig Description: PGP signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browser][PATCH v2] chromium-wayland: update to 53.0.2785.14
Hi Jacobo, Khem, I'm traveling, so not able to access my build system for a few more days. I didn't check Julien's patch yet, so as long as it does at least what mine does, it should be OK for me. I'm open to whatever solution, whether I regenerate a patch or Jacobo integrates it in his. One thing I will do, though, is test the resulting recipe on my build platform, to see if it's still working in my configuration. Cheers, Herve > On 31 Jan 2017, at 03:04, Jacobo Aragunde Pérez <jaragu...@igalia.com> wrote: > >> On 30/01/17 19:36, Khem Raj wrote: >> On Mon, Jan 30, 2017 at 10:33 AM, Jacobo Aragunde Pérez >> <jaragu...@igalia.com> wrote: >>> Hi Khem Raj, >>> >>> sorry, I didn't understand your response. Do you prefer I send a new >>> version of the rebase patch, including Herve's fix? In that case, Herve, >>> I think I could use jbriance's upstream patch so you don't need to >>> generate it, if you all agree. I'd use the one that didn't get merged >>> [1], because we need the .gyp part too. >>> >>> Future rebases will require changes to use GN, at that point we should >>> probably get rid of this custom patch. That's a problem for another day, >>> though :) >> >> I was thinking both of Herve and you will send your patches >> independently after rework but if you can integrate both that would be >> wonderful. >> > > I definitely can, it's easy enough by picking Julien's diff from > Chromium code review. I've updated my patch and just triggered a build > to make sure everything is in place, it will compile overnight. I just > don't want to "steal" Herve's idea, so I'll wait for his blessing :) > > Best, > -- > Jacobo Aragunde > Software Engineer at Igalia > >>> >>> [1] https://codereview.chromium.org/2239833003/#ps1 >>> >>> Thank you all, >>> -- >>> Jacobo Aragunde >>> Software Engineer at Igalia >>> >>> >>>> On 29/01/17 02:13, Khem Raj wrote: >>>> Hi Herve >>>> >>>> Yes please send a V2 with suggested changes. >>>> >>>>> On Sat, Jan 28, 2017 at 7:05 AM, Herve Jourdain <herve.jourd...@neuf.fr> >>>>> wrote: >>>>> Hi Khem, >>>>> >>>>> Shall I generate a proper patch with the proper header? Or should Jacobo >>>>> add that to his patch? >>>>> I'm not even sure the patch is accepted on master yet. >>>>> >>>>> Cheers, >>>>> Herve >>>>> >>>>>> On 28 Jan 2017, at 01:51, Khem Raj <raj.k...@gmail.com> wrote: >>>>>> >>>>>> >>>>>> >>>>>> On 1/27/17 6:06 AM, Julien Brianceau (jbriance) wrote: >>>>>>>> -Original Message- >>>>>>>> From: openembedded-devel-boun...@lists.openembedded.org >>>>>>>> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of >>>>>>>> Khem Raj >>>>>>>> Sent: vendredi 27 janvier 2017 02:47 >>>>>>>> To: openembedded-devel@lists.openembedded.org >>>>>>>> Subject: Re: [oe] [meta-browser][PATCH v2] chromium-wayland: update to >>>>>>>> 53.0.2785.14 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> On 1/25/17 9:50 PM, Herve Jourdain wrote: >>>>>>>>> Hi Jacob, >>>>>>>>> >>>>>>>>> I've been able to compile chromium-wayland 53.0.2785.14 on >>>>>>>> RaspberryPi, with Wayland only (no X11), BUT I had to add an additional >>>>>>>> patch for it to work, or else I get an error in >>>>>>>> ui/events/keycodes/keyboard_code_conversion_xkb.cc. >>>>>>>>> I'm using VC4, which has a DRM/KMS interface (it seems that DRM >>>>>>>> interface is required by ozone-wayland), but this patch seems to not be >>>>>>>> related to RaspberryPi itself. >>>>>>>>> Basically, it seems that USE_XKBCOMMON is not defined when compiling >>>>>>>> keycodes. >>>>>>>>> >>>>>>>>> Is it something that you saw as well? Or do you have a different >>>>>>>> setting/experience? >>>>>>>>> >>>>>>>>> Just fo
Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds
Hi Jacobo, I'm using "master", and I do have patches for enabling armv7ve. But since they're needed only for raspberrypi, I planned to submit them only for meta-raspberrypi. If you think it could be useful in meta-browser, though, I can submit them there. Cheers, Herve -Original Message- From: Jacobo Aragunde Pérez [mailto:jaragu...@igalia.com] Sent: jeudi 2 février 2017 13:30 To: openembedded-devel@lists.openembedded.org Cc: ota...@ossystems.com.br; Herve Jourdain <herve.jourd...@neuf.fr> Subject: Re: [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds Thank you all for your reviews. This should be the last patch, it addresses Herve's problem when building on a Raspberry Pi. Unfortunately, I haven't been able to reproduce his problem myself, but this patch is actually a backport of an upstream patch, so it makes no harm in my opinion. Another question, are you using krogoth in you rpi build? I found problems with the declared architecture in releases newer than jethro, it is called "armv7ve" and chromium doesn't build because it expects "armv7a". We could use a patch if you have worked around this problem :) Thanks again, -- Jacobo Aragunde Software Engineer at Igalia On 02/02/17 13:17, Jacobo Aragunde Pérez wrote: > Certain build configurations enable a code path that includes > keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11 > environments because of a missing patch that is present upstream. > > This commit adds the missing patch from > https://codereview.chromium.org/2239833003 > > There are two versions of the patch in the code review URL above. > The first version fixes the problem both under the gyp and GN build > systems. That patch was rejected because gyp is considered deprecated > upstream. The second version fixes the problem only on GN and it was > merged upstream. We are picking the first version because our recipes > still use gyp to build. > > Signed-off-by: Jacobo Aragunde Pérez <jaragu...@igalia.com> > --- > .../chromium/chromium-wayland_53.0.2785.143.bb | 1 + > .../fix-non-x11-build-when-use_xkbcommon-1.patch | 51 > ++ > 2 files changed, 52 insertions(+) > create mode 100644 > recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch > > diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > index a75918b..ef913a7 100644 > --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > @@ -13,6 +13,7 @@ SRC_URI += "\ > file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \ > file://chromium-wayland/remove-Werror.patch \ > file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \ > +file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch > \ > ${@bb.utils.contains('PACKAGECONFIG', 'component-build', > 'file://component-build.gypi', '', d)} \ > ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', > 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', d)} > \ > " > diff --git > a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch > > b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch > new file mode 100644 > index 000..976ece9 > --- /dev/null > +++ > b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch > @@ -0,0 +1,51 @@ > +From: jbriance <jbria...@cisco.com> > +Subject: keycodes: Fix non-X11 build when use_xkbcommon=1 > + > +Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if > +use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading > +to the following compilation error in this case: > + > + In file included from > ../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0, > + from > ../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5: > + ../../ui/events/keycodes/xkb_keysym.h:19:19: fatal error: X11/X.h: No such > file or directory > + > +BUG=none > + > +Review-Url: https://codereview.chromium.org/2239833003 > +-- > + > +Index: ui/events/keycodes/BUILD.gn > +diff --git a/ui/events/keycodes/BUILD.gn b/ui/events/keycodes/BUILD.gn > +index > 4f2d47c2497d321332c79d0dd4e9007b50c319c7..716c7ed17cc8049ea65b95a5062e7c6e0adc6e48 > 100644 > +--- a/ui/events/keycodes/BUILD.gn > b/ui/events/keycodes/BUILD.gn > +@@ -17,6 +17,10 @@ source_set("xkb") { > + "//b
Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds
And BTW, I'll try to test your patch tomorrow - I'm back now, so I'll have access to my build server. -Original Message- From: Herve Jourdain [mailto:herve.jourd...@neuf.fr] Sent: jeudi 2 février 2017 13:47 To: 'Jacobo Aragunde Pérez' <jaragu...@igalia.com>; 'openembedded-devel@lists.openembedded.org' <openembedded-devel@lists.openembedded.org> Cc: 'ota...@ossystems.com.br' <ota...@ossystems.com.br> Subject: RE: [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds Hi Jacobo, I'm using "master", and I do have patches for enabling armv7ve. But since they're needed only for raspberrypi, I planned to submit them only for meta-raspberrypi. If you think it could be useful in meta-browser, though, I can submit them there. Cheers, Herve -Original Message- From: Jacobo Aragunde Pérez [mailto:jaragu...@igalia.com] Sent: jeudi 2 février 2017 13:30 To: openembedded-devel@lists.openembedded.org Cc: ota...@ossystems.com.br; Herve Jourdain <herve.jourd...@neuf.fr> Subject: Re: [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds Thank you all for your reviews. This should be the last patch, it addresses Herve's problem when building on a Raspberry Pi. Unfortunately, I haven't been able to reproduce his problem myself, but this patch is actually a backport of an upstream patch, so it makes no harm in my opinion. Another question, are you using krogoth in you rpi build? I found problems with the declared architecture in releases newer than jethro, it is called "armv7ve" and chromium doesn't build because it expects "armv7a". We could use a patch if you have worked around this problem :) Thanks again, -- Jacobo Aragunde Software Engineer at Igalia On 02/02/17 13:17, Jacobo Aragunde Pérez wrote: > Certain build configurations enable a code path that includes > keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11 > environments because of a missing patch that is present upstream. > > This commit adds the missing patch from > https://codereview.chromium.org/2239833003 > > There are two versions of the patch in the code review URL above. > The first version fixes the problem both under the gyp and GN build > systems. That patch was rejected because gyp is considered deprecated > upstream. The second version fixes the problem only on GN and it was > merged upstream. We are picking the first version because our recipes > still use gyp to build. > > Signed-off-by: Jacobo Aragunde Pérez <jaragu...@igalia.com> > --- > .../chromium/chromium-wayland_53.0.2785.143.bb | 1 + > .../fix-non-x11-build-when-use_xkbcommon-1.patch | 51 > ++ > 2 files changed, 52 insertions(+) > create mode 100644 > recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-w > hen-use_xkbcommon-1.patch > > diff --git > a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > index a75918b..ef913a7 100644 > --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb > @@ -13,6 +13,7 @@ SRC_URI += "\ > file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \ > file://chromium-wayland/remove-Werror.patch \ > > file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \ > + > + file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch > + \ > ${@bb.utils.contains('PACKAGECONFIG', 'component-build', > 'file://component-build.gypi', '', d)} \ > ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', > 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', d)} > \ " > diff --git > a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build > -when-use_xkbcommon-1.patch > b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build > -when-use_xkbcommon-1.patch > new file mode 100644 > index 000..976ece9 > --- /dev/null > +++ b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-b > +++ uild-when-use_xkbcommon-1.patch > @@ -0,0 +1,51 @@ > +From: jbriance <jbria...@cisco.com> > +Subject: keycodes: Fix non-X11 build when use_xkbcommon=1 > + > +Since M51, ui/events/keycodes/xkb_keysym.h follows X11 path, even if > +use_xkbcommon=1 is set because USE_XKBCOMMON is not defined, leading > +to the following compilation error in this case: > + > + In file included from > ../../ui/events/keycodes/keyboard_code_conversion_xkb.h:12:0, > + from > ../../ui/events/keycodes/keyboard_code_conversion_xkb.cc:5: > + ../../ui/events/ke
Re: [oe] [meta-browser][PATCH] chromium-wayland: fix compilation problem on non-X11 builds
Hi Jacobo, OK, I will send those extra patched to the meta-raspberry list tomorrow then. Cheers, Herve > On 2 Feb 2017, at 21:28, Jacobo Aragunde Pérez <jaragu...@igalia.com> wrote: > >> On 02/02/17 13:46, Herve Jourdain wrote: >> Hi Jacobo, >> >> I'm using "master", and I do have patches for enabling armv7ve. But since >> they're needed only for raspberrypi, I planned to submit them only for >> meta-raspberrypi. >> If you think it could be useful in meta-browser, though, I can submit them >> there. >> > > Oh, I think sending them to meta-rpi would be good enough, thank you! > I'll keep an eye on it. > > Best regards, > -- > Jacobo Aragunde > Software Engineer at Igalia > > >> -Original Message- >> From: Jacobo Aragunde Pérez [mailto:jaragu...@igalia.com] >> Sent: jeudi 2 février 2017 13:30 >> To: openembedded-devel@lists.openembedded.org >> Cc: ota...@ossystems.com.br; Herve Jourdain <herve.jourd...@neuf.fr> >> Subject: Re: [meta-browser][PATCH] chromium-wayland: fix compilation problem >> on non-X11 builds >> >> Thank you all for your reviews. This should be the last patch, it addresses >> Herve's problem when building on a Raspberry Pi. >> >> Unfortunately, I haven't been able to reproduce his problem myself, but this >> patch is actually a backport of an upstream patch, so it makes no harm in my >> opinion. >> >> Another question, are you using krogoth in you rpi build? I found problems >> with the declared architecture in releases newer than jethro, it is called >> "armv7ve" and chromium doesn't build because it expects "armv7a". We could >> use a patch if you have worked around this problem :) >> >> Thanks again, >> -- >> Jacobo Aragunde >> Software Engineer at Igalia >> >> >>> On 02/02/17 13:17, Jacobo Aragunde Pérez wrote: >>> Certain build configurations enable a code path that includes >>> keyboard_code_conversion_xkb.cc, but it eventually fails in non-X11 >>> environments because of a missing patch that is present upstream. >>> >>> This commit adds the missing patch from >>> https://codereview.chromium.org/2239833003 >>> >>> There are two versions of the patch in the code review URL above. >>> The first version fixes the problem both under the gyp and GN build >>> systems. That patch was rejected because gyp is considered deprecated >>> upstream. The second version fixes the problem only on GN and it was >>> merged upstream. We are picking the first version because our recipes >>> still use gyp to build. >>> >>> Signed-off-by: Jacobo Aragunde Pérez <jaragu...@igalia.com> >>> --- >>> .../chromium/chromium-wayland_53.0.2785.143.bb | 1 + >>> .../fix-non-x11-build-when-use_xkbcommon-1.patch | 51 >>> ++ >>> 2 files changed, 52 insertions(+) >>> create mode 100644 >>> recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch >>> >>> diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb >>> b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb >>> index a75918b..ef913a7 100644 >>> --- a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb >>> +++ b/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb >>> @@ -13,6 +13,7 @@ SRC_URI += "\ >>> file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \ >>> file://chromium-wayland/remove-Werror.patch \ >>> file://chromium-wayland/guard-x11_desktop_handler-inclusion.patch \ >>> + >>> file://chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch \ >>> ${@bb.utils.contains('PACKAGECONFIG', 'component-build', >>> 'file://component-build.gypi', '', d)} \ >>> ${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', >>> 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', >>> d)} \ >>> " >>> diff --git >>> a/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch >>> >>> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch >>> new file mode 100644 >>> index 000..976ece9 >>> --- /dev/null >>> +++ >>> b/recipes-browser/chromium/chromium/chromium-wayland/fix-non-x11-build-when-use_xkbcommon-1.patch &
Re: [oe] ***SPAM*** Re: [meta-browser][PATCH v2] chromium-wayland: update to 53.0.2785.14
Hi Khem, Shall I generate a proper patch with the proper header? Or should Jacobo add that to his patch? I'm not even sure the patch is accepted on master yet. Cheers, Herve > On 28 Jan 2017, at 01:51, Khem Raj <raj.k...@gmail.com> wrote: > > > > On 1/27/17 6:06 AM, Julien Brianceau (jbriance) wrote: >>> -Original Message- >>> From: openembedded-devel-boun...@lists.openembedded.org >>> [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of >>> Khem Raj >>> Sent: vendredi 27 janvier 2017 02:47 >>> To: openembedded-devel@lists.openembedded.org >>> Subject: Re: [oe] [meta-browser][PATCH v2] chromium-wayland: update to >>> 53.0.2785.14 >>> >>> >>> >>>> On 1/25/17 9:50 PM, Herve Jourdain wrote: >>>> Hi Jacob, >>>> >>>> I've been able to compile chromium-wayland 53.0.2785.14 on >>> RaspberryPi, with Wayland only (no X11), BUT I had to add an additional >>> patch for it to work, or else I get an error in >>> ui/events/keycodes/keyboard_code_conversion_xkb.cc. >>>> I'm using VC4, which has a DRM/KMS interface (it seems that DRM >>> interface is required by ozone-wayland), but this patch seems to not be >>> related to RaspberryPi itself. >>>> Basically, it seems that USE_XKBCOMMON is not defined when compiling >>> keycodes. >>>> >>>> Is it something that you saw as well? Or do you have a different >>> setting/experience? >>>> >>>> Just for reference, here is the patch I need (right now, I'm >>> triggering it from meta-raspberrypi, but I believe it may be needed in >>> meta-browser). >>>> >>>> --- a/ui/events/keycodes/events_keycodes.gyp2017-01-23 >>> 19:12:01.767271256 +0800 >>>> +++ b/ui/events/keycodes/events_keycodes.gyp2017-01-23 >>> 19:12:11.503048216 +0800 >>>> @@ -21,6 +21,9 @@ >>>> 'scoped_xkb.h', >>>> 'xkb_keysym.h', >>>> ], >>>> + 'defines': [ >>>> +'USE_XKBCOMMON', >>> >>> This seems fine to me. It should also be proposed upstream as well I >>> think. >>> >> >> For the record, I've already tried to upstream a similar change (see Patch >> Set 1 of review https://codereview.chromium.org/2239833003/), but only the >> GN part has been accepted as gyp support has been removed in Chromium 54. >> > > thats we should make a note of this in patch header. We will have to > remove it or replace it as well when we upgrade chromium. >> Julien >> > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browser][PATCH v2] chromium-wayland: update to 53.0.2785.14
Hi Jacob, I've been able to compile chromium-wayland 53.0.2785.14 on RaspberryPi, with Wayland only (no X11), BUT I had to add an additional patch for it to work, or else I get an error in ui/events/keycodes/keyboard_code_conversion_xkb.cc. I'm using VC4, which has a DRM/KMS interface (it seems that DRM interface is required by ozone-wayland), but this patch seems to not be related to RaspberryPi itself. Basically, it seems that USE_XKBCOMMON is not defined when compiling keycodes. Is it something that you saw as well? Or do you have a different setting/experience? Just for reference, here is the patch I need (right now, I'm triggering it from meta-raspberrypi, but I believe it may be needed in meta-browser). --- a/ui/events/keycodes/events_keycodes.gyp2017-01-23 19:12:01.767271256 +0800 +++ b/ui/events/keycodes/events_keycodes.gyp2017-01-23 19:12:11.503048216 +0800 @@ -21,6 +21,9 @@ 'scoped_xkb.h', 'xkb_keysym.h', ], + 'defines': [ +'USE_XKBCOMMON', + ], }, ], 'conditions': [ Cheers, Herve -Original Message- From: openembedded-devel-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Jacobo Aragunde Pérez Sent: mercredi 25 janvier 2017 16:07 To: openembedded-devel@lists.openembedded.org Cc: ota...@ossystems.com.br Subject: [oe] [meta-browser][PATCH v2] chromium-wayland: update to 53.0.2785.14 That is the latest version of Chromium that has been made work with the Ozone-Wayland project. Patches have been rebased and configure flags were changed because existing ones were causing conflicts in the new version. An extra patch was added to prevent the build from failing when building without X11 libs present due to an unnecessary inclusion. Signed-off-by: Jacobo Aragunde Pérez--- .../chromium/chromium-wayland_48.0.2548.0.bb | 36 - .../chromium/chromium-wayland_53.0.2785.143.bb | 37 + .../0011-Replace-readdir_r-with-readdir.patch | 88 +- .../add_missing_stat_h_include.patch | 2 +- .../guard-x11_desktop_handler-inclusion.patch | 13 .../chromium/chromium-wayland/remove-Werror.patch | 66 ...3-Remove-hard-coded-values-for-CC-and-CXX.patch | 11 ++- 7 files changed, 108 insertions(+), 145 deletions(-) delete mode 100644 recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb create mode 100644 recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb create mode 100644 recipes-browser/chromium/chromium/chromium-wayland/guard-x11_desktop_handler-inclusion.patch diff --git a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb b/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb deleted file mode 100644 index 0db8f7d..000 --- a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb +++ /dev/null @@ -1,36 +0,0 @@ -CHROMIUM_ENABLE_WAYLAND = "1" - -include chromium-browser.inc - -DEPENDS += "wayland libxkbcommon" - -SRC_URI += "\ -file://chromium-wayland/add_missing_stat_h_include.patch \ -file://0003-Remove-hard-coded-values-for-CC-and-CXX.patch \ -file://0004-Create-empty-i18n_process_css_test.html-file-to-avoi.patch \ -file://0005-Override-root-filesystem-access-restriction.patch \ - file://chromium-wayland/0007-Workaround-for-glib-related-build-error-with-ozone-w.patch \ -file://chromium-wayland/0011-Replace-readdir_r-with-readdir.patch \ -file://chromium-wayland/remove-Werror.patch \ -${@bb.utils.contains('PACKAGECONFIG', 'component-build', 'file://component-build.gypi', '', d)} \ -${@bb.utils.contains('PACKAGECONFIG', 'ignore-lost-context', 'file://0001-Remove-accelerated-Canvas-support-from-blacklist.patch', '', d)} \ -" - -LIC_FILES_CHKSUM = "file://LICENSE;md5=0fca02217a5d49a14dfe2d11837bb34d" -SRC_URI[md5sum] = "0534981cc21efcd11e64b67b85854420" -SRC_URI[sha256sum] = "4ca4e2adb340b3fb4d502266ad7d6bda45fa3519906dbf63cce11a63f680dbc8" - -OZONE_WAYLAND_GIT_BRANCH = "Milestone-SouthSister" -OZONE_WAYLAND_GIT_SRCREV = "c605505044af3345a276abbd7c29fd53db1dea40" - -SRC_URI += "git://github.com/01org/ozone-wayland.git;destsuffix=${OZONE_WAYLAND_GIT_DESTSUFFIX};branch=${OZONE_WAYLAND_GIT_BRANCH};rev=${OZONE_WAYLAND_GIT_SRCREV} file://chromium-wayland/0006-Remove-GBM-support-from-wayland.gyp.patch" - -# Component build is unsupported in ozone-wayland for Chromium 48 -python() { -if not bb.utils.contains('DISTRO_FEATURES', 'wayland', True, False, d): -raise bb.parse.SkipPackage("Wayland is not available") -if bb.utils.contains('PACKAGECONFIG', 'component-build', True, False, d): -bb.fatal("Chromium 48 Wayland version cannot be built in component-mode") -} - -CHROMIUM_WAYLAND_GYP_DEFINES = "use_ash=1 use_aura=1 chromeos=0 use_ozone=1 use_xkbcommon=1" diff --git a/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb
[oe] [meta-qt5][PATCH] Minor improvements: configure complains it can't find oe-device-extra.pri, and add libxkbcommon in the dependencies
During configure, it complains it can't find oe-device-extra.pri, but it doesn't result in any error. Fix it, though, just in case. In qtwayland, xkb should be optional, but it's not for the moment, so add it to the dependencies. Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr> --- recipes-qt/qt5/qtbase_git.bb| 3 +++ recipes-qt/qt5/qtwayland_git.bb | 1 + 2 files changed, 4 insertions(+) diff --git a/recipes-qt/qt5/qtbase_git.bb b/recipes-qt/qt5/qtbase_git.bb index 6541973..258c7ed 100644 --- a/recipes-qt/qt5/qtbase_git.bb +++ b/recipes-qt/qt5/qtbase_git.bb @@ -173,6 +173,9 @@ do_configure() { ln -sf ${OE_QMAKE_QMAKE_ORIG} ${B}/bin/qmake fi +# Avoid qmake error "Cannot read [...]/usr/lib/qt5/mkspecs/oe-device-extra.pri: No such file or directory" during configuration +touch ${S}/mkspecs/oe-device-extra.pri + ${S}/configure -v \ -opensource -confirm-license \ -sysroot ${STAGING_DIR_TARGET} \ diff --git a/recipes-qt/qt5/qtwayland_git.bb b/recipes-qt/qt5/qtwayland_git.bb index e315924..51421d5 100644 --- a/recipes-qt/qt5/qtwayland_git.bb +++ b/recipes-qt/qt5/qtwayland_git.bb @@ -18,6 +18,7 @@ LIC_FILES_CHKSUM = " \ #FIXME: xkb should be optional; we add it here to fix the build error without it # (https://bugreports.qt.io/browse/QTBUG-54851) +DEPENDS += "libxkbcommon" PACKAGECONFIG ?= " \ compositor-api \ wayland-egl \ -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ***SPAM*** Re: [meta-qt5][PATCH] Minor improvements: configure complains it can't find oe-device-extra.pri, and add libxkbcommon in the dependencies
Hi Khem, It seems not, since I disabled X11. Only libxkbcommon is needed, and it doesn't pull the whole X11 AFAIK. Cheers, Herve -Original Message- From: openembedded-devel-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Khem Raj Sent: vendredi 20 janvier 2017 07:52 To: openembeded-devel <openembedded-devel@lists.openembedded.org> Subject: ***SPAM*** Re: [oe] [meta-qt5][PATCH] Minor improvements: configure complains it can't find oe-device-extra.pri, and add libxkbcommon in the dependencies On Thu, Jan 19, 2017 at 5:07 AM, Herve Jourdain <herve.jourd...@neuf.fr> wrote: > During configure, it complains it can't find oe-device-extra.pri, but it doesn't result in any error. Fix it, though, just in case. > In qtwayland, xkb should be optional, but it's not for the moment, so add it to the dependencies. Does this also mean that now we need to enable x11 along with wayland for distro features ? > > Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr> > --- > recipes-qt/qt5/qtbase_git.bb| 3 +++ > recipes-qt/qt5/qtwayland_git.bb | 1 + > 2 files changed, 4 insertions(+) > > diff --git a/recipes-qt/qt5/qtbase_git.bb > b/recipes-qt/qt5/qtbase_git.bb index 6541973..258c7ed 100644 > --- a/recipes-qt/qt5/qtbase_git.bb > +++ b/recipes-qt/qt5/qtbase_git.bb > @@ -173,6 +173,9 @@ do_configure() { > ln -sf ${OE_QMAKE_QMAKE_ORIG} ${B}/bin/qmake > fi > > +# Avoid qmake error "Cannot read [...]/usr/lib/qt5/mkspecs/oe-device-extra.pri: No such file or directory" during configuration > +touch ${S}/mkspecs/oe-device-extra.pri > + > ${S}/configure -v \ > -opensource -confirm-license \ > -sysroot ${STAGING_DIR_TARGET} \ diff --git > a/recipes-qt/qt5/qtwayland_git.bb b/recipes-qt/qt5/qtwayland_git.bb > index e315924..51421d5 100644 > --- a/recipes-qt/qt5/qtwayland_git.bb > +++ b/recipes-qt/qt5/qtwayland_git.bb > @@ -18,6 +18,7 @@ LIC_FILES_CHKSUM = " \ > > #FIXME: xkb should be optional; we add it here to fix the build error without it > # (https://bugreports.qt.io/browse/QTBUG-54851) > +DEPENDS += "libxkbcommon" > PACKAGECONFIG ?= " \ > compositor-api \ > wayland-egl \ > -- > 2.7.4 > > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 0/1] v4l-utils: add support for "native" build
Herve Jourdain (1): Add support for "native" build (dvb-format-convert can be used in other packages, for instance) PARALLEL_MAKE is disabled for native because of a race condition between libv4l2 and v4l2convert when installing (because of relinking needed for both) meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb | 3 +++ 1 file changed, 3 insertions(+) -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-multimedia][PATCH 0/1] dvb-apps: fix recipe, and update to the latest version
Fixed error "GNU_HASH not present" Fixed dvb-scan-data package Fixed the VERSION_FILE (used to check the dvb api version) to the one used for the target (by default, it uses the one on the host) Updated to the "latest" version (2014/03/22) The latest version suppressed the original scan tables (not maintained anymore), so fetch and install the latest ones (using dvb api v3 format)(introduces a dependency on v4l-utils-native) Herve Jourdain (1): Fix recipe, and update to the latest version .../recipes-dvb/dvb-apps/dvb-apps_1.1.1.bb | 26 ++ 1 file changed, 22 insertions(+), 4 deletions(-) -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-multimedia][PATCH 1/1] dvb-apps: fix recipe, and update to the latest version
Fixed error "GNU_HASH not present" Fixed dvb-scan-data package Fixed the VERSION_FILE (used to check the dvb api version) to the one used for the target (by default, it uses the one on the host) Updated to the "latest" version (2014/03/22) The latest version suppressed the original scan tables (not maintained anymore), so fetch and install the latest ones (using dvb api v3 format)(introduces a dependency on v4l-utils-native) Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr> --- .../recipes-dvb/dvb-apps/dvb-apps_1.1.1.bb | 26 ++ 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/meta-multimedia/recipes-dvb/dvb-apps/dvb-apps_1.1.1.bb b/meta-multimedia/recipes-dvb/dvb-apps/dvb-apps_1.1.1.bb index d9ee439..0b4b72d 100644 --- a/meta-multimedia/recipes-dvb/dvb-apps/dvb-apps_1.1.1.bb +++ b/meta-multimedia/recipes-dvb/dvb-apps/dvb-apps_1.1.1.bb @@ -4,20 +4,38 @@ SUMMARY = "Linux DVB API applications and utilities" LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe" -SRC_URI = "hg://linuxtv.org/hg;module=dvb-apps;protocol=http" -SRCREV = "3fc7dfa68484" +DEPENDS = "v4l-utils-native" + +SRC_URI = " \ +hg://linuxtv.org/hg;module=dvb-apps;protocol=http;name=apps \ + git://linuxtv.org/git/dtv-scan-tables.git;protocol=http;destsuffix=dvb-apps/initial-scan-tables;name=scantables \ + " +SRCREV_apps = "3d43b280298c" +SRCREV_scantables = "ceb11833b35f05813b1f0397a60e0f3b99430aab" +SRCREV_FORMAT = "apps_scantables" S = "${WORKDIR}/${BPN}" +TARGET_CC_ARCH += "${LDFLAGS}" +EXTRA_OEMAKE = "VERSION_FILE='${STAGING_INCDIR}/linux/dvb/version.h'" + do_configure() { sed -i -e s:/usr/include:${STAGING_INCDIR}:g util/av7110_loadkeys/generate-keynames.sh } +do_compile_append() { +# dvb-apps only support DVBAPI v3, so generate them from the DVBAPI v5 downloaded files +make -C initial-scan-tables clean +make -C initial-scan-tables dvbv3 +} + do_install() { make DESTDIR=${D} install +# dvb-apps only support DVBAPI v3, so only install the generated DVBAPI v3 files +make -C initial-scan-tables DATADIR=${D}/${datadir} DVBV3DIR=dvb install_v3 + install -d ${D}/${bindir} install -d ${D}/${docdir}/dvb-apps -install -d ${D}/${docdir}/dvb-apps/scan install -d ${D}/${docdir}/dvb-apps/szap chmod a+rx ${D}/${libdir}/*.so* @@ -89,7 +107,7 @@ FILES_dvbnet-dbg = "${bindir}/.debug/dvbnet" FILES_dvb-scan = "${bindir}/*scan " FILES_dvb-scan-dbg = "${bindir}/.debug/*scan" -FILES_dvb-scan-data = "${docdir}/dvb-apps/scan" +FILES_dvb-scan-data = "${datadir}/dvb" FILES_dvb-azap = "${bindir}/azap" FILES_dvb-azap-dbg = "${bindir}/.debug/azap" -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH 1/1] v4l-utils: add support for "native" build
Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr> --- meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb b/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb index 6148695..b9732fe 100644 --- a/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb +++ b/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb @@ -43,3 +43,6 @@ FILES_libv4l-dbg += "${libdir}/libv4l/.debug ${libdir}/libv4l/plugins/.debug" FILES_libv4l-dev += "${includedir} ${libdir}/pkgconfig \ ${libdir}/libv4l*${SOLIBSDEV} ${libdir}/*.la \ ${libdir}/v4l*${SOLIBSDEV} ${libdir}/libv4l/*.la ${libdir}/libv4l/plugins/*.la" + +PARALLEL_MAKE_class-native = "" +BBCLASSEXTEND = "native" -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ***SPAM*** Re: [meta-oe][PATCH 1/1] v4l-utils: add support for "native" build
Hi Khem, Well, I guess I didn't really have the time then, so I went for the fastest solution available... But you're right, I'll try fixing the makefile, and post a V2. I believe I should have time for that in 1 or 2 days. Cheers, Herve -Original Message- From: openembedded-devel-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Khem Raj Sent: mercredi 19 octobre 2016 07:44 To: openembeded-devel <openembedded-devel@lists.openembedded.org> Subject: ***SPAM*** Re: [oe] [meta-oe][PATCH 1/1] v4l-utils: add support for "native" build On Tue, Oct 18, 2016 at 1:10 AM, Herve Jourdain <herve.jourd...@neuf.fr> wrote: > Signed-off-by: Herve Jourdain <herve.jourd...@neuf.fr> > --- > meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb b/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb > index 6148695..b9732fe 100644 > --- a/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb > +++ b/meta-oe/recipes-multimedia/v4l2apps/v4l-utils_1.10.1.bb > @@ -43,3 +43,6 @@ FILES_libv4l-dbg += "${libdir}/libv4l/.debug ${libdir}/libv4l/plugins/.debug" > FILES_libv4l-dev += "${includedir} ${libdir}/pkgconfig \ > ${libdir}/libv4l*${SOLIBSDEV} ${libdir}/*.la \ > ${libdir}/v4l*${SOLIBSDEV} ${libdir}/libv4l/*.la ${libdir}/libv4l/plugins/*.la" > + > +PARALLEL_MAKE_class-native = "" you seem to have root casued it. Then why not fix the Makefile instead > +BBCLASSEXTEND = "native" > -- > 2.7.4 > > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] ***SPAM*** [PATCH] chromium: enable aarch64 support
Hi, And in more recent / GN based versions of Chromium, no specific patch is even needed, as aarch64 is "natively" supported by the codebase. I guess recipes for those will come soon, since it seems several different persons/groups came with their own flavor of GN build... Cheers, Herve -Original Message- From: openembedded-devel-boun...@lists.openembedded.org [mailto:openembedded-devel-boun...@lists.openembedded.org] On Behalf Of Andrey Konovalov Sent: vendredi 7 avril 2017 20:57 To: openembedded-devel@lists.openembedded.org Subject: ***SPAM*** [oe] [PATCH] chromium: enable aarch64 support Tested by running: - chromium-wayland on HiKey - chromium on dragonboard-410c Signed-off-by: Andrey Konovalov--- recipes-browser/chromium/chromium.inc | 1 + recipes-browser/chromium/files/aarch64/include.gypi | 6 ++ recipes-browser/chromium/files/aarch64/oe-defaults.gypi | 15 +++ 3 files changed, 22 insertions(+) create mode 100644 recipes-browser/chromium/files/aarch64/include.gypi create mode 100644 recipes-browser/chromium/files/aarch64/oe-defaults.gypi diff --git a/recipes-browser/chromium/chromium.inc b/recipes-browser/chromium/chromium.inc index 60edccb..c0c3b94 100644 --- a/recipes-browser/chromium/chromium.inc +++ b/recipes-browser/chromium/chromium.inc @@ -7,6 +7,7 @@ COMPATIBLE_MACHINE_x86-64 = "(.*)" COMPATIBLE_MACHINE_armv6 = "(.*)" COMPATIBLE_MACHINE_armv7a = "(.*)" COMPATIBLE_MACHINE_armv7ve = "(.*)" +COMPATIBLE_MACHINE_aarch64 = "(.*)" # The build type defaults to Release. If you want a Debug build, you can set # the variable CHROMIUM_BUILD_TYPE to "Debug" in your conf/local.conf file. diff --git a/recipes-browser/chromium/files/aarch64/include.gypi b/recipes-browser/chromium/files/aarch64/include.gypi new file mode 100644 index 000..ad0347a --- /dev/null +++ b/recipes-browser/chromium/files/aarch64/include.gypi @@ -0,0 +1,6 @@ +{ + 'variables': { +# Configure for aarch64 compilation +'target_arch': 'arm64', + }, +} diff --git a/recipes-browser/chromium/files/aarch64/oe-defaults.gypi b/recipes-browser/chromium/files/aarch64/oe-defaults.gypi new file mode 100644 index 000..27e1cfe --- /dev/null +++ b/recipes-browser/chromium/files/aarch64/oe-defaults.gypi @@ -0,0 +1,15 @@ +{ + 'variables': { +'use_system_bzip2': 1, +'disable_nacl': 1, +'proprietary_codecs': 1, +'v8_use_snapshot': 1, +'use_system_ffmpeg': 0, +'linux_use_tcmalloc': 0, +'linux_link_kerberos': 0, +'use_kerberos': 0, +'use_cups': 0, +'use_gnome_keyring': 0, +'linux_link_gnome_keyring': 0 + }, +} -- 2.1.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel