Re: [Gumstix-users] file location in openembedded

[Cliff B. <cli...@gm...>]

On Sun, Jul 12, 2009 at 8:51 PM, Matthew Bowles<ma...@aw...> wrote:

> firstly I'm not sure which recipe I should be editing? and secondly I am not
> confident about the bitbake system at all. it seems very interwoven and hard
> to trace when a file doesn't make its way into the rootfs.
>
> I'll give an specific example and hopefully someone can help me.
> I would like the file /etc/passwd to be a symbolic link to
> /mmc/aux/etc/passwd
> such as if it were created at runtime with 'ln -s /mmc/aux/etc/passwd
> /etc/passwd
>
> I think I was trying to create this link by putting some instructions into
> the base-file-xxx.bb recipe

What I typically do is create a custom image, and then a recipe that
has all my custom files in it.  If you are not worried about opkg
upgrade, then you can just replace existing files in the rootfs if you
place the package last in the IMAGE_INSTALL list.

To create a custom image recipe, look at:
http://bec-systems.com/site/177/the-correct-way-to-add-packages-to-an-openembedded-image

A recipe that includes your custom files, and creates links can look
something like the below:

========================
my_custom_recipe.bb:
PR = "r1"

SRC_URI = "file://custom_file_1 \
  file://custom_file_2 \
  "
do_install() {
  # systconfdir is typically /etc
  install -d ${D}${sysconfdir}/
  install -m 0755 ${WORKDIR}/custom_file_1 ${D}${sysconfdir}/
  ln -sf custom_file_1 ${D}/{sysconfdir}/link_to_custom_file_1
  ln -s /mmc/aux/etc/passwd ${D}${sysconfdir}/passwd
}

========================

And then set IMAGE_INSTALL in the image recipe to look something like:

IMAGE_INSTALL += "\
      ....
      my_custom_recipe \
      "

Note, my_custom_recipe is the last package in the list, so that it can
replace files in other packages if needed.

Cliff
http://bec-systems.com