Arch Linux User Repository

I revamped this package so that now, the engine will be compiled on demand by packages using it and cached in the user cache directory (~/.cache/flutter-engine). It will be cached per version, so it will be the user's responsibility to clean it once in a while.

My package will try to detect the version of the engine used, but packages can also define the variable _engine_version to specify which version to use.

See package localsend for an example on how to use.

This package will compile the flutter engine from source, which can take a lot of time and memory. Use flutter-engine-google-bin if you want to use pre-compiled binaries from Google.

It is meant to be a make dependency.

@Freso It's possible but I wouldn't recommend it and I opted not to since it's not stable enough. It would be too difficult to maintain and make sure an update doesn't break an app. This method make sure it doesn't break apps and apps can use the version they need.

I’m not familiar with how flutter-engine works, but is there no way to actually build/compile a binary and install it system wide via the package instead of doing this script to have users install it under their $HOME?

I revamped this package so that now, the engine will be compiled on demand by packages using it and cached in the user cache directory (~/.cache/flutter-engine). It will be cached per version, so it will be the user's responsibility to clean it once in a while.

My package will try to detect the version of the engine used, but packages can also define the variable _engine_version to specify which version to use.

I reverted the version back to 3.13.9, can you try again with that version?

==> Making package: localsend 1.12.0-2 (Tue 28 Nov 2023 22:24:51)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found localsend-1.12.0.tar.gz
  -> Updating flutter git repo...
From https://github.com/flutter/flutter
 - [deleted]                 (none)                 -> refs/pull/138937/merge
remote: Enumerating objects: 41, done.
remote: Counting objects: 100% (40/40), done.
remote: Compressing objects: 100% (25/25), done.
remote: Total 41 (delta 28), reused 16 (delta 15), pack-reused 1
Unpacking objects: 100% (41/41), 11.26 KiB | 1.61 MiB/s, done.
   223f32e09ec..f2b74725c58  main                   -> main
   223f32e09ec..f2b74725c58  master                 -> master
   223f32e09ec..f2b74725c58  refs/pull/126219/head  -> refs/pull/126219/head
   223f32e09ec..f2b74725c58  refs/pull/126253/head  -> refs/pull/126253/head
   223f32e09ec..f2b74725c58  refs/pull/126255/head  -> refs/pull/126255/head
   223f32e09ec..f2b74725c58  refs/pull/126256/head  -> refs/pull/126256/head
 + 9e9249ee9c0...0fc0a1d3fb9 refs/pull/137348/merge -> refs/pull/137348/merge  (forced update)
 + 9fdae28e6c4...132f1dcee23 refs/pull/137936/merge -> refs/pull/137936/merge  (forced update)
 + 055401ffa88...da36a77bc94 refs/pull/138581/merge -> refs/pull/138581/merge  (forced update)
   5c4b3f21276..429c666ec47  refs/pull/138896/head  -> refs/pull/138896/head
 + a168d734474...a2f0eac11b7 refs/pull/138896/merge -> refs/pull/138896/merge  (forced update)
  -> Updating flutter-engine git repo...
==> Validating source files with sha256sums...
    localsend-1.12.0.tar.gz ... Passed
    flutter ... Skipped
    flutter-engine ... Skipped
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting localsend-1.12.0.tar.gz with bsdtar
  -> Creating working copy of flutter git repo...
Cloning into 'flutter'...
done.
  -> Creating working copy of flutter-engine git repo...
Cloning into 'flutter-engine'...
done.
==> Starting prepare()...
Note: switching to '3.16.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 74d16627b94 [flutter_releases] Flutter stable 3.16.0 Engine Cherrypicks (#48029)
Note: switching to '3.16.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at db7ef5bf9f5 [flutter_releases] Flutter stable 3.16.0 Framework Cherrypicks (#138506)
sed: can't read flutter/bin/internal/shared.sh: No such file or directory
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: localsend-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
localsend - exit status 4

See package localsend for an example on how to use.

This package will compile the flutter engine from source, which can take a lot of time and memory. Use flutter-engine-google-bin if you want to use pre-compiled binaries from Google.

It is meant to be a make dependency.