From: Peter Korsgaard <peter@korsgaard.com>
To: Adam Duskett <aduskett@gmail.com>
Cc: Luca Ceresoli <luca@lucaceresoli.net>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Flutter-engine package help wanted.
Date: Sat, 15 Jul 2023 18:24:02 +0200 [thread overview]
Message-ID: <877cr1f8il.fsf@48ers.dk> (raw)
In-Reply-To: <CAFSsvmqOZCu+nRz4Ym-h1zHV53BEgdGkLahXpaiDu=-T17qNpA@mail.gmail.com> (Adam Duskett's message of "Fri, 14 Jul 2023 20:02:23 -0700")
>>>>> "Adam" == Adam Duskett <aduskett@gmail.com> writes:
> Hello! I have a task to port Flutter to Buildroot and to make the packages
> suitable for the master branch.
[snip lots of details]
Gaah, sounds like a big mess :/ Oh well, I guess that is life. Good luck
with it ;)
I take it that you have already looked at
https://github.com/sony/flutter-embedded-linux and the meta-flutter
layer? From a quick look it seems to largely do the same (but skip the
reproducible tarball).
I take it that you have already played around with Flutter? How useful
(features, but also size and build time) is it in the context of
Buildroot?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-15 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 3:02 [Buildroot] Flutter-engine package help wanted Adam Duskett
2023-07-15 16:24 ` Peter Korsgaard [this message]
2023-07-15 18:35 ` Adam Duskett
2023-07-15 21:45 ` Peter Korsgaard
2023-07-16 15:32 ` Arnout Vandecappelle via buildroot
2023-07-17 17:44 ` Adam Duskett
2023-07-17 18:38 ` Yann E. MORIN
2023-07-17 19:16 ` Yann E. MORIN
2023-07-17 19:33 ` Adam Duskett
2023-07-19 2:04 ` Adam Duskett
2023-07-20 2:12 ` 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=877cr1f8il.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=aduskett@gmail.com \
--cc=buildroot@buildroot.org \
--cc=luca@lucaceresoli.net \
--cc=thomas.petazzoni@bootlin.com \
--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