Re: [yocto] [npm] duplicate code

Hi Jean-Marie, what work do you plan to do on npm and recipetool? I have start to rework the complete npm integration to synchronize it with other languages like python. I replace the bitbake npm fetch with the wget fetcher and download the npm tgz files direct. The idea is to handle every pa

[yocto] Demos for the Yocto Project booth at ELCE in Lyon

Dear all, As usual, the Yocto Project will have a booth at the ELCE conference in Lyon later this month. While the booth is a great opportunity for everyone to get a new sticker of your favorite project ;-) we are also very excited when developers from our community get a chance to show off the fu

[yocto] kernel.bbclass do_bundle_initramfs did not work

Hi, It seems to me if both INITRAMFS_IMAGE and INITRAMFS_IMAGE_BUNDLE are set it should generate initramfs, but I did not get. I set up in my image: INITRAMFS_IMAGE = "zImage-initramfs" INITRAMFS_IMAGE_BUNDLE = "1" But it did not build zImage-initramfs, what I could be missing here? Thank you.

Re: [yocto] kernel.bbclass do_bundle_initramfs did not work

Hey JH, I had a similiar problem before. What branch and revision do you have checked out for your meta-layers ? Mine looks like the following and I get an initramfs built into my image: meta-yocto-bsp   = "warrior:01b8a8b54bc569e5ef3f5e6fc6abcee365ab25d9" meta-intel   = "warrior:6bd

Re: [yocto] Cannot use "LICENSE_CREATE_PACKAGE = 1" when building the image with mdns

I investigated a little bit. Probably, I didn't understand your point. The postinst script modifies nsswitch adding mdns and this is right, but why is this interfering with the license create package? If I remove the postinst I can build with license create package, however I need this change to

Re: [yocto] [npm] duplicate code

Hi Stefan, I have recently worked on a yocto project using npm and I have seen some issues. I have solved a few but only for bitbake: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eecba41822e86b69ebdb9cbc8fbfd512ad9a47d7 https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a34d

Re: [yocto] [npm] duplicate code

Hi Jean-Marie, Am 04.10.19 um 14:37 schrieb Jean-marie Lemetayer: > I have recently worked on a yocto project using npm and I have seen some issues. I have solved a few but only for bitbake: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=eecba41822e86b69ebdb9cbc8fbfd512ad9a47d7 http

Re: [yocto] Cannot use "LICENSE_CREATE_PACKAGE = 1" when building the image with mdns

I fixed this issue in this way: I modified the recipe replacing this: -- pkg_postinst_${PN} () { sed -e '/^hosts:/s/\s*\//' \ -e 's/\(^hosts:.*\)\(\\)\(.*\)\(\\)\(.*\)/\1\2 mdns\3\4\5/' \ -i $D/etc/nsswitch.conf } pkg_prerm_${PN} () { sed -e '/^

Re: [yocto] Cannot use "LICENSE_CREATE_PACKAGE = 1" when building the image with mdns

Oh, another update to integrate the previous email. Inside the source code of mDNSResponder ( https://opensource.apple.com/tarballs/mDNSResponder/mDNSResponder-878.260.1.tar.gz) I found in "mDNSPosix/Makefile" this: " # Check the nsswitch.conf file. # If 'mdns' does not already appear on the "hos

[yocto] Building a out of tree kernel module on target system

Hello, I am trying to build an out of tree service module on a yocto raspberry pi image(target system). I am using yocto version warrior and my machine is Raspberrypi-cm3 Kernel version is 4.19.58 I was able to get the build directory by including IMAGE_INSTALL_append = " kernel-modules kernel-d

[yocto] [layerindex-web][PATCH] These changes will add the metadata for product revision and epoch if present in the bitbake recipe.

Signed-off-by: Pranay Mankad --- .../migrations/0042_recipe_property_addition.py | 20 layerindex/models.py | 2 ++ layerindex/update_layer.py | 2 ++ 3 files changed, 24 insertions(+) create mode 100644 layeri

[yocto] [layerindex-web][PATCH] Track PE and PR for recipes

This change is to report PE (epoch) and PR (release) values for recipes from the bitbake cooker. These values will be reflected in the Rest API and will not be exposed on the UI. The aim of this change is to enrich metadata availability to consumers of the feed. ` Signed-off-by: Pranay Mankad -

[yocto] sumo-2.5 build error with core-image-base ERROR: e2fsprogs-native-1.43.8-r0 do_patch: Command Error: 'quilt --quiltrc

Hi scott/stefano, Please provide your inputs to clear the below issue from yocto- sumo-2.5 branch( Compiling for iMx8) i am struggling since 2 weeks. I am building yocto sumo 2.5 branch with below configuration (bblayers.conf and local.conf are below the mail. please check ). Below is the error

[yocto] meta-selinux warrior support

Hi, I am getting the below error when I am trying to integrate 'meta-selinux' into our yocto solution. This error also happens when I just build 'core-image-selinux' by including the required layers in warrior branch. Can anyone provide a fix for this.. local.conf contains the following li

Re: [yocto] Building a out of tree kernel module on target system

On Fri, Oct 4, 2019 at 11:40 AM Shravan Singh wrote: > > Hello, > > I am trying to build an out of tree service module on a yocto raspberry pi > image(target system). > I am using yocto version warrior > and my machine is Raspberrypi-cm3 > Kernel version is 4.19.58 > > I was able to get the build

[yocto] using BBMULTICONFIG to create a 32-bit rootfs, kernel, u-boot that also includes a 64-bit kernel, u-boot for NXP i.mx6/i.mx8

Hello, We're working on a Linux distro for two systems where one is based on NXP i.mx6(32-bit,armv7) and the other i.mx8(64-bit,armv8). I have two machine types defined in Yocto so individually I can build either one however our goal is to create a single distro that can run on both processors.

Re: [yocto] using BBMULTICONFIG to create a 32-bit rootfs, kernel, u-boot that also includes a 64-bit kernel, u-boot for NXP i.mx6/i.mx8

On Fri, Oct 4, 2019, 7:04 PM Davis Roman wrote: > Hello, > > We're working on a Linux distro for two systems where one is based on > NXP i.mx6(32-bit,armv7) and the other i.mx8(64-bit,armv8). > > I have two machine types defined in Yocto so individually I can build > either one however our goal i