I have had some success and some failure. Attempt 1: FAILI changed the SRC to:FILESEXTRAPATHS_prepend := "${THISDIR}/files:" removing the machine name and the space. The machine is sama5d3xek. I still get an the error : (the directory is now changed) > | DEBUG: Executing shell function do_install > | cp: cannot stat > '/home/lachlan/poky/build-atmel/tmp/work/sama5d3xek-poky-linux-gnueabi/linux > -yocto-custom/3.10+AUTOINC+35158dd80a-r5/sama5d3xek_lsp.dts': No > such file or directory >
Note: There is already a .bbappend file for this recipe in the original source. Can a problem occur having two bbappend recipes each containing FILESEXTRAPATHS_prepend := "${THISDIR}/files:" but referring to different ${THISDIR} directories? The existing linux-yocto-custom_3.10.bbppend file contains:KBRANCH = "linux-3.10-at91"SRCREV = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" - i am on a differnt computer so I wont copy the numbersPV = "${LINUX_VERSION}+${SRCPV}"PR = "r5"FILESEXTRAPATHS_prepend := "${THISDIR}/files/${MACHINE}:" SRC_URI = "git://github.com/linux4sam/linux-at91git;protocol=git;branch=${KBRANCH};nocheckout=1"SRC_URI += "file://defconfig" do_deploy_append () {.......} Attempt 2: FAIL I tried making the source file name incorrectSRC_URI += " file://sama5d3xek_wrong.dts "The same error results. I would have thought it would pick up a different error if the original source file could not be found. Attempt 3: THIS WORKEDI also copied the following code to the original vendor supplied .bbppend recipe, as well as moving the sama5d3xek_lsp.dts to the correct directory for that recipeSRC_URI += " file://sama5d3xek_lsp.dts " KERNEL_DEVICETREE += " sama5d3xek_lsp.dtb" do_install_prepend () { cp ${WORKDIR}/sama5d3xek_lsp.dts ${WORKDIR}/linux/arch/${ARCH}/boot/dts } This worked and the device tree blob was built. However, I don't want to modify the vendor supplied source files and would like another way of doing this in my own layer. Any thoughts?ThanksLachlan ----- Original Message ----- From: "Paul Eggleton" To: Cc: Sent:Mon, 29 Dec 2014 11:25:50 +0000 Subject:Re: [yocto] bitbake cannot locate source file from recipe Hi Lachlan, On Monday 29 December 2014 18:49:32 peterengcomau...@adam.com.au wrote: > I am trying to modify my device tree build to include a slightly > modifed version. > > I have created the recipe linux-yocto-custom_3.10.bbappend that > contains the following: > > PR = "r5" > FILESEXTRAPATHS_prepend := "${THISDIR}/files/sama5d3xek: " > SRC_URI += " file://sama5d3xek_lsp.dts " > KERNEL_DEVICETREE += " sama5d3xek_lsp.dtb" > > do_install_prepend () { > cp ${WORKDIR}/sama5d3xek_lsp.dts > ${WORKDIR}/linux/arch/${ARCH}/boot/dts > } > > I fget the error from bitbake as follows: > > Log data follows: > | DEBUG: Executing shell function do_install > | cp: cannot stat > > '/home/lachlan/poky/build-atmel/tmp/work/sama5d3xek-poky-linux-gnueabi/linux > -yocto-custom/3.10+AUTOINC+35158dd80a-r5/sama5d3xek/sama5d3xek_lsp.dts': No > such file or directory > > The source file is located in the append recipes subdirectory > files/sama5d3xek/ > > Can anyone suggest why the source dts file is not being made > available ? I am sure it is a simple mistake! This error is a little puzzling because I can't see how you could end up with "/home/lachlan/poky/build-atmel/tmp/work/sama5d3xek-poky-linux-gnueabi/linux- yocto-custom/3.10+AUTOINC+35158dd80a-r5/sama5d3xek/" (or more specifically, the final "sama5d3xek" subdirectory) from "${WORKDIR}/". Was this perhaps from an earlier version of the recipe? In any case, is "sama5d3xek" the value of MACHINE in your configuration? If so, the MACHINE value is already searched as a subdirectory of anything in FILESEXTRAPATHS, and you shouldn't then end up with that subdirectory when the file is copied into the WORKDIR. Try this instead: FILESEXTRAPATHS_prepend := "${THISDIR}/files:" (Also, there should be no spaces in FILESEXTRAPATHS, I notice you had a trailing one in there.) Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ---- Message sent via Adam Internet WebMail - http://www.adam.com.au/
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto