Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 23:45:54 +0200	[thread overview]
Message-ID: <87351og86l.fsf@48ers.dk> (raw)
In-Reply-To: <CAFSsvmrKm3QVhiZYJRe-UBmX5TEkdrCKdHy+xJ242ng=wdQctw@mail.gmail.com> (Adam Duskett's message of "Sat, 15 Jul 2023 11:35:40 -0700")

>>>>> "Adam" == Adam Duskett <aduskett@gmail.com> writes:

 > Hey Peter!
 > One thought I had that I didn’t bring up in the first email: Another
 > possible solution is to create and upload a tarball to the buildroot
 > sources server, but each tarball is around 2.1GiB in size!

So far the s.b.o is just a fallback and something required for an active
package. I would prefer to keep it like that if at all possible.


 > I have been using meta-flutter to port the package to Buildroot, but
 > haven’t quite got it to compile yet!

OK.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-07-15 21:46 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
2023-07-15 18:35   ` Adam Duskett
2023-07-15 21:45     ` Peter Korsgaard [this message]
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=87351og86l.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