|
Layer index update for meta-linux-mainline
Thanks Nico! I'll check again at the end of the week to see if it has updated. Regards,
Thanks Nico! I'll check again at the end of the week to see if it has updated. Regards,
|
By
Paul Barker
· #58924
·
|
|
Layer index update for meta-linux-mainline
Hi folks, I'm unable to make updates to the meta-linux-mainline layer on the layer index. It still has an old email address in the maintainer field which I no longer have access to. The layer can be s
Hi folks, I'm unable to make updates to the meta-linux-mainline layer on the layer index. It still has an old email address in the maintainer field which I no longer have access to. The layer can be s
|
By
Paul Barker
· #58922
·
|
|
[meta-qt4]
Cc'd Paul Eggleton's current email. Perhaps the readme file in meta-qt4 needs updating. Thanks,
Cc'd Paul Eggleton's current email. Perhaps the readme file in meta-qt4 needs updating. Thanks,
|
By
Paul Barker
· #55127
·
|
|
#archiver Archiver not archiving sources from Mirror
#archiver
"Seipel, Christoph" <Christoph.Seipel@...> wrote: If the archives you've been given have names starting with 'gitshallow_' then it's likely that the following variables were set in local.conf or
"Seipel, Christoph" <Christoph.Seipel@...> wrote: If the archives you've been given have names starting with 'gitshallow_' then it's likely that the following variables were set in local.conf or
|
By
Paul Barker
· #54088
·
|
|
Writing a BSP from downstream kernel sources
I think setting `KBUILD_DEFCONFIG = "msm8909_defconfig"` is likely the correct approach here. What you may be missing though is the correct value for KCONFIG_MODE. By default, the supplied defconfig f
I think setting `KBUILD_DEFCONFIG = "msm8909_defconfig"` is likely the correct approach here. What you may be missing though is the correct value for KCONFIG_MODE. By default, the supplied defconfig f
|
By
Paul Barker
· #52070
·
|
|
OpenEmbedded Virtual Stand at FOSDEM 2021
<robert.berger.yocto.user@...> wrote: I'd say video content for FOSDEM should be around the level of the things we'd show on the stand, short demos or introductions which can be understood by pe
<robert.berger.yocto.user@...> wrote: I'd say video content for FOSDEM should be around the level of the things we'd show on the stand, short demos or introductions which can be understood by pe
|
By
Paul Barker
· #52068
·
|
|
requesting help
<vijayrakeshmunganda@...> wrote: Hi Vijay, I hate to be rude but this is terrible advice. That recipe likely has dependencies on other recipes and before you know it you'd be assembling a comple
<vijayrakeshmunganda@...> wrote: Hi Vijay, I hate to be rude but this is terrible advice. That recipe likely has dependencies on other recipes and before you know it you'd be assembling a comple
|
By
Paul Barker
· #52021
·
|
|
OpenEmbedded Virtual Stand at FOSDEM 2021
Hi folks, OpenEmbedded has been accepted to hold a "virtual stand" at FOSDEM 2021 which is taking place online this year on Sat 6th Feb & Sun 7th Feb, based around the CET timezone. Most of you will b
Hi folks, OpenEmbedded has been accepted to hold a "virtual stand" at FOSDEM 2021 which is taking place online this year on Sat 6th Feb & Sun 7th Feb, based around the CET timezone. Most of you will b
|
By
Paul Barker
· #52000
·
|
|
Unable to extract tar file
#dunfell
#yocto
<vijayrakeshmunganda@...> wrote: What I mean is, do you see the file "libopentok_linux_llvm_arm64-2.18.1.tgz" itself under ${WORKDIR}? i.e. has it been copied instead of extracted? Also, please
<vijayrakeshmunganda@...> wrote: What I mean is, do you see the file "libopentok_linux_llvm_arm64-2.18.1.tgz" itself under ${WORKDIR}? i.e. has it been copied instead of extracted? Also, please
|
By
Paul Barker
· #51935
·
|
|
Unable to extract tar file
#dunfell
#yocto
<vijayrakeshmunganda@...> wrote: Does the .tgz file get placed in ${WORKDIR} without being extracted? Also, which Yocto Project version/branch are you using? Thanks,
<vijayrakeshmunganda@...> wrote: Does the .tgz file get placed in ${WORKDIR} without being extracted? Also, which Yocto Project version/branch are you using? Thanks,
|
By
Paul Barker
· #51932
·
|
|
chpasswd not working in yocto-2019
<raghu.icecraft@...> wrote: Yocto Project doesn't have a version "2019.1", see https://wiki.yoctoproject.org/wiki/Releases. I guess you're using a vendor supplied BSP or SDK with that version nu
<raghu.icecraft@...> wrote: Yocto Project doesn't have a version "2019.1", see https://wiki.yoctoproject.org/wiki/Releases. I guess you're using a vendor supplied BSP or SDK with that version nu
|
By
Paul Barker
· #51838
·
|
|
Automatic addition of trailing slashes on layers.openembedded.org
Hi folks, Working on the docs recently we noticed that there is no automatic addition of a trailing slash on layers.openembedded.org when it's needed: https://layers.openembedded.org/layerindex/branch
Hi folks, Working on the docs recently we noticed that there is no automatic addition of a trailing slash on layers.openembedded.org when it's needed: https://layers.openembedded.org/layerindex/branch
|
By
Paul Barker
· #51826
·
|
|
Using U-boot in Yocto
The IMAGE_INSTALL variable is used for packages to install into the rootfs. Typically bootloaders need some special handling and simply adding them to IMAGE_INSTALL either doesn't work or isn't suffic
The IMAGE_INSTALL variable is used for packages to install into the rootfs. Typically bootloaders need some special handling and simply adding them to IMAGE_INSTALL either doesn't work or isn't suffic
|
By
Paul Barker
· #51813
·
|
|
meta-kernel -> meta-linux-mainline
Hi all, Just a quick announcement. The meta-kernel layer has been renamed to meta-linux-mainline to avoid any confusion. The new URL for the layer is https://gitlab.com/openembedded/community/meta-lin
Hi all, Just a quick announcement. The meta-kernel layer has been renamed to meta-linux-mainline to avoid any confusion. The new URL for the layer is https://gitlab.com/openembedded/community/meta-lin
|
By
Paul Barker
· #51677
·
|
|
Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
Could you share the command that you executed along with the full output that was printed? There's not really enough information here to diagnose the issue. Thanks,
Could you share the command that you executed along with the full output that was printed? There's not really enough information here to diagnose the issue. Thanks,
|
By
Paul Barker
· #51572
·
|
|
Use of USERADD_PACKAGES with out recipe package files
You probably need to set `ALLOW_EMPTY_${PN}-user-sys`. See https://docs.yoctoproject.org/ref-manual/ref-variables.html?highlight=allow_empty#term-ALLOW_EMPTY. Thanks,
You probably need to set `ALLOW_EMPTY_${PN}-user-sys`. See https://docs.yoctoproject.org/ref-manual/ref-variables.html?highlight=allow_empty#term-ALLOW_EMPTY. Thanks,
|
By
Paul Barker
· #51569
·
|
|
[OE-core][PATCH] kernel-dummy: fix executing unexpected tasks
I don't think "CLOSED" is a good choice to use in the core metadata. The usual way to handle recipes like this which don't require external source code is to say that they have the same license as the
I don't think "CLOSED" is a good choice to use in the core metadata. The usual way to handle recipes like this which don't require external source code is to say that they have the same license as the
|
By
Paul Barker
· #51561
·
|
|
Enaable to add binary in /usr/bin using .bb file
It looks like your original email was sent less than an hour ago, give people some time. I also recommend looking at the docs yourself. Thanks,
It looks like your original email was sent less than an hour ago, give people some time. I also recommend looking at the docs yourself. Thanks,
|
By
Paul Barker
· #51444
·
|
|
Enaable to add binary in /usr/bin using .bb file
It looks like your original email was sent less than an hour ago, give people some time. I also recommend looking at the docs yourself. Thanks,
It looks like your original email was sent less than an hour ago, give people some time. I also recommend looking at the docs yourself. Thanks,
|
By
Paul Barker
· #51429
·
|
|
Patch files before recipe is parsed
There's nothing in bitbake to support this. If you need to carry patches against an EOL branch then you can either create a local fork of poky or use a setup tool like kas (https://github.com/siemens/
There's nothing in bitbake to support this. If you need to carry patches against an EOL branch then you can either create a local fork of poky or use a setup tool like kas (https://github.com/siemens/
|
By
Paul Barker
· #51371
·
|