On Fri, 2023-08-11 at 09:22 +1200, Tom Isaacson wrote:
> DEBUG: Checking
> /home/tom/Documents/Bitbucket/my-app/my-yocto-sdk/poky/build/tmp/work/x86_64-linux/dwarfsrcfiles-native/1.0-r0/sysroot-destdir//home/tom/Documents/Bitbucket/my-app/my-yocto-sdk/poky/build/tmp/work/x86_64-linux/dwarfsrcfiles-
Hi all,
I added a new recipe for libudev-zero, which provides a minimal daemon-less
udev implementation. The recipe works, but has an issue that pops up regularly
where it causes an exception during rootfs:
Exception: FileNotFoundError: [Errno 2] No such file or directory:
'/ssd/opt/oe/yocto/k
I have a recipe abc_1.0.bb. It generates a txt contains all layers git commit
ID into /etc. It is installed into image by IMAGE_INSTALL:append = " abc".
I want to rebuild abc every time I execute bitbake . So I set nostamp to
1 in abc_1.0.bb.
It served my purpose. When I execute bitbake core-imag
I tried the dependency graph but it was enormous and too hard to read.
I can see in log.do_package for my app:
NOTE: Direct dependencies are
['poky/meta/recipes-devtools/dwarfsrcfiles/dwarfsrcfiles.bb:do_populate_sysroot']
and it doesn't make any difference if I add "dwarfsrcfiles-native" as
a depe
See
https://patchwork.yoctoproject.org/project/oe-core/patch/20230623093323.4058529-1-martin.ja...@gmail.com/
which is easy to backport work around to fix uninative-3.9 and 4.0.
Until uninative-4.1 with more proper fix (
https://patchwork.yoctoproject.org/project/oe-core/patch/20230731191005.34668
You just need to switch all the layers to the needed branch and run
the build, and see what happens. It's impossible to predict that until
the build runs and fails in some way, but when it does fail, we can
offer guidance, or you can look it up in migration guides first
perhaps.
I'm not sure where
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage
*Attendees: *Richard Purdie, Steve Sakoman, Stephen Jolley, Bruce
Ashfield, Tim Orling, Joshua Watt, Ross Burton, Randy Macleod, Trevor
Gamblin, Alexandre Belloni, Michael Opdenacker, Antonio, Yoann Congal,
Pavel Zhukov, Edi Feschiyan
*AR
On 10 Aug 2023, at 09:35, Alexander Kanavin via lists.yoctoproject.org
wrote:
>
> On Thu, 10 Aug 2023 at 10:28, Michael Opdenacker via
> lists.yoctoproject.org
> wrote:
>> You may actually prefer to use our latest long term support release,
>> Kirkstone, which will be supported until 2026.
>
>
I looked for Kirkstone but there is only a kirkstone-next layer for meta-xilinx
repository: https://github.com/Xilinx/meta-xilinx/tree/kirkstone-next. I
actually don't understand what the difference is between these normal and -next
branches. My guess is they create them for the uncompleted code
On Thu, 10 Aug 2023 at 10:28, Michael Opdenacker via
lists.yoctoproject.org
wrote:
> You may actually prefer to use our latest long term support release,
> Kirkstone, which will be supported until 2026.
For what it's worth, I would not recommend anyone to start with the
LTS. It's useful if you ar
I have a ramdomize problem on local ssh git repository.
The git server is on the PC where i am using YOCTO
The git repository belong to an another user (git) than bitbake user (ame).
DISTRO = "poky"
DISTRO_NAME = "Poky (Yocto Project Reference Distro)"
DISTRO_VERSION = "4.2"
DISTRO_CODENAME = "mi
Hello,
On 10.08.23 at 09:57, msenturk wrote:
I am convinced to not use an older version. As I said, I am currently
using Gatesgarth. I am planning to migrate to Mickledore which is
currently supported. How can I migrate? I looked system requirements
for Mickledore and everything seems good. Co
I am convinced to not use an older version. As I said, I am currently using
Gatesgarth. I am planning to migrate to Mickledore which is currently
supported. How can I migrate? I looked system requirements for Mickledore and
everything seems good. Could you tell it with details for a beginner. Th
13 matches
Mail list logo
