summaryrefslogtreecommitdiff
path: root/meta/classes/relative_symlinks.bbclass
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2017-02-08 16:10:50 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-02-09 10:50:54 +0000
commite478550c8cd889f12e336e268e9e3b30827bf840 (patch)
tree5bfc7ebdc09e7f0a8159080ee4891de77dba5d90 /meta/classes/relative_symlinks.bbclass
parent15376e5ff35367c1b40941d10e7b19302058a53e (diff)
downloadopenembedded-core-e478550c8cd889f12e336e268e9e3b30827bf840.tar.gz
openembedded-core-e478550c8cd889f12e336e268e9e3b30827bf840.tar.bz2
openembedded-core-e478550c8cd889f12e336e268e9e3b30827bf840.zip
openssl/fontconfig/bzip2: Use relative symlinks instead of absolute ones (using a new class)
Absolute path symlinks are a bit of a pain for sstate and the native versions of these recipes currently contain broken symlinks as a result. There are only a small number of problematic recipes, at least in OE-Core, namely the three here. Rather than trying to make sstate handle this magically, which turns out to be a harder problem than you'd first realise, simply make the symlinks relative early in the process and avoid all the problems. The alternative is adding new complexity to sstate which we could really do without as without the complexity, you can't always tell where the absolute symlink is relative to (due to prefixes used for native sstate). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/relative_symlinks.bbclass')
-rw-r--r--meta/classes/relative_symlinks.bbclass5
1 files changed, 5 insertions, 0 deletions
diff --git a/meta/classes/relative_symlinks.bbclass b/meta/classes/relative_symlinks.bbclass
new file mode 100644
index 0000000000..3157737347
--- /dev/null
+++ b/meta/classes/relative_symlinks.bbclass
@@ -0,0 +1,5 @@
+do_install[postfuncs] += "install_relative_symlinks"
+
+python install_relative_symlinks () {
+ oe.path.replace_absolute_symlinks(d.getVar('D'), d)
+}