From: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Andreas Naumann <anaumann@ultratronik.de>
Cc: Adam Duskett <adam.duskett@amarulasolutions.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/2] Fix flutter build failure
Date: Tue, 20 Feb 2024 14:20:28 +0100 [thread overview]
Message-ID: <eca996e7-dda2-4dfb-9cc2-0f2ea90daafa@bubu1.eu> (raw)
In-Reply-To: <ZdPG1PGaE3RfoWHk@landeda>
Hi Andreas, Yann, all
On 19.02.24 22:23, Yann E. MORIN wrote:
> Andreas, All,
>
> On 2024-02-19 10:51 +0100, Andreas Naumann spake thusly:
>> Hello Adam, all,
>> I was motivated to give flutter a spin after your talk at FOSDEM,
>> however the recent bump to Python 3.12.1 broke some script during
>> the flutter-engine configure step.
>> Fortunately now a new major stable version has been released 3.19.0,
>> which contains a patch for this.
>>
>> After bumping engine and sdk they successfully build again, as does
>> creating the flutter bundles which you provided in
>> https://github.com/aduskett/buildroot-fosdem2024-flutter-demos
>>
>> I have not yet been able to run them using ivi-homescreen, but that's
>> probably due to my target display/wayland setup.
>>
>> However, the flutter-gallery no longer builds with 3.19, even after
>> bumping to the main HEAD. Their github README says
>> "NOTE: The Flutter Gallery is now deprecated, and no longer being active
>> maintained."
>> I thought about including a patch for removal of the gallery package,
>> but that would leave us with no example for how to create a flutter
>> bundle.
>
> The upstream repository has also been "archived", which means it is
> frozen and will never get fixed, ever.
>
> That's a bit unfortunate indeed, but we don't have much choice going
> forward: we'll have to drop that package in the near future, but not
> now: we're still considering reverting the python 3.12 version bump for
> 2024.02, as it still causes issues in the target==build case, which
> means we'd be able to keep the current flutter stack for 2024.02 LTS.
>
> Then, we can reintroduce python3, the flutter-engine bumps in this
> series, and drop flutter-gfallery, hopefully introducing another package
> as an example on how to build flutter packages...
The archived repo page links to
https://github.com/gskinnerTeam/flutter-wonderous-app and
https://github.com/flutter/samples/tree/main/material_3_demo as
replacement showcases.
I wonder how long these will last... :-/.
Marcus
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-02-20 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:51 [Buildroot] [PATCH 0/2] Fix flutter build failure Andreas Naumann
2024-02-19 9:51 ` [Buildroot] [PATCH 1/2] package/flutter-engine: bump to version 3.19.0 Andreas Naumann
2024-02-19 9:51 ` [Buildroot] [PATCH 2/2] package/flutter-sdk-bin: " Andreas Naumann
2024-02-19 21:23 ` [Buildroot] [PATCH 0/2] Fix flutter build failure Yann E. MORIN
2024-02-20 13:20 ` Marcus Hoffmann via buildroot [this message]
2024-02-22 22:43 ` Adam Duskett
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=eca996e7-dda2-4dfb-9cc2-0f2ea90daafa@bubu1.eu \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.com \
--cc=anaumann@ultratronik.de \
--cc=buildroot@bubu1.eu \
--cc=yann.morin.1998@free.fr \
/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