|
Re: Using bitbake with external SDK
#sdk
#zeus
#toolchain
Hello Enrico,
an eSDK would be enough to do everything, however I would demand the entire development system if I were to start a project, but that is my opinion.
I don't know well Node-RED but using
Hello Enrico,
an eSDK would be enough to do everything, however I would demand the entire development system if I were to start a project, but that is my opinion.
I don't know well Node-RED but using
|
By
Marco Cavallini
·
#54837
·
|
|
Re: Using bitbake with external SDK
#sdk
#zeus
#toolchain
Hello Marco,
In your opinion isn't enough to ask for eSDK? for instance if i want to add Node-RED, it would be difficult to build with devtool? because i've seen that it doesn't resolve dependencies
Hello Marco,
In your opinion isn't enough to ask for eSDK? for instance if i want to add Node-RED, it would be difficult to build with devtool? because i've seen that it doesn't resolve dependencies
|
By
enrico.buffoli1994@...
·
#54836
·
|
|
Re: Using bitbake with external SDK
#sdk
#zeus
#toolchain
With the eSDK i've to use devtool right?
With the eSDK i've to use devtool right?
|
By
enrico.buffoli1994@...
·
#54835
·
|
|
Re: Using bitbake with external SDK
#sdk
#zeus
#toolchain
Hello Enrico,
usually nowadays every honest hardware manufacturer provides all the sources of the BSP and the development system to their customers.
Try asking your supplier for them.
--
Marco
Hello Enrico,
usually nowadays every honest hardware manufacturer provides all the sources of the BSP and the development system to their customers.
Try asking your supplier for them.
--
Marco
|
By
Marco Cavallini
·
#54834
·
|
|
[meta-zephyr][PATCH 1/2] zephyr-qemuboot: fix parse build failure
As OE-core explicitly have added depends for qemu-helper addto_recipe_sysroot task, which
breaks zephyr-qemuboot implementation of adding build
As OE-core explicitly have added depends for qemu-helper addto_recipe_sysroot task, which
breaks zephyr-qemuboot implementation of adding build
|
By
Naveen Saini
·
#54833
·
|
|
[meta-zephyr][PATCH 2/2] zephyr-kernel: upgrade 2.6.0 -> 2.6.1
It has GCC-11 fixes.
https://github.com/zephyrproject-rtos/zephyr/issues/35707
Commits included:
2d6322d74a demand_paging: eviction/nru: fix incorrect dirty bit return val
25771e6928 drivers:
It has GCC-11 fixes.
https://github.com/zephyrproject-rtos/zephyr/issues/35707
Commits included:
2d6322d74a demand_paging: eviction/nru: fix incorrect dirty bit return val
25771e6928 drivers:
|
By
Naveen Saini
·
#54832
·
|
|
Re: "stack smashing detected" when building aarch64 kernel
its hard to say what might be going on. Perhaps enable builds with V=1
so you can see if its always failing to compile at same file.
or atleast you can get one file where it fails then you can
its hard to say what might be going on. Perhaps enable builds with V=1
so you can see if its always failing to compile at same file.
or atleast you can get one file where it fails then you can
|
By
Khem Raj
·
#54831
·
|
|
Re: gcov support for target in Yocto
IMAGE_INSTALL += "gcov gcov-symlinks"
IMAGE_INSTALL += "gcov gcov-symlinks"
|
By
Khem Raj
·
#54830
·
|
|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
are you both using systemd or sysvinit
are you both using systemd or sysvinit
|
By
Khem Raj
·
#54829
·
|
|
Re: googletest shared library
Hi,
Regarding the INSANE_SKIP: as that files get packed in the "-dev" package, you should probably then accordingly have:
INSANE_SKIP_${PN}-dev += "dev-elf"
Cheers,
Federico
Hi,
Regarding the INSANE_SKIP: as that files get packed in the "-dev" package, you should probably then accordingly have:
INSANE_SKIP_${PN}-dev += "dev-elf"
Cheers,
Federico
|
By
Federico Pellegrin
·
#54828
·
|
|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
No, it doesn't. Those entries are ignored except /boot.One interesting thing: i always had that bunch of malformed fstab entries.Before the change from static to uuid it looked like this in
No, it doesn't. Those entries are ignored except /boot.One interesting thing: i always had that bunch of malformed fstab entries.Before the change from static to uuid it looked like this in
|
By
Markus Volk
·
#54827
·
|
|
[meta-rockchip][PATCH v2 2/2] rockchip-wic.inc: dont let wic edit fstab by default
Signed-off-by: MarkusVolk <f_l_k@...>
---
conf/machine/include/rockchip-wic.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/conf/machine/include/rockchip-wic.inc
Signed-off-by: MarkusVolk <f_l_k@...>
---
conf/machine/include/rockchip-wic.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/conf/machine/include/rockchip-wic.inc
|
By
Markus Volk
·
#54826
·
|
|
[meta-rockchip][PATCH v2 1/2] rockchip.wks: use uuid for all partitions
My rock pi 4 refused to boot with the latest changes because there are fa=
lse entries
written to fstab. Fix this by using uuid for all partitions
Signed-off-by: MarkusVolk <f_l_k@...>
---
My rock pi 4 refused to boot with the latest changes because there are fa=
lse entries
written to fstab. Fix this by using uuid for all partitions
Signed-off-by: MarkusVolk <f_l_k@...>
---
|
By
Markus Volk
·
#54825
·
|
|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
Thanks for testing. It's also strange that my fstab also has those entries,
but they're apparently ignored in my setup since, commented in or commented
out, they don't seem to affect my board's
Thanks for testing. It's also strange that my fstab also has those entries,
but they're apparently ignored in my setup since, commented in or commented
out, they don't seem to affect my board's
|
By
Trevor Woerner
·
#54824
·
|
|
scikit-learn
#gatesgarth
#yocto
hi guys,
i am trying to build scikit-learn on yocto but i am getting error of setup.py ,it is showing failed i build all dependencies but it is giving error please try to give some i dea
ERROR:
hi guys,
i am trying to build scikit-learn on yocto but i am getting error of setup.py ,it is showing failed i build all dependencies but it is giving error please try to give some i dea
ERROR:
|
By
abhi <abhishek.kumar@...>
·
#54823
·
|
|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
Am 23.09.21 um 13:59 schrieb Trevor Woerner:
That is really strange. As soon as there are those /dev/sda* entries in my fstabmy rock-pi-4c doesn't boot up anymore. As soon as i
Am 23.09.21 um 13:59 schrieb Trevor Woerner:
That is really strange. As soon as there are those /dev/sda* entries in my fstabmy rock-pi-4c doesn't boot up anymore. As soon as i
|
By
Markus Volk
·
#54822
·
|
|
Re: Minutes: Yocto Project Weekly Triage Meeting 9/23/2021
<trevor.gamblin@...> wrote:
I was looking at two issues prior to the meeting. Sadly, due to
inadequate caffeine blood levels and the early hour I confused the
two. So this explains why I
<trevor.gamblin@...> wrote:
I was looking at two issues prior to the meeting. Sadly, due to
inadequate caffeine blood levels and the early hour I confused the
two. So this explains why I
|
By
Steve Sakoman
·
#54821
·
|
|
Re: Using bitbake with external SDK
#sdk
#zeus
#toolchain
if its eSDK then you can, with standard application SDK not so much.
if its eSDK then you can, with standard application SDK not so much.
|
By
Khem Raj
·
#54820
·
|
|
Re: googletest shared library
look into package-split/ directory inside googletest build area and
see how things changes when you use SOLIBS option. I wonder why its
ignoring .h files
look into package-split/ directory inside googletest build area and
see how things changes when you use SOLIBS option. I wonder why its
ignoring .h files
|
By
Khem Raj
·
#54819
·
|
|
Re: Minutes: Yocto Project Weekly Triage Meeting 9/23/2021
I did look at it. It was using a modified oe-selftest with threading instead of multiprocess. We're not using that so I closed it.
Cheers,
Richard
I did look at it. It was using a modified oe-selftest with threading instead of multiprocess. We're not using that so I closed it.
Cheers,
Richard
|
By
Richard Purdie
·
#54818
·
|