From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 2] fs/tar: use qstrip to clean up build output
Date: Fri, 23 May 2014 00:30:55 +0200 [thread overview]
Message-ID: <537E7A9F.4050207@openwide.fr> (raw)
In-Reply-To: <cda34eac2826e87dffc2.1400762141@argentina>
Hi Thomas,
Le 22/05/2014 14:35, Thomas De Schampheleire a ?crit :
> When using the tar filesystem method, the build output shows at the end:
>
> echo " tar -c""f <br>/output/images/rootfs.tar -C <br>/output/target ." >>
> <br>/output/build/_fakeroot.fs
>
> The inner set of quotes can be easily removed by properly stripping the tar
> options (coming from the buildroot configuration).
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Acked-by: Romain Naour <romain.naour@openwide.fr>
Thanks
Romain
>
> ---
> fs/tar/tar.mk | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/tar/tar.mk b/fs/tar/tar.mk
> --- a/fs/tar/tar.mk
> +++ b/fs/tar/tar.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -TAR_OPTS := $(BR2_TARGET_ROOTFS_TAR_OPTIONS)
> +TAR_OPTS := $(call qstrip,$(BR2_TARGET_ROOTFS_TAR_OPTIONS))
>
> define ROOTFS_TAR_CMD
> tar -c$(TAR_OPTS)f $@ -C $(TARGET_DIR) .
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2014-05-22 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 12:35 [Buildroot] [PATCH 0 of 2] Small cleanups of build output Thomas De Schampheleire
2014-05-22 12:35 ` [Buildroot] [PATCH 1 of 2] infra: permissions/users/device tables: avoid adding empty entries Thomas De Schampheleire
2014-05-22 22:30 ` Romain Naour
2014-05-28 20:04 ` Peter Korsgaard
2014-05-22 12:35 ` [Buildroot] [PATCH 2 of 2] fs/tar: use qstrip to clean up build output Thomas De Schampheleire
2014-05-22 22:30 ` Romain Naour [this message]
2014-05-28 20:04 ` Peter Korsgaard
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=537E7A9F.4050207@openwide.fr \
--to=romain.naour@openwide.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.