Files
meta-openembedded/meta-oe
Chase Maupin 0738c3c808 kernel bbclass: return to original directory in do_deploy
* During the base kernel_do_deploy function the directory is
  changed to DEPLOYDIR in order to do some cleanup and symlinking.
  However, the directory is not changed back to the original
  starting directory ${S} at the end.  For append functions this
  means that the starting directory is not ${S} as expected but
  instead ${DEPLOYDIR}.

  For functions like the do_deploy_append in
  recipes-kernel/linux/linux-dtb.inc there is an assumption that
  you are still in the source directory and not the DEPLOYDIR.
  Without this change the .dtb files are not copied because the
  check for the existence of ${DTS_FILE} which is a relative
  path from the ${S} directory fails.  This means that the .dtb
  files are not copied into the deploy directory and subsequently
  the deploy/images directory.

  In the log.do_deploy file you will see lines like:

    Warning: arch/arm/boot/dts/xxxxx.dts is not available!

  This fix has also been picked up in the oe-core kernel.bbclass:

  http://cgit.openembedded.org/openembedded-core/commit/?id=fd5d80ab1a405cb4ef94f2cde25f8c251da490f0

Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Eric Bénard <eric@eukrea.com>
2013-04-05 16:55:00 +02:00
..
2013-02-01 09:59:00 +01:00
2013-01-31 22:25:35 +01:00
2011-07-26 21:51:39 +02:00
2012-11-23 15:22:46 +01:00

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: danny
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][danny]' in the subject'

When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][danny][PATCH'

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <koen@dominion.thruhere.net>