Re: [Buildroot] [PATCH 1/1] package/python-pykwalify: add required package for zephyr cmake

["Yann E. MORIN" <yann.morin.1998@free.fr>]

Arnout, Charles, All,

On 2023-09-21 22:03 +0200, Arnout Vandecappelle via buildroot spake thusly:
> On 22/08/2023 20:02, Charles Hardin wrote:
> >>On Aug 22, 2023, at 10:57 AM, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> >>>On Mon, 21 Aug 2023 16:45:23 -0700
> >>>Charles Hardin <ckhardin@gmail.com> wrote:
> >>>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?
> >Yes, and we are doing this today with these patches.
>  Honestly, I don't know if we want to go in this direction. If Zephyr
> doesn't give you the possibility to do "from scratch" builds, then in this
> day and age it's more appropriate to create a container image for your build
> environment IMHO. There's something to be said for including host packages
> that are likely to be used in post-build/post-image scripts, but for
> building a completely different OS, that is going a little far IMHO.

I concur.

I believe in this case that external projects are better suited to
handle the nitty-gritty details of running those buildsystems, even if,
as Arnout suggests, that is wrapped in a docker image. With proper
CI/CD, it is easy to construct pipelines that build those "other OS"
stuff, export their artefacts for followup Buildroot-based jobs that
integrate those artefacts (either as wrapping package that jsut instlla
binary blob) or as rootfs overlays, or from post-build scripts.

I have marked the series as rejected in patchwork.

>  Specifically for Python packages, I also think it's much more appropriate
> to use poetry to control them for the host. That way we just have to provide
> host-python-poetry, and the post-build/post-image scripts can take care of
> installing all the needed python tools at the exact version you need,
> controlled by a lock file.
> 
>  In my opinion, even including those arm-none-eabi etc. compilers in
> Buildroot was going a bit too far already. But I guess that that ship has
> sailed :-)

I also heartily agree.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot