From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/4] libfslparser: add install hooks to fix libraries path
Date: Thu, 10 Dec 2015 14:52:39 +0100 [thread overview]
Message-ID: <1449755560-2911-4-git-send-email-gary.bisson@boundarydevices.com> (raw)
In-Reply-To: <1449755560-2911-1-git-send-email-gary.bisson@boundarydevices.com>
By default, all the libraries are installed under /usr/lib/imx-mm which
causes problems at runtime.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
---
I'm actually not sure if libfslparser is needed at all. I couldn't find
a library depending on any of the one from the package. But Yocto still has
depency on the package for gst-fsl-plugins:
https://github.com/Freescale/meta-fsl-arm/blob/fido/recipes-multimedia/gstreamer/gst-fsl-plugin.inc#L9
Regards,
Gary
---
package/libfslparser/libfslparser.mk | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/package/libfslparser/libfslparser.mk b/package/libfslparser/libfslparser.mk
index 2b53d62..221d5e4 100644
--- a/package/libfslparser/libfslparser.mk
+++ b/package/libfslparser/libfslparser.mk
@@ -20,4 +20,19 @@ endef
# The Makefile installs several versions of the libraries, but we only
# need one of them, depending on the platform.
+# Use symlinks in staging dir so every application can link against the libs
+# whether they look at imx-mm or not (gst-fsl-plugins vs. gst1-imx).
+define LIBFSLPARSER_FIXUP_STAGING_PATH
+ find $(STAGING_DIR)/usr/lib/imx-mm -mindepth 2 -maxdepth 2 -not -type d \
+ -exec ln -fs {} $(STAGING_DIR)/usr/lib \;
+endef
+LIBFSLPARSER_POST_INSTALL_STAGING_HOOKS += LIBFSLPARSER_FIXUP_STAGING_PATH
+
+# Use symlinks for install dir as well to match staging setup.
+define LIBFSLPARSER_FIXUP_TARGET_PATH
+ find $(TARGET_DIR)/usr/lib/imx-mm -mindepth 2 -maxdepth 2 -not -type d \
+ -exec ln -fs {} $(TARGET_DIR)/usr/lib \;
+endef
+LIBFSLPARSER_POST_INSTALL_TARGET_HOOKS += LIBFSLPARSER_FIXUP_TARGET_PATH
+
$(eval $(autotools-package))
--
2.6.2
next prev parent reply other threads:[~2015-12-10 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 13:52 [Buildroot] [PATCH v2 0/4] libfsl*: fix install path + update conf opts Gary Bisson
2015-12-10 13:52 ` [Buildroot] [PATCH v2 1/4] libfslcodec: add install hooks to fix libraries path Gary Bisson
2015-12-13 20:31 ` Yann E. MORIN
2015-12-14 21:34 ` Gary Bisson
2015-12-13 20:36 ` Yann E. MORIN
2015-12-14 21:25 ` Gary Bisson
2016-01-24 20:55 ` Gary Bisson
2015-12-10 13:52 ` [Buildroot] [PATCH v2 2/4] libfslcodec: add missing configure options Gary Bisson
2015-12-13 20:32 ` Yann E. MORIN
2015-12-14 21:28 ` Gary Bisson
2016-03-04 9:17 ` Gary Bisson
2015-12-10 13:52 ` Gary Bisson [this message]
2015-12-13 20:38 ` [Buildroot] [PATCH v2 3/4] libfslparser: add install hooks to fix libraries path Yann E. MORIN
2015-12-10 13:52 ` [Buildroot] [PATCH v2 4/4] libfslparser: add missing configure options Gary Bisson
2015-12-13 20:39 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1449755560-2911-4-git-send-email-gary.bisson@boundarydevices.com \
--to=gary.bisson@boundarydevices.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox