From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charles Hardin <ckhardin@gmail.com>
Cc: "Alvaro G . M" <alvaro.gamez@hazent.com>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-pykwalify: add required package for zephyr cmake
Date: Tue, 22 Aug 2023 00:13:41 +0200 [thread overview]
Message-ID: <20230822001341.7256e67d@windsurf> (raw)
In-Reply-To: <20230821175828.42827-1-ckhardin@gmail.com>
Hello Charles,
On Mon, 21 Aug 2023 10:58:28 -0700
Charles Hardin <ckhardin@gmail.com> wrote:
> When building zephyr based firmware, the cmake integrates with
> python scripts that can be run using the buildroot host-python
> dependencies. This is useful for the sdk setups and associated
> build steps for the firmware. In this use-case, a buildroot
> external project can be setup with recipes to build firmware
> images using eabi toolchains and the linux controller software
> to talk to those firmware images using one SDK. This might not
> be overtly obvious from the patches.
Could you clarify a bit what you call "zephyr cmake" and the use case
for this?
> Add the required host packages and additional pykwalify
This needs to be split into multiple patches, one per package affected.
But I think we also need to understand the bigger picture of what this
is useful for.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-21 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 17:58 [Buildroot] [PATCH 1/1] package/python-pykwalify: add required package for zephyr cmake Charles Hardin
2023-08-21 22:13 ` Thomas Petazzoni via buildroot [this message]
2023-08-21 23:45 ` Charles Hardin
2023-08-22 17:57 ` Thomas Petazzoni via buildroot
2023-08-22 18:02 ` Charles Hardin
2023-09-21 20:03 ` Arnout Vandecappelle via buildroot
2023-09-21 22:05 ` Yann E. MORIN
2023-08-22 1:33 ` [Buildroot] [PATCH v2 1/4] package/python-dateutil: add host python package for dependencies Charles Hardin
2023-08-22 1:33 ` [Buildroot] [PATCH v2 2/4] package/python-docopt: " Charles Hardin
2023-08-22 1:33 ` [Buildroot] [PATCH v2 3/4] package/python-ruamel-yaml: " Charles Hardin
2023-08-22 1:33 ` [Buildroot] [PATCH v2 4/4] package/python-pykwalify: add required package for zephyr cmake Charles Hardin
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=20230822001341.7256e67d@windsurf \
--to=buildroot@buildroot.org \
--cc=alvaro.gamez@hazent.com \
--cc=asafka7@gmail.com \
--cc=ckhardin@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.