I'm trying to create/integrate a recipe that builds Qt5.7 on a Architech
Hachiko (ARM) board.
This board is uniquely compatible with Poky DORA (for technical reasons, I
don't have the choice).
Using meta-qt5 is excluded.
Actually? I succeeded to build qt5.7 with the Poky SDK and I would li
On vendredi 3 février 2017 13:51:34 CET Bruce Ashfield wrote:
>
> I was able to merge branches with this patch applied to Morty.
>
> Cheers,
>
> Bruce
>
I've just successfully tested it on Morty myself. Works for me too, branches
are merged just like they were before !
Thank you
David
--
_
On 7 February 2017 at 11:05, Karim ATIKI wrote:
> Using meta-qt5 is excluded.
>
> But why not port meta-qt5 to dora?
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi Burt,
I tried.
But many errors raise that impact the "meta-hachiko" layer which is not
compatible at all with versions > Dora.
De : Burton, Ross
Envoyé : mardi 7 février 2017 12:44
À : Karim ATIKI
Cc : yocto
Objet : Re: [yocto] [dora] Compiling Qt 5.7 wi
On 2017-02-07 06:21 AM, David Vincent wrote:
On vendredi 3 février 2017 13:51:34 CET Bruce Ashfield wrote:
I was able to merge branches with this patch applied to Morty.
Cheers,
Bruce
I've just successfully tested it on Morty myself. Works for me too, branches
are merged just like they were
colleague asked me for a list of OE/YP recipes for monitoring system
performance/resource utilization/profiling, i'm unaware of any single
list that tracks that sort of thing so i'll just ask what people are
aware of. just off the top of my head:
* sysstat
* atop
* collectd
* netdata
* rrd
From: Leonardo Sandoval
This new command allows to fetch bundles (set of selected patches by the user)
and print them into the stdout. For the moment, bundles must be public
(otherwise
these wont be found)
Command line example:
openembedded-core$ git pw bundle newbundle --username lsandov1
Si
From: Leonardo Sandoval
This new command allows to fetch bundles (set of selected patches by the user)
and print them into the stdout. For the moment, bundles must be public
(otherwise
these wont be found)
Command line example:
openembedded-core$ git pw bundle newbundle --username lsandov1
Si
Attendees: Stephen, Armin, Stephano Sona, Ross, Joshua, Jussi, Saul, Sveinse,
Richard,
Agenda:
* Opens collection - 5 min (Stephen)
* Yocto Project status - 5 min (Stephen/team)
YP 2.3 M2 rc3 is in QA.
YP 2.3 M3 target cut off is Feb. 27th.
YP 2.2.1 should go into QA after YP 2.3 M2 is o
On 1 February 2017 at 20:28, Wilde, DonaldX wrote:
> Unfortunately, what happens is that somewhere along the line after the
> initial patch and compilation, something in our image gets radically
> corrupted. With IMAGE_INCLUDE += “iperf3” set, the image is corrupted.
> Horrible results occur incl
On 7 February 2017 at 17:42, Wilde, DonaldX wrote:
> My bad, Ross. I meant IMAGE_INSTALL. Must have been lexdysic the other
> day. J
>
>
In that case my guess was right: don't += it from your local.conf as you'll
wipe the default value away. Use _append (and remember the leading
whitespace as ap
Hi Jolley,
Cve-check tool fails on master and latest morty, I have created following bug
(Jussi is working on this):
Bug 11026 - cve-check: Error in executing cve-check-update
Some background info about this tool:
=
cve-check tool has been supported since the Morty r
Hi,
Easy question!
I would like to disable the /etc/version file from being installed to
the rootfs. How do I proceed? It looks hard-coded at first glance...?
Regards,
Marc
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.o
My bad, Ross. I meant IMAGE_INSTALL. Must have been lexdysic the other day. ☺
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Tuesday, February 7, 2017 10:34 AM
To: Wilde, DonaldX
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Installing iperf3 causes strange image corruption
On 1 Febr
As it happens, I learned to generate a statically linked binary that I could
load into NVRAM on our board so I could move forward and accomplish my work,
but I will take your advice and I believe you’ve told me enough that I can
learn to do what you say to do for the future work that I do. Once
Patch forms in series view do not pass selected patch id
as request element during a POST call, so no status/bundle
updates can be performed from such view.
This change includes the selected patch id as a request
element and pass it to POST call through a hidden input field.
[YOCTO #10973]
Signe
Current series view is missing a POST call, avoiding users to update
or edit patch status or bundles.
This change adds POST call to series view, including the target
patch id, which is taken from request context.
[YOCTO #10973]
Signed-off-by: Jose Lamego
---
patchwork/views/series.py | 83
These changes enable patch status updating, adding a patch to an existing
bundle and creating a new bundle from the series view.
[YOCTO #10973]
Changes in v2: Fixed javascript formatting and pep8 compliance.
Jose Lamego (2):
series.js: Get patch id and pass it to POST request
series.py: Add
Hi Marc,
On Tuesday, 7 February 2017 2:20:09 PM NZDT Marc Ferland wrote:
> I would like to disable the /etc/version file from being installed to
> the rootfs. How do I proceed? It looks hard-coded at first glance...?
It is hardcoded, however it would be trivial to delete it in a shell function
a
On Tue, Feb 7, 2017 at 3:31 PM, Robert P. J. Day wrote:
>
> colleague asked me for a list of OE/YP recipes for monitoring system
> performance/resource utilization/profiling, i'm unaware of any single
> list that tracks that sort of thing so i'll just ask what people are
> aware of. just off the
20 matches
Mail list logo
