Hi Michael,
On Thu, Sep 29, 2022 at 10:27 PM wrote:
>
> Hello,
>
> I have an application that is comprised of C++ and C code modules. I have two
> bitbake builds, prod and dev. The dev image builds 100% of the time. The
> difference between prod and dev, dev has debug tools, prod build the
Signed-off-by: Yi Zhao
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index d6f83c9..5673b73 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -17,7 +17,7 @@ BBFILE_PRIORITY_selinux = "5"
# cause compatibility issues
Signed-off-by: Jon Mason
---
meta-zephyr-bsp/conf/layer.conf | 4 ++--
meta-zephyr-core/conf/layer.conf | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta-zephyr-bsp/conf/layer.conf b/meta-zephyr-bsp/conf/layer.conf
index 507374f..cbbaafe 100644
---
Signed-off-by: Khem Raj
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index a2661f9..0e28857 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -14,7 +14,7 @@ BBFILE_PRIORITY_rockchip = "1"
# This should only be
Hello,
I work on OpenBMC and am having an issue with EXTRA_IMAGECMD:squashfs-xz.
There was a recent change pulled into OpenBMC in image_types.bbclass. In
the old file, IMAGE_CMD:squashfs-xz was defined directly:
IMAGE_CMD:squashfs-xz = "mksquashfs ${IMAGE_ROOTFS}
Hello,
I have an application that is comprised of C++ and C code modules. I have two
bitbake builds, prod and dev. The dev image builds 100% of the time. The
difference between prod and dev, dev has debug tools, prod build the main
application and attempts to include it in the image. I cannot
Hello,
I have an application that is comprised of C++ and C code modules. I have two
bitbake builds, prod and dev. The dev image builds 100% of the time. The
difference between prod and dev, dev has debug tools, prod build the main
application and attempts to include it in the image. I cannot
Thanks,
I'll run this against the builds where I developed the problematic
change. If everything keeps working, the choice is simple .. I'll
merge this and we can all keep moving.
If something breaks, I'll have a jumping point to try and reproduce
your issue and still keep all three working.
The strip_common_prefix function is changed in a way that they will
use the expanded path of the input argument.
There are some changes in the process_file function for the *.cfg files
only and not none for *.scc, *.patch and *defconfig.
This doesn't work for cases where we have the defconfig
Bruce Ashfield escreveu no dia quinta,
29/09/2022 à(s) 18:09:
> On Thu, Sep 29, 2022 at 12:55 PM Jose Quaresma
> wrote:
>
>> Hi Bruce,
>>
>> Bruce Ashfield escreveu no dia quinta,
>> 29/09/2022 à(s) 17:42:
>>
>>> If this broke another use case, send the details and I'll debug it here.
>>> But
On Thu, Sep 29, 2022 at 12:55 PM Jose Quaresma
wrote:
> Hi Bruce,
>
> Bruce Ashfield escreveu no dia quinta,
> 29/09/2022 à(s) 17:42:
>
>> If this broke another use case, send the details and I'll debug it here.
>> But these changes are required for some configurations, so I'm not going to
>>
Hi Bruce,
Bruce Ashfield escreveu no dia quinta,
29/09/2022 à(s) 17:42:
> If this broke another use case, send the details and I'll debug it here.
> But these changes are required for some configurations, so I'm not going to
> simply revert.
>
I've been trying to figure out why this is
If this broke another use case, send the details and I'll debug it here.
But these changes are required for some configurations, so I'm not going to
simply revert.
Bruce
On Thu, Sep 29, 2022 at 12:37 PM Jose Quaresma
wrote:
> This reverts commit 9320c2a1aaa085e94abd15ede0d93ffdab578e9d.
>
>
This reverts commit 9320c2a1aaa085e94abd15ede0d93ffdab578e9d.
The strip_common_prefix function is changed in a way that they will
use the expanded path of the input argument.
There are some changes in the process_file function for the *.cfg files
only and not none for *.scc, *.patch and
When process_file function fails the output of the processed script is show to
the user, some parsing is performed as well to look for common errors so we
can point to the right input file.
This can only be done when the scc_output_file have some valid content
otherwise it will show invalid
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage
*Attendees: *Steve Sakoman, Joshua Watt, Richard Purdie, Alexandre
Belloni, Stephen Jolley, Ross Burton, Tim Orling, Alexandre Belloni,
Bruce Ashfield
*ARs:*
N/A*
*
*Notes:
*
*
*
*Medium+ 4.1 Unassigned Enhancements/Bugs: *27 (Last
On Thu, Sep 29, 2022 at 11:30 AM Jon Mason wrote:
>
> zephyr-openthread-rcp support was recently added to
> nrf52840-mdk-usb-dongle and nrf52840dk-nrf52840. Add this to the
> targets for both machines, which necessitates adding a target entry
> for nrf52840-mdk-usb-dongle.
>
> Signed-off-by: Jon
zephyr-openthread-rcp support was recently added to
nrf52840-mdk-usb-dongle and nrf52840dk-nrf52840. Add this to the
targets for both machines, which necessitates adding a target entry
for nrf52840-mdk-usb-dongle.
Signed-off-by: Jon Mason
---
ci/nrf52840-mdk-usb-dongle.yml | 14 ++
On Wed, Sep 28, 2022 at 03:09:01PM +0200, philippe.co...@astrolabe.coop wrote:
> From: Philippe Coval
>
> This makerdiary board can be a fallback option for Oniro's gateway-blueprint
> I've been tested it myself along my single arduino-nano node
>
> Origin:
>
On Wed, Sep 28, 2022 at 02:27:26PM +0200, philippe.co...@astrolabe.coop wrote:
> From: Philippe Coval
>
> It was tested using zephyr-blinky and deployed manually using:
>
> udisksctl mount -b "/dev/disk/by-label'FRDM-KW41ZJ"
>
> Relate-to:
>
On Wed, Sep 28, 2022 at 12:14:20PM +0800, Naveen Saini wrote:
> Signed-off-by: Naveen Saini
I wasn't seeing this issue. So, my "testing" isn't very valid for it,
but it did work for me :)
Verified in a batch CI job. See
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/654231304
On Tue, Sep 27, 2022 at 02:51:41PM -0400, Jon Mason wrote:
> On Tue, Sep 27, 2022 at 5:55 AM Saini, Naveen Kumar
> wrote:
> >
> >
> >
> > > -Original Message-
> > > From: yocto@lists.yoctoproject.org On
> > > Behalf Of Jon Mason
> > > Sent: Tuesday, September 27, 2022 3:11 AM
> > > To:
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index 8a74e0a80a..ffa35a5ca7 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -88,6 +88,7 @@ def strip_comma(s):
PACKAGECONFIG = " \
gallium \
+
You need to build mesa, not mesa-native. And please show exact changes you
made.
Alex
On Thu 29. Sep 2022 at 12.28, PHIL wrote:
> Tried in a sifferent machine with wednesday poky master
>
> Building mesa-native gives the error
>
> cp:
>
Tried in a sifferent machine with wednesday poky master
Building mesa-native gives the error
cp:
'/media/user/SSD1TB/yoctoqemu/poky/build-virgl/tmp/work/x86_64-linux/mesa-native/2_22.2.0-r0/recipe-sysroot-native/usr/bin/llvm-config14.0.6'
and
25 matches
Mail list logo
