From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/4] dtc: add host build
Date: Mon, 12 Jan 2015 21:42:33 +0100 [thread overview]
Message-ID: <20150112214233.3f5edf16@free-electrons.com> (raw)
In-Reply-To: <1421000166-24963-3-git-send-email-ps.report@gmx.net>
Dear Peter Seiderer,
On Sun, 11 Jan 2015 19:16:05 +0100, Peter Seiderer wrote:
> diff --git a/package/dtc/Config.in.host b/package/dtc/Config.in.host
> new file mode 100644
> index 0000000..cbabf0a
> --- /dev/null
> +++ b/package/dtc/Config.in.host
> @@ -0,0 +1,9 @@
> +config BR2_PACKAGE_HOST_DTC
> + bool "host dtc"
> + help
> + The Device Tree Compiler, dtc, takes as input a device-tree in
> + a given format and outputs a device-tree in another format.
> +
> + Install host tools: dtc, convert-dtsv0, fdtdump, fdtget and fdtput.
> +
> + https://git.kernel.org/cgit/utils/dtc/dtc.git
I'd like to understand a bit more how this is going to be used exactly,
to see whether there is really a need for a menuconfig option for this
host package. Most host packages are merely build dependencies for
another package, and as such, don't need to appear in menuconfig.
How is host dtc going to be used in your use case?
> +# host build
> +HOST_DTC_DEPENDENCIES = host-bison host-flex
Not really needed, those dependencies are automatically inherited from
DTC_DEPENDENCIES.
> +define HOST_DTC_BUILD_CMDS
> + $(HOST_CONFIGURE_OPTS) \
> + CFLAGS="$(HOST_CFLAGS)" \
Not needed, this definition of CFLAGS is already in
$(HOST_CONFIGURE_OPTS).
Otherwise, looks good.
Thanks,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-12 20:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 18:16 [Buildroot] [PATCH v2 1/4] dtc: fix project and download url Peter Seiderer
2015-01-11 18:16 ` [Buildroot] [PATCH v2 2/4] dtc: bump version to 1.4.1 Peter Seiderer
2015-01-12 20:07 ` Thomas Petazzoni
2015-01-12 22:13 ` Peter Seiderer
2015-01-11 18:16 ` [Buildroot] [PATCH v2 3/4] dtc: add host build Peter Seiderer
2015-01-12 20:42 ` Thomas Petazzoni [this message]
2015-01-12 22:31 ` Peter Seiderer
2015-01-11 18:16 ` [Buildroot] [PATCH v2 4/4] dtc: add patches for raspberry pi overlay support Peter Seiderer
2015-01-12 13:57 ` Matthew Weber
2015-01-12 16:01 ` Peter Seiderer
2015-01-12 20:50 ` Thomas Petazzoni
2015-01-12 22:39 ` Peter Seiderer
2015-01-12 20:39 ` [Buildroot] [PATCH v2 1/4] dtc: fix project and download url Thomas Petazzoni
2015-01-12 22:15 ` Peter Seiderer
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=20150112214233.3f5edf16@free-electrons.com \
--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