From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv1 00/18] Convert the internal toolchain backend to packages
Date: Wed, 26 Jun 2013 21:52:15 +0200 [thread overview]
Message-ID: <20130626215215.3cf0699c@skate> (raw)
In-Reply-To: <CAAXf6LXU3fv0O5hu4hG7f9WaWe_SoAvK5Se=J63ZdHNkszwdOw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Wed, 26 Jun 2013 19:08:33 +0200, Thomas De Schampheleire wrote:
> What about putting all three gcc/gcc-initial/gcc-intermediate packages
> in one directory (three .mk files) and then a common file. This common
> file can contain common rules that can be used by all gcc packages.
> You can make sure that the variables are defined by including the
> common file explicitly from each .mk file (and making sure it doesn't
> match the global 'include package/*/*.mk').
This seems like a good idea, I'll try this out, thanks!
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-06-26 19:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 19:35 [Buildroot] [RFCv1 00/18] Convert the internal toolchain backend to packages Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 01/18] uClibc: KERNEL_SOURCE no longer exists Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 02/18] busybox: don't use kernel headers directly Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 03/18] package: allow to override the make install target for host packages Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 04/18] toolchain/gcc: remove dead code related to host binary stripping Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 05/18] toolchain: remove references to LIBFLOAT_TARGET Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 06/18] toolchain/gcc: get rid of stale variable reference Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 07/18] elf2flt: convert to the package infrastructure Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 08/18] kernel-headers: migrate " Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 09/18] gcc-initial: new package Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 10/18] gcc-intermediate: " Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 11/18] gcc: " Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 12/18] toolchain: switch to using gcc through package infrastructure Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 13/18] gcc-initial, gcc-intermediate, gcc: optimize extraction Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 14/18] uclibc: convert to the package infrastructure Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 15/18] Remove TOOLCHAIN_DIR Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 16/18] Use the 'host-gcc' target instead of the 'uclibc' target Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 17/18] Remove BR2_HAVE_DEVFILES Thomas Petazzoni
2013-06-25 19:35 ` [Buildroot] [RFCv1 18/18] Remove toolchain/toolchain-buildroot.mk Thomas Petazzoni
2013-06-26 17:08 ` [Buildroot] [RFCv1 00/18] Convert the internal toolchain backend to packages Thomas De Schampheleire
2013-06-26 19:52 ` Thomas Petazzoni [this message]
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=20130626215215.3cf0699c@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 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.