From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] libfslparser: add install hooks to fix libraries path
Date: Fri, 30 Oct 2015 11:27:06 +0100 [thread overview]
Message-ID: <2787793.hk6j5KppJf@sagittea> (raw)
In-Reply-To: <1446149212-12048-4-git-send-email-gary.bisson@boundarydevices.com>
Hello Garry,
On Thursday 29 October 2015 21:06:51 Gary Bisson wrote:
[...]
> b/package/libfslparser/libfslparser.mk index 2b53d62..aa02f19 100644
> --- a/package/libfslparser/libfslparser.mk
> +++ b/package/libfslparser/libfslparser.mk
> @@ -20,4 +20,12 @@ endef
> # The Makefile installs several versions of the libraries, but we only
> # need one of them, depending on the platform.
>
> +# no need to symlink in target image, just move libraries around
> +define LIBFSLPARSER_FIXUP_TARGET_PATH
> + find $(TARGET_DIR)/usr/lib/imx-mm -mindepth 2 -maxdepth 2 -not -type d \
> + -exec mv {} $(TARGET_DIR)/usr/lib \;
> + rm -fr $(TARGET_DIR)/usr/lib/imx-mm
> +endef
> +LIBFSLPARSER_POST_INSTALL_TARGET_HOOKS += LIBFSLPARSER_FIXUP_TARGET_PATH
A POST_INSTALL_STAGING_HOOKS is not necessary for libfslparser?
Regards,
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2015-10-30 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 20:06 [Buildroot] [PATCH 0/4] libfsl*: fix install path + update conf opts Gary Bisson
2015-10-29 20:06 ` [Buildroot] [PATCH 1/4] libfslcodec: add install hooks to fix libraries path Gary Bisson
2015-10-29 20:06 ` [Buildroot] [PATCH 2/4] libfslcodec: add missing configure options Gary Bisson
2015-10-29 20:06 ` [Buildroot] [PATCH 3/4] libfslparser: add install hooks to fix libraries path Gary Bisson
2015-10-30 10:27 ` Jérôme Pouiller [this message]
2015-10-30 10:36 ` Gary Bisson
2015-10-30 10:43 ` Jérôme Pouiller
2015-11-08 16:08 ` Gary Bisson
2015-11-09 8:43 ` Jérôme Pouiller
2015-10-29 20:06 ` [Buildroot] [PATCH 4/4] libfslparser: add missing configure options Gary Bisson
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=2787793.hk6j5KppJf@sagittea \
--to=jezz@sysmic.org \
--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