summaryrefslogtreecommitdiffstats
path: root/README.hardware
diff options
context:
space:
mode:
authorMarkus Lehtonen <markus.lehtonen@linux.intel.com>2016-08-04 12:02:11 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-08-10 10:46:31 +0100
commit961b5269cdda9d9f7a2abc36401ae484e550089d (patch)
treefeab148cbc72f152afe11f3c7e9da73c7af28105 /README.hardware
parent416c4bc00973f585b18262f62dbb1aee188dbee9 (diff)
downloadpoky-961b5269cdda9d9f7a2abc36401ae484e550089d.tar.gz
package.bbclass: better handling of middle-path dir symlinks
For example in a directory structure like this . ├── symlink -> foo/bar └── foo └── bar └── file 'file' could be referenced by specifying e.g. 'foo/bar/file' or 'symlink/file'. In cases like this populate_packages() might crash if the file was referenced (in FILES) via the symlinked directory. The outcome depends on how the user defined FILES_pn. This patch should make the function behave more consistently. It looks for files which are referenced via symlinked directories and handles them separately, failing if their parent directory is a non-existent path. For example, defining FILES_{PN} = "symlink/file" causes a build failure because symlinks target 'foo/bar' is not included at all. [YOCTO #9827] (From OE-Core rev: 29d1738329ddf4e63844a9ad1158a1d41e2ee343) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README.hardware')
0 files changed, 0 insertions, 0 deletions