Arch Linux User Repository

Note to the lovers of AUR helpers : It looks like dependency resolution is a complex topic. Despite all package relations being properly declared in the Flutter packages, most AUR helpers seem to have trouble resolving the dependency chain between the package bases aur/flutter and aur/flutter-artifacts-google-bin. This is not my fault and I cannot do anything about it.

It looks like the initial installation works fine using aur/paru. Sadly aur/paru does not reach at building updates for the package.

On the other hand aur/yay properly reaches at both installing and updating this package, even though it builds the package 15 times (!!!) again and again.

If you use aur/paru, consider to simply execute pacman -R flutter && pacman -Rns flutter to clean up the previous installation of both package bases.

• https://github.com/Jguer/yay/issues/2413
• https://github.com/Morganamilo/paru/issues/1173

If you build both package bases using makepkg -sfC and later on install all build outputs using pacman -U, both the installation and the updates work like a charm.

I'm very sorry for the inconvenience, but sadly there's nothing I can do about this.

Huge update to the Flutter AUR package :

The previous implementation basically did a user installation of Flutter - downloaded the custom Dart SDK, CI artifacts from Chromium CI and had to be kept in user R/W access in order to have the Flutter Cache Manager working.

These times are now over - a clean and (almost) completely rewritten PKGBUILD which now uses clean dependency declarations, system Dart and Gradle and for sure no more user R/W installation directory.

This AUR entry is now a split package. Installing aur/flutter will still bundle the entire toolchain you knew from before. The other way round, if you don't need everything - e.g. when depending on Flutter as a build dependency in another package, you can choose to only depend on what you need.

The following split packages are available :

• flutter : meta package containing all other split packages

• flutter-common : the common files for Flutter needed for all use cases

• flutter-devel : your option of choice as a developer - ships the Flutter tool and all required templates to e.g. create a new project

• flutter-tool : The pure Flutter tool. Use as depends to build your package.

• flutter-target-linux : The Flutter Linux build files. Use as depends to build your package.

• flutter-target-web : The Flutter web build files. Use as depends to build web apps (e.g. fluffychat-web does this).

• flutter-target-android : The Flutter Android build files. Use if you want to develop Android apps.

• flutter-gradle : The Flutter Gradle wrapper. Populated from system Gradle.

• flutter-intellij-patch : a tiny patch to make the IntelliJ Flutter plugin work with the new package.

• flutter-material-fonts-google-bin : Mandatory fonts package, planned to have a system-installed drop-in replacement soon.

• flutter-engine-common-google-bin : Shared part of the Flutter engine - downloaded from Google servers.

• flutter-sky-engine-google-bin : Flutter sky engine - downloaded from Google servers.

• flutter-engine-linux-google-bin : Linux part of the Flutter engine - downloaded from Google servers.

• flutter-engine-web-google-bin : Web part of the Flutter engine - downloaded from Google servers.

• flutter-engine-android-google-bin : Android part of the Flutter engine - downloaded from Google servers.

• flutter-gradle-google-bin : The Flutter Gradle wrapper - downloaded from Google servers.

Stay tuned for non google-bin versions of the engine, they are in coming !

Since almost everything is written from scratch and heavy patches are applied to use the system packages as dependencies, there might still be bugs occurring. Please report them otherwise I can't fix them !

Trying to update to 3.19.6-1 and I get the following whenever I flutter run:

Unhandled exception:
Unexpected Kernel Format Version 117 (expected 114)
#0      BinaryBuilder.readComponent.<anonymous closure> (package:kernel/binary/ast_from_binary.dart:692)
#1      Timeline.timeSync (dart:developer/timeline.dart:173)
#2      BinaryBuilder.readComponent (package:kernel/binary/ast_from_binary.dart:679)
#3      _InitializationFromSdkSummary._prepareSummary (package:front_end/src/fasta/incremental_compiler.dart:2503)
#4      _InitializationFromUri.initialize (package:front_end/src/fasta/incremental_compiler.dart:2577)
...

kso: yes. We're all getting shenanigans with this package (I've already seen the "layer.error" error when trying to install it). It goes worse and worse with each new release patch. What worked for me was the steps mentionned by the maintainer:

In all cases, building the two pkgbase repos using makepkg -s[fC] and a manual installation of all output packages using pacman -U works.

Hi the build was working before (back in February 2024) but now I get this error:

==> Starting prepare()...
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> Failed to install layer, rolling up to next layer.error:error making: flutter - exit status 4

Is anyone else getting this error? Does anyone know what is the full name of the "layer" library mentioned in the error?

@WithTheBraid I just got to see your comment in my emails. Sorry for no response.

Apparently, the underlying issue regarding that error wasn't because of the AUR package itself but because I had arch4edu repo added on my install. They forgot to update dependencies for flutter-target-* at the time, causing them to fail to install.

I had that repo added for not having to spend much bandwidth for proprietary packages like google-chrome-stable, but I found out that it's a no-go after this incident.

I absolutely refuse to use Chaotic AUR for prebuilt packages as I build linux-nitrous from its source with USE_MPERFORMANCE=1, which is a flag to enable mtune flag for the detected CPU throughout the kernel. This flag isn't in use on generic repos like CAUR to make it work globally on any system the prebuilt packages are installed on which means performance drawbacks, which kinda defeats the purpose of that kernel for modern hardware.

I apologize for the confusion, just wanted to clear that up.

getting an error: ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.

I tried installing stable dart-sdk 3.3.2 on Manjaro using my own PKGBUILD, since the extra/dart package is still in 3.0.7 and dart-sdk-dev from aur uses a different sdk path. Now the error became:

Unhandled exception:
Crash when compiling package:mypackage/main.dart:
Unexpected Kernel SDK Version c09cb46304 (expected bc4150a9a2).

EDIT: I installed extra/dart straight from ArchLinux repo to solve the issue

I got past the "Your Flutter SDK download may be corrupt" message on Manjaro by creating a symlink from /opt/dart-sdk-dev to /opt/dart-sdk.

But now I'm getting a "Unexpected Kernel Format Version 114 (expected 116)" error when trying to run a new test project.

I met the same issue as @StrontiumK9:

Your Flutter SDK download may be corrupt or missing permissions to run. Try re-downloading the Flutter SDK into a directory that has read/write permissions for the
current user.

Same of StrontiumK9 for me. flutter doctor doesn't see any issue on my installation but flutter doesn't even create a new project from terminal, printing that error. Obviously, I got to my user r/w permissions for flutter at /usr/lib/flutter