From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/6 RFC] toolchain/external: use generic extract commands (branch yem/extract-cmds)
Date: Sat, 3 Oct 2015 15:31:49 +0200 [thread overview]
Message-ID: <560FD8C5.1060803@openwide.fr> (raw)
In-Reply-To: <cover.1441233378.git.yann.morin.1998@free.fr>
Hi Yann,
Le 03/09/2015 00:51, Yann E. MORIN a ?crit :
> Hello All!
>
> This series is an attempt at simplifying the way external toolchains are
> extracted.
>
> Currently, external toolchains use custom extract commands, because they
> want to exclude a bumch of files during extraction, so as to save a bit
> of space (locales in some toolchains can account for up to 80% of the
> size of the toolchain as a whole).
>
> And it turns out, gcc also wants to exclude a bunch of files (java and
> go, testsuites).
>
> Using custom extract commands means that those packages (and critical
> ones, at that) can not benefit from the enhancements and fixes made to
> the generic commands, like the automatic triiping of components.
>
> In this series:
>
> - we first introduce the support for the exclusion list
> - we always break/dereference hardlinks
> - we make gcc use the exclusion list
> - we then make the external toolchains use it (in two passes: one for
> the non-Blackfin case, one for it, as it is 'seecial')
> - finaly, we introduce the Codescape MTI toolchain from Vincent
>
> Thomas, there is a question for you in the second commit: would you
> care to explain what your goal was when you added --hard-dereference
> when extracting the Blackfin toolchains?
>
What do you think about a new Kconfig option that allow users to define a list
of excluded files or directories.
Some toolchains (ie SourceryCodeBench standard) can bundle eclipse or other
stuff that are not used in the build process.
Something like:
config BR2_TOOLCHAIN_EXTERNAL_EXCLUDES
string "Exclude unwanted directories from the toolchain archive"
default ""
help
If some directories in the toolchain archive are not intended
to be used in the build process, this option define a
space-separated list of patterns to exclude when extracting
the archive.
ifneq ($(BR2_TOOLCHAIN_EXTERNAL_EXCLUDES),)
TOOLCHAIN_EXTERNAL_EXCLUDES = $(call qstrip,$(BR2_TOOLCHAIN_EXTERNAL_EXCLUDES))
endif
Thoughts ?
Best regards,
Romain
> Regards,
> Yann E. MORIN.
next prev parent reply other threads:[~2015-10-03 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 22:51 [Buildroot] [PATCH 0/6 RFC] toolchain/external: use generic extract commands (branch yem/extract-cmds) Yann E. MORIN
2015-09-02 22:51 ` [Buildroot] [PATCH 1/6 RFC] core/pkg-generic: allow packages to exclude files when extracting Yann E. MORIN
2015-10-03 14:46 ` Romain Naour
2015-09-02 22:51 ` [Buildroot] [PATCH 2/6 RFC] core/pkg-generic: always dereference hardlinks from archives Yann E. MORIN
2015-09-02 22:51 ` [Buildroot] [PATCH 3/6 RFC] package/gcc: use generic extract commands Yann E. MORIN
2015-10-03 14:49 ` Romain Naour
2015-09-02 22:51 ` [Buildroot] [PATCH 4/6 RFC] toolchain/external: use generic extract commands (!blackfin case) Yann E. MORIN
2015-10-03 14:55 ` Romain Naour
2015-09-02 22:51 ` [Buildroot] [PATCH 5/6 RFC] toolchain/external: use generic extract commands (blackfin case) Yann E. MORIN
2015-10-03 14:55 ` Romain Naour
2015-09-02 22:52 ` [Buildroot] [PATCH 6/6 RFC] Add support for MIPS Codescape MTI GNU Linux toolchain Yann E. MORIN
2015-09-03 14:06 ` Vicente Olivert Riera
2015-10-03 14:58 ` Romain Naour
2015-10-03 13:31 ` Romain Naour [this message]
2015-10-03 14:06 ` [Buildroot] [PATCH 0/6 RFC] toolchain/external: use generic extract commands (branch yem/extract-cmds) Arnout Vandecappelle
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=560FD8C5.1060803@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox