Highlights of this upgrade:
* tinyproxy binary is not installed to /usr/sbin now.
* removed a deprecated configure parameter.
* reworked disable-documentation.patch.
Signed-off-by: Jacobo Aragunde Pérez
---
.../tinyproxy/disable-documentation.patch | 44
Hi all,
I noticed a warning in the logs after having sent the patch. Will post a
new version. Sorry for the noise!
Best,
--
Jacobo Aragunde
Software Engineer at Igalia
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
h
Signed-off-by: Jacobo Aragunde Pérez
---
.../tinyproxy/disable-documentation.patch | 44 +++---
.../tinyproxy/tinyproxy/tinyproxy.service | 2 +-
.../{tinyproxy_1.8.4.bb => tinyproxy_1.10.0.bb}| 4 +-
3 files changed, 26 insertions(+), 24 deleti
Hi!
On 15/01/18 23:14, Bhargava Sreekantappa Gayathri wrote:
> Hello,
>
> Has anyone has been able to run chromium-x11 as root user? Is there a flag or
> config I can tweak before building chromium?
>
You should be able to run chromium as root with the runtime flag
`--no-sandbox`. No changes i
On 27/10/17 17:44, Trevor Woerner wrote:
> ...
> I was able to successfully build for the minnow board (x86_64), but
> when I tried building for the 32-bit variant for raspberrypi3 I got:
>
> | install: cannot stat 'swiftshader/libEGL.so': No such file or directory
>
> during the do_install s
On 27/10/17 10:49, Daniel Mack wrote:
>
> I'd like to give Chromium 62 a shot on arm64, but the recipes currently
> only support x11, is that correct? My platform is based on wayland, any
> plans on supporting that?
>
The problem is that upstream Chromium does not support Wayland natively
yet. T
Hi everyone,
I have several potential patches for Rafael's layer after having tried
several builds for different hardware. I'm sending individual mails to
discuss each of them.
The first one is pretty straightforward. It is just a backport of an
existing upstream chromium patch to fix a compilati
Hi all,
On 05/10/17 02:43, Trevor Woerner wrote:
> Hi Jocobo,
>
> Please have a look at
> https://github.com/rakuco/meta-crosswalk/tree/chromium61/recipes-browser/chromium
> from Raphael (CCed). It is an interesting and promising approach.
>
Indeed, I've been in touch with Raphael who has also
Hi Trevor,
I think you spent some time trying to get a more recent version of
Chromium for meta-browser but it's been difficult. I have booked some
time during the Web Engines Hackfest [1], happening now, to try to do this.
I recently learned about the usage of custom toolchains with GN, whis
are
Hi Trevor,
On 06/04/17 22:37, Trevor Woerner wrote:
> ...
> Currently I'm trying to figure out how to move past this version.
> After 53.0.2810.2 the current method OE uses to build chromium starts
> to fail because (as is my understanding) it was around this point that
> the chromium build switch
Aragunde Pérez
---
recipes-browser/chromium/chromium.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-browser/chromium/chromium.inc
b/recipes-browser/chromium/chromium.inc
index 0e7250e..e603af0 100644
--- a/recipes-browser/chromium/chromium.inc
+++ b/recipes-browser/chromium
On 23/02/17 01:41, Otavio Salvador wrote:
> On Wed, Feb 22, 2017 at 9:53 AM, Jacobo Aragunde Pérez
> wrote:
>> Chromium-wayland fails with:
>> http://errors.yoctoproject.org/Errors/Build/32356/
>>
>> Root cause seems to be ICU mixing host and target archi
Chromium-wayland fails with:
http://errors.yoctoproject.org/Errors/Build/32356/
Root cause seems to be ICU mixing host and target architectures,
same as in: https://bugreports.qt.io/browse/QTBUG-57705
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium.inc | 1 +
1
ds-up.
Best,
--
Jacobo Aragunde
Software Engineer at Igalia
> On Wed, Feb 15, 2017 at 7:17 PM, Jacobo Aragunde Pérez > wrote:
>
>> Hi everyone!
>>
>> The patch in this thread has been recently merged. Thanks for your review!
>>
>> On 02/02/17 16:33, Herve Jourdain
#x27;t found your patches
around in yocto ML and I would like to try them. May I be following the
wrong ML?
Thanks in advance,
--
Jacobo Aragunde
Software Engineer at Igalia
>> On 2 Feb 2017, at 21:28, Jacobo Aragunde Pérez wrote:
>>
>>> On 02/02/17 13:46, Herve Jourdain w
bo 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 upstre
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
roblem :)
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 missi
version because our recipes
still use gyp to build.
Signed-off-by: Jacobo Aragunde Pérez
---
.../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
Chromium and chromium-wayland recipes cannot share this patch any
more due to diverging code bases. We create a new version of the
patch only for chromium-wayland and revert the existing patch to
its previous state to be used by chromium recipe.
Signed-off-by: Jacobo Aragunde Pérez
g 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 wrote:
>>
>>> On 30/01/17 19:36, Khem Raj wrote
Chromium and chromium-wayland recipes cannot share this patch any
more due to diverging code bases. We create a new version of the
patch only for chromium-wayland and revert the existing patch to
its previous state.
Signed-off-by: Jacobo Aragunde Pérez
---
.../chromium/chromium
Hi Gary,
I think I know what happened here; now there must be different versions
of this patch for chromium and chromium-wayland. Let me send a fix in a
while, would you kindly try it?
Best,
--
Jacobo Aragunde
Software Engineer at Igalia
On 31/01/17 17:17, Gary Thomas wrote:
> poky/yocto: d4
On 30/01/17 19:36, Khem Raj wrote:
> On Mon, Jan 30, 2017 at 10:33 AM, Jacobo Aragunde Pérez
> 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
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], b
On 27/01/17 15:06, Julien Brianceau (jbriance) wrote:
>> ...
>> 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 ge
On 20/01/17 12:37, Carlos Rafael Giani wrote:
> Looks okay overall. A few details need to be addressed:
>
Thank you again for the review. I've sent a new version of the patch to
the ML, addressing your comments.
Best,
--
Jacobo Aragunde
Software Engineer at Igalia
--
__
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
eyond/
[2] http://frederic-wang.fr/chromium-on-r-car-m3.html
[3] http://frederic-wang.fr/analysis-of-ozone-wayland.html
Best,
--
Jacobo Aragunde
Software Engineer at Igalia
> On 2017-01-13 13:37, Jacobo Aragunde Pérez wrote:
>> That is the latest version of Chromium that has been
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
.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
b/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
It can be a source of problems, because you must have chosen the
correct recipe to build the wayland or x11 version of chromium.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium-browser.inc | 6 --
1 file changed, 6 deletions(-)
diff --git a/recipes-browser
Aragunde Pérez
---
recipes-browser/chromium/chromium_52.0.2743.76.bb | 8
1 file changed, 8 insertions(+)
diff --git a/recipes-browser/chromium/chromium_52.0.2743.76.bb
b/recipes-browser/chromium/chromium_52.0.2743.76.bb
index 14b519c..a3270e9 100644
--- a/recipes-browser/chromium
It can be a source of problems, because you must have chosen the
correct recipe to build the wayland or x11 version of chromium.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium-browser.inc | 6 --
1 file changed, 6 deletions(-)
diff --git a/recipes-browser
The chromium x11 recipe crashed when run with CHROMIUM_ENABLE_WAYLAND
enabled, because it missed some steps that are performed in the
chromium-wayland recipe. Doing this change, we eliminate one possible
failure point.
Also adds a check for x11 in DISTRO_FEATURES.
Signed-off-by: Jacobo Aragunde
.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
b/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
It can be a source of problems, because you must have chosen the
correct recipe to build the wayland or x11 version of chromium.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium-browser.inc | 6 --
1 file changed, 6 deletions(-)
diff --git a/recipes-browser
because it missed some steps that are performed in the
chromium-wayland recipe. We remove one possible failure point.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium_52.0.2743.76.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/recipes-browser/chromium
.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
b/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
On 17/11/16 19:09, Khem Raj wrote:
>
>
> On 11/17/16 9:34 AM, Jacobo Aragunde Pérez wrote:
>> It makes no sense to trigger a build of chromium-wayland and not
>> enable CHROMIUM_ENABLE_WAYLAND, so we are doing it directly in the
>> recipe now.
>>
>> We
It makes no sense to trigger a build of chromium-wayland and not
enable CHROMIUM_ENABLE_WAYLAND, so we are doing it directly in the
recipe now.
We are allowed to remove some conditionals, now we know the value of
the flag beforehand.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser
Running the chromium_*.bb recipe with CHROMIUM_ENABLE_WAYLAND on
was crashing because it missed some steps that are performed in the
chromium-wayland recipe. We remove one possible failure point.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium_52.0.2743.76.bb | 2
It can be a source of problems, because you must have chosen the
correct recipe to build the wayland or x11 version of chromium.
Signed-off-by: Jacobo Aragunde Pérez
---
recipes-browser/chromium/chromium-browser.inc | 6 --
1 file changed, 6 deletions(-)
diff --git a/recipes-browser
43 matches
Mail list logo
