couldnt this have been a udev_append.bb
instead of writing your own my-rules On Wed, Nov 7, 2018 at 6:46 PM Markus W <markus4...@gmail.com> wrote: > > This my bb file and than I have added the following to local.conf > IMAGE_INSTALL_append = " my-rules ...". > > SUMMARY = "My rules" > LICENSE = "CLOSED" > PR = "r1" > > SRC_URI = "file://90-interfaces.rules" > > do_install[nostamp] = "1" > do_unpack[nostamp] = "1" > > do_install () { > install -d ${D}${sysconfdir}/udev/rules.d > install -m 0666 ${WORKDIR}/90-interfaces.rules > ${D}/etc/udev/rules.d/90-interfaces.rules > > } > > FILES_${PN} += " /etc/udev/rules.d/90-interfaces.rules" > > PACKAGES = "${PN}" > PROVIDES = "my-rules" > > Hope this helps > > /Markus > > On Wed, 7 Nov 2018 at 12:41, Outback Dingo <outbackdi...@gmail.com> wrote: >> >> so curious, as im trying to add 2 udev rules also that i require in my >> build, so how was your recipe configured? >> >> mine keeps telling me i have a conflict between packages as they both >> install files to the same name and same place >> On Wed, Nov 7, 2018 at 4:53 PM Outback Dingo <outbackdi...@gmail.com> wrote: >> > >> > >> > >> > On Wed, Nov 7, 2018, 16:44 Markus W <markus4...@gmail.com wrote: >> >> >> >> I have resolved this issue. My problem was that in my layer I have a >> >> recipe-core and within that I had the following structure >> >> udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on >> >> the same level. >> >> >> >> By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it >> >> suddenly worked. >> >> >> >> Cool >> >> >> >> >> >> Regards, >> >> Markus >> >> >> >> On Tue, 6 Nov 2018 at 14:06, Outback Dingo <outbackdi...@gmail.com> wrote: >> >> > >> >> > On Tue, Nov 6, 2018 at 11:57 AM Markus W <markus4...@gmail.com> wrote: >> >> > > >> >> > > Hi! >> >> > > >> >> > > I want to append the rules in the >> >> > > recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from >> >> > > within my own recipe. I canĀ“t figure out how to do that. >> >> > > >> >> > > I have tried to add those rules as separate rules file in a recipe in >> >> > > my own layer. After the build I can see that the rules file is in the >> >> > > correct directory /etc/udev/rules.d (next to 99-com.rules) but the >> >> > > rules didn't get applied. The groups below I have created by >> >> > > inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c; >> >> > > -r gpio") in a different layer with a higher priority than the layer >> >> > > with the rules recipe. >> >> > > >> >> > > Not sure why this is not working. Any suggestions? >> >> > > >> >> > > 90-interfaces.rules file: >> >> > > >> >> > > SUBSYSTEM=="input", GROUP="input", MODE="0660" >> >> > > SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660" >> >> > > SUBSYSTEM=="spidev", GROUP="spi", MODE="0660" >> >> > > SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660" >> >> > > >> >> > > SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660" >> >> > > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\ >> >> > > chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\ >> >> > > chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770 >> >> > > /sys/devices/virtual/gpio;\ >> >> > > chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\ >> >> > > '" >> >> > > >> >> > >> >> > might help to post the recipe used..... >> >> > >> >> > >> >> > > Regards, >> >> > > Markus >> >> > > -- >> >> > > _______________________________________________ >> >> > > yocto mailing list >> >> > > yocto@yoctoproject.org >> >> > > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto