From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libffi: minor corrections in post install hooks
Date: Tue, 27 Aug 2013 19:10:27 +0200 [thread overview]
Message-ID: <20130827191027.3add3cc2@skate> (raw)
In-Reply-To: <1541068056.5590214.1377606409099.JavaMail.root@openwide.fr>
Dear Nicolas M?n?gale,
This looks good, but:
* Your patch subject should have mentioned it's the second version.
See --subject-prefix when generating/sending your patches.
* The commit log could be a little bit more verbose on what the commit
is doing. Basically, all the details you wrote after the "---"
should in this case be part of the commit log itself. What is after
the "---" marker are changelog informations, i.e things that changed
between revisions of the patches. The real description of what the
patch is doing should be part of the commit log.
Thanks,
Thomas
On Tue, 27 Aug 2013 14:26:49 +0200 (CEST), Nicolas M?n?gale wrote:
> Signed-off-by: Nicolas M?n?gale <nicolas.menegale@openwide.fr>
> ---
> v1: second commit
> In order to be sure that we just deal with the includes related with
> the actual package described into libffi.mk it is better to explicitly
> specify the version of the libffi we deal with into the post install
> hook.
> As dev files are deprecated in target rootfs target post install
> hook was also deleted.
> ---
> package/libffi/libffi.mk | 11 +----------
> 1 file changed, 1 insertion(+), 10 deletions(-)
>
> diff --git a/package/libffi/libffi.mk b/package/libffi/libffi.mk
> index 0ad5c84..8c84924 100644
> --- a/package/libffi/libffi.mk
> +++ b/package/libffi/libffi.mk
> @@ -14,7 +14,7 @@ LIBFFI_AUTORECONF = YES
> # Move the headers to the usual location, and adjust the .pc file
> # accordingly.
> define LIBFFI_MOVE_STAGING_HEADERS
> - mv $(STAGING_DIR)/usr/lib/libffi-*/include/*.h $(STAGING_DIR)/usr/include/
> + mv $(STAGING_DIR)/usr/lib/libffi-$(LIBFFI_VERSION)/include/*.h $(STAGING_DIR)/usr/include/
> $(SED) '/^includedir.*/d' -e '/^Cflags:.*/d' \
> $(STAGING_DIR)/usr/lib/pkgconfig/libffi.pc
> rm -rf $(TARGET_DIR)/usr/lib/libffi-*
> @@ -22,15 +22,6 @@ endef
>
> LIBFFI_POST_INSTALL_STAGING_HOOKS += LIBFFI_MOVE_STAGING_HEADERS
>
> -# Similar for target headers
> -define LIBFFI_MOVE_TARGET_HEADERS
> - install -d $(TARGET_DIR)/usr/include/
> - mv $(TARGET_DIR)/usr/lib/libffi-*/include/*.h $(TARGET_DIR)/usr/include/
> - rm -rf $(TARGET_DIR)/usr/lib/libffi-*
> -endef
> -
> -LIBFFI_POST_INSTALL_TARGET_HOOKS += LIBFFI_MOVE_TARGET_HEADERS
> -
> HOST_LIBFFI_AUTORECONF = YES
>
> $(eval $(autotools-package))
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-27 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 12:26 [Buildroot] [PATCH 1/1] libffi: minor corrections in post install hooks Nicolas Ménégale
2013-08-27 17:10 ` Thomas Petazzoni [this message]
[not found] <1931727883.5578934.1377595721868.JavaMail.root@openwide.fr>
2013-08-27 9:29 ` Nicolas Ménégale
2013-08-27 9:36 ` Samuel Martin
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=20130827191027.3add3cc2@skate \
--to=thomas.petazzoni@free-electrons.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