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 19:57:26 +0200 [thread overview]
Message-ID: <20230822195726.0f691945@windsurf> (raw)
In-Reply-To: <CAN=fXj29fRXvHHZVG03LfTfPQeBrzroV5VN3nwavTw3gejS90Q@mail.gmail.com>
Hello Charles,
On Mon, 21 Aug 2023 16:45:23 -0700
Charles Hardin <ckhardin@gmail.com> wrote:
> https://github.com/zephyrproject-rtos
Yes, I know what Zephyr is :-)
> The build is cmake derived but relies on calling into some python scripts to
> generate some build dependencies
>
> https://github.com/zephyrproject-rtos/zephyr/blob/main/scripts/requirements-base.txt
OK.
> So, we have various RTOS MCUs that are hooked up into linux controllers,
> and this is just a simple hook so that the same SDK can be handled to build
> both firmware for something like an STM32 and a Raspberry-pi
If I rephrase this: you want to use Buildroot to build the Zephyr
firmware for your STM32 micro-controller, alongside with the Linux
system running on the RaspberryPi?
> Assume a reference to
> https://gist.github.com/titouanc/ea0685d9cd8592deb1c49d48e33b3eee to add
> the gcc eabi toolchain has been done in an external package, with the
> patches above we can actually build both firmware and the drivers in
> buildroot from one tree with external recipes like below
Note: this gcc eabi toolchain is now in Buildroot upstream, no need to
add it as an external package.
> env PATH=/opt/sdk/aarch64-buildroot-linux-gnu_sdk-buildroot/bin:$PATH cmake
> \
>
> -DCMAKE_TOOLCHAIN_FILE=/opt/sdk/aarch64-buildroot-linux-gnu_sdk-buildroot/share/buildroot/toolchainfile.cmake
> \
>
>
> -DARMGNU_GCC_TOOLCHAIN_PREFIX="/opt/sdk/aarch64-buildroot-linux-gnu_sdk-buildroot/share/gcc-arm-none-eabi"
> \
>
> -DCMAKE_BUILD_TYPE=Debug \
>
> ../buildroot-external
Not sure to really follow in which projects this cmake command is used?
To build Zephyr?
Best regards,
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-22 17:57 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
2023-08-21 23:45 ` Charles Hardin
2023-08-22 17:57 ` Thomas Petazzoni via buildroot [this message]
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=20230822195726.0f691945@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox