NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
fff23fd15d
kumquat-buildroot/package/flutter-engine/flutter-engine.mk

247 lines
8.7 KiB
Makefile
Raw Normal View History

package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
################################################################################
#
# flutter-engine
#
################################################################################
# Flutter-engine has a release on the GitHub page. However, that release is
# only for Google. Its intended purpose is for the gclient tool provided by
# Google in their depot-tools package. To use the source code, we must use
# gclient to download the flutter-engine source code along with several other
# projects. Unfortunately, the Buildroot download system does not have the
# capability of using gclient, and considering this package is the only
# package that uses gclient, we side-step the entire download process and
# perform the following steps if a tarball does not exist already:
#
# - Copy the pre-made gclient config file to a temporary scratch directory.
# - Run gclient sync to generate a source directory with the proper
# flutter-engine source code in the correct places.
# - Create a source tarball.
# - Copy the source tarball to the $(FLUTTER_ENGINE_DL_DIR) directory.
#
# There is no hash provided, as the gn binary (used for configuration) relies
# on the .git directories. As such, a reproducible tarball is not possible.
package/flutter-engine: bump version to 3.16.8 Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2024-01-17 23:50:44 +01:00
FLUTTER_ENGINE_VERSION = 3.16.8
package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
# There is nothing for Buildroot to download. This is handled by gclient.
FLUTTER_ENGINE_SITE =
FLUTTER_ENGINE_SOURCE =
FLUTTER_ENGINE_LICENSE = BSD-3-Clause
FLUTTER_ENGINE_LICENSE_FILES = LICENSE
FLUTTER_ENGINE_TARBALL_PATH = $(FLUTTER_ENGINE_DL_DIR)/flutter-$(FLUTTER_ENGINE_VERSION).tar.gz
FLUTTER_ENGINE_INSTALL_STAGING = YES
FLUTTER_ENGINE_DOWNLOAD_DEPENDENCIES = host-depot-tools
FLUTTER_ENGINE_DEPENDENCIES = \
host-flutter-sdk-bin \
host-ninja \
host-pkgconf \
freetype \
zlib
# Dispatch all architectures of flutter
# FLUTTER_ENGINE_TARGET_TRIPPLE must match the directory name found in
# buildtools/linux-x64/clang/lib/clang/*/lib
ifeq ($(BR2_aarch64),y)
FLUTTER_ENGINE_TARGET_ARCH = arm64
FLUTTER_ENGINE_TARGET_TRIPPLE = aarch64-unknown-linux-gnu
else ifeq ($(BR2_arm)$(BR2_armeb),y)
FLUTTER_ENGINE_TARGET_ARCH = arm
FLUTTER_ENGINE_TARGET_TRIPPLE = armv7-unknown-linux-gnueabihf
else ifeq ($(BR2_x86_64),y)
FLUTTER_ENGINE_TARGET_ARCH = x64
FLUTTER_ENGINE_TARGET_TRIPPLE = x86_64-unknown-linux-gnu
endif
package/flutter-engine: Add profile runtime mode selection Buildroot only offers two possible runtime modes for Flutter that are automatically selected based on what the user has selected: - debug if BR2_ENABLE_RUNTIME_DEBUG is enabled. - release if BR2_ENABLE_RUNTIME_DEBUG is not enabled. However, Flutter also offers the profile runtime mode option. From https://docs.flutter.dev/testing/build-modes: ``` "Use profile mode when you want to analyze performance." What is profile mode? Some debugging ability is maintained in profile mode, which is enough to profile your app's performance. Profile mode is turned off on the emulator and simulator because their behavior does not represent actual performance. ``` As Flutter projects can be heavy and consume many resources, it is necessary to allow users developing a Flutter application to profile their application during development. This patch introduces a new choice: FLUTTER_ENGINE_RUNTIME_MODE_PROFILE. If unselected, the global option BR2_ENABLE_RUNTIME_DEBUG continues to determine whether to build Flutter in release or debug mode. This new option may confuse some users who wonder where the release and debug options are, so the help menu section under the FLUTTER_ENGINE_RUNTIME_MODE_PROFILE option explains that the global BR2_ENABLE_RUNTIME_DEBUG option controls the debug and release modes. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2024-01-03 00:59:29 +01:00
ifeq ($(FLUTTER_ENGINE_RUNTIME_MODE_PROFILE),y)
FLUTTER_ENGINE_RUNTIME_MODE=profile
else ifeq ($(BR2_ENABLE_RUNTIME_DEBUG),y)
package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
FLUTTER_ENGINE_RUNTIME_MODE=debug
else
FLUTTER_ENGINE_RUNTIME_MODE=release
endif
FLUTTER_ENGINE_BUILD_DIR = \
$(@D)/out/linux_$(FLUTTER_ENGINE_RUNTIME_MODE)_$(FLUTTER_ENGINE_TARGET_ARCH)
FLUTTER_ENGINE_INSTALL_FILES = libflutter_engine.so
# Flutter engine includes a bundled patched clang that must be used for
# compiling or else there are linking errors.
FLUTTER_ENGINE_CLANG_PATH = $(@D)/buildtools/linux-x64/clang
FLUTTER_ENGINE_CONF_OPTS = \
--clang \
--embedder-for-target \
--linux-cpu $(FLUTTER_ENGINE_TARGET_ARCH) \
--no-build-embedder-examples \
--no-clang-static-analyzer \
--no-enable-unittests \
--no-goma \
--no-prebuilt-dart-sdk \
--no-stripped \
--runtime-mode $(FLUTTER_ENGINE_RUNTIME_MODE) \
--target-os linux \
--target-sysroot $(STAGING_DIR) \
--target-toolchain $(FLUTTER_ENGINE_CLANG_PATH) \
--target-triple $(FLUTTER_ENGINE_TARGET_TRIPPLE)
ifeq ($(BR2_arm)$(BR2_armeb),y)
FLUTTER_ENGINE_CONF_OPTS += \
--arm-float-abi $(call qstrip,$(BR2_GCC_TARGET_FLOAT_ABI))
endif
# We must specify a full path to ccache and a full path to the flutter-engine
# provided clang in order to use ccache, or else flutter-engine will error out
# attempting to find ccache in the target-toolchain provided path.
ifeq ($(BR2_CCACHE),y)
define FLUTTER_ENGINE_COMPILER_PATH_FIXUP
$(SED) "s%cc =.*%cc = \"$(HOST_DIR)/bin/ccache $(FLUTTER_ENGINE_CLANG_PATH)/bin/clang\""%g \
$(@D)/build/toolchain/custom/BUILD.gn
$(SED) "s%cxx =.*%cxx = \"$(HOST_DIR)/bin/ccache $(FLUTTER_ENGINE_CLANG_PATH)/bin/clang++\""%g \
$(@D)/build/toolchain/custom/BUILD.gn
endef
FLUTTER_ENGINE_PRE_CONFIGURE_HOOKS += FLUTTER_ENGINE_COMPILER_PATH_FIXUP
endif
ifeq ($(BR2_ENABLE_LTO),y)
FLUTTER_ENGINE_CONF_OPTS += --lto
else
FLUTTER_ENGINE_CONF_OPTS += --no-lto
endif
ifeq ($(BR2_OPTIMIZE_0),y)
FLUTTER_ENGINE_CONF_OPTS += --unoptimized
endif
# There is no --disable-fontconfig option.
ifeq ($(BR2_PACKAGE_FONTCONFIG),y)
FLUTTER_ENGINE_DEPENDENCIES += fontconfig
FLUTTER_ENGINE_CONF_OPTS += --enable-fontconfig
endif
ifeq ($(BR2_PACKAGE_HAS_LIBGL),y)
FLUTTER_ENGINE_DEPENDENCIES += libgl
endif
ifeq ($(BR2_PACKAGE_HAS_LIBGLES),y)
FLUTTER_ENGINE_DEPENDENCIES += libgles
package/flutter-engine: use impeller rendering engine From https://docs.flutter.dev/perf/impeller: Impeller provides a new rendering runtime for Flutter. The Flutter team’s believes this solves Flutter’s early-onset jank issue. Impeller precompiles a smaller, simpler set of shaders at Engine build time so they don’t compile at runtime. Impeller has the following objectives: - Predictable performance: Impeller compiles all shaders reflection and offline at build time. It builds all pipeline state objects upfront. The engine controls caching and caches explicitly. - Instrumentable: Impeller tags and labels all graphics resources like textures, and buffers. It can capture and persist animations to disk without affecting per-frame rendering performance. - Portable: Flutter doesn’t tie Impeller to a specific client rendering API. You can author shaders once and convert them to backend-specific formats as necessary. - Leverages modern graphics APIs: Impeller uses, but doesn’t depend on, features available in modern APIs like Metal and Vulkan. - Leverages concurrency: Impeller can distribute single-frame workloads across multiple threads if necessary. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-11-03 10:56:17 +01:00
FLUTTER_ENGINE_CONF_OPTS += --enable-impeller-opengles
package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
endif
ifeq ($(BR2_PACKAGE_LIBGLFW),y)
FLUTTER_ENGINE_DEPENDENCIES += libglfw
FLUTTER_ENGINE_CONF_OPTS += --build-glfw-shell
else
FLUTTER_ENGINE_CONF_OPTS += --no-build-glfw-shell
endif
ifeq ($(BR2_PACKAGE_LIBGTK3),y)
FLUTTER_ENGINE_DEPENDENCIES += libgtk3
FLUTTER_ENGINE_INSTALL_FILES += libflutter_linux_gtk.so
else
FLUTTER_ENGINE_CONF_OPTS += --disable-desktop-embeddings
endif
# There is no --disable-vulkan option
ifeq ($(BR2_PACKAGE_MESA3D_VULKAN_DRIVER),y)
package/flutter-engine: use impeller rendering engine From https://docs.flutter.dev/perf/impeller: Impeller provides a new rendering runtime for Flutter. The Flutter team’s believes this solves Flutter’s early-onset jank issue. Impeller precompiles a smaller, simpler set of shaders at Engine build time so they don’t compile at runtime. Impeller has the following objectives: - Predictable performance: Impeller compiles all shaders reflection and offline at build time. It builds all pipeline state objects upfront. The engine controls caching and caches explicitly. - Instrumentable: Impeller tags and labels all graphics resources like textures, and buffers. It can capture and persist animations to disk without affecting per-frame rendering performance. - Portable: Flutter doesn’t tie Impeller to a specific client rendering API. You can author shaders once and convert them to backend-specific formats as necessary. - Leverages modern graphics APIs: Impeller uses, but doesn’t depend on, features available in modern APIs like Metal and Vulkan. - Leverages concurrency: Impeller can distribute single-frame workloads across multiple threads if necessary. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-11-03 10:56:17 +01:00
FLUTTER_ENGINE_CONF_OPTS += --enable-vulkan --enable-impeller-vulkan
package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
endif
ifeq ($(BR2_PACKAGE_XORG7)$(BR2_PACKAGE_LIBXCB),yy)
FLUTTER_ENGINE_DEPENDENCIES += libxcb
else
define FLUTTER_ENGINE_VULKAN_X11_SUPPORT_FIXUP
$(SED) "s%vulkan_use_x11.*%vulkan_use_x11 = false%g" -i \
$(@D)/build_overrides/vulkan_headers.gni
endef
FLUTTER_ENGINE_PRE_CONFIGURE_HOOKS += FLUTTER_ENGINE_VULKAN_X11_SUPPORT_FIXUP
endif
ifeq ($(BR2_PACKAGE_WAYLAND),y)
FLUTTER_ENGINE_DEPENDENCIES += wayland
else
define FLUTTER_ENGINE_VULKAN_WAYLAND_SUPPORT_FIXUP
$(SED) "s%vulkan_use_wayland.*%vulkan_use_wayland = false%g" \
$(@D)/build_overrides/vulkan_headers.gni
endef
FLUTTER_ENGINE_PRE_CONFIGURE_HOOKS += FLUTTER_ENGINE_VULKAN_WAYLAND_SUPPORT_FIXUP
endif
# Generate a tarball if one does not already exist.
define FLUTTER_ENGINE_GENERATE_TARBALL
PATH=$(HOST_DIR)/share/depot_tools:$(BR_PATH) \
PYTHONPATH=$(HOST_DIR)/lib/python$(PYTHON3_VERSION_MAJOR) \
PUB_CACHE=$(FLUTTER_SDK_BIN_PUB_CACHE) \
$(FLUTTER_ENGINE_PKGDIR)/gen-tarball \
--dot-gclient $(TOPDIR)/$(FLUTTER_ENGINE_PKGDIR)/dot-gclient \
--jobs $(PARALLEL_JOBS) \
--scratch-dir $(@D)/dl-tmp \
--tarball-dl-path $(FLUTTER_ENGINE_TARBALL_PATH) \
--version $(FLUTTER_ENGINE_VERSION)
endef
FLUTTER_ENGINE_POST_DOWNLOAD_HOOKS += FLUTTER_ENGINE_GENERATE_TARBALL
define FLUTTER_ENGINE_EXTRACT_CMDS
$(call suitable-extractor,$(FLUTTER_ENGINE_TARBALL_PATH)) $(FLUTTER_ENGINE_TARBALL_PATH) \
| $(TAR) --strip-components=1 -C $(@D) $(TAR_OPTIONS) -
endef
package/flutter-engine: don't pollute user's home directory flutter-engine will forcibly create ~/.dart/ and ~/.flutter/ and store stuff in there. This is however quite dirty and pollutes the user's home, and will also not work when the home is read-only (e.g. shared in a container). Forcibly redirect flutter-engine to the same location where we redirected host-flutter-sdk-bin, using the same trick of redefining HOME as for host-flutter-sdk-bin. Ideally, we'd like to have some way to share this with all flutter-based packages, but we so far have only a few of them, so it is too early to even think about some commonalities (even less so about a shared infra). So we just duplicate the setting for now, this can be revisited later. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-11-17 17:33:49 +01:00
# We must set the home directory to the sdk directory or else flutter will
# place .dart, and .flutter in ~/.
package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
define FLUTTER_ENGINE_CONFIGURE_CMDS
cd $(@D) && \
rm -rf $(FLUTTER_ENGINE_BUILD_DIR) && \
PATH=$(HOST_DIR)/share/depot_tools:$(BR_PATH) \
PUB_CACHE=$(FLUTTER_SDK_BIN_PUB_CACHE) \
package/flutter-engine: don't pollute user's home directory flutter-engine will forcibly create ~/.dart/ and ~/.flutter/ and store stuff in there. This is however quite dirty and pollutes the user's home, and will also not work when the home is read-only (e.g. shared in a container). Forcibly redirect flutter-engine to the same location where we redirected host-flutter-sdk-bin, using the same trick of redefining HOME as for host-flutter-sdk-bin. Ideally, we'd like to have some way to share this with all flutter-based packages, but we so far have only a few of them, so it is too early to even think about some commonalities (even less so about a shared infra). So we just duplicate the setting for now, this can be revisited later. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-11-17 17:33:49 +01:00
HOME=$(HOST_FLUTTER_SDK_BIN_SDK) \
package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
./flutter/tools/gn \
$(FLUTTER_ENGINE_CONF_OPTS)
endef
define FLUTTER_ENGINE_BUILD_CMDS
cd $(@D) && \
PATH=$(HOST_DIR)/share/depot_tools:$(BR_PATH) \
PUB_CACHE=$(FLUTTER_SDK_BIN_PUB_CACHE) \
package/flutter-engine: don't pollute user's home directory flutter-engine will forcibly create ~/.dart/ and ~/.flutter/ and store stuff in there. This is however quite dirty and pollutes the user's home, and will also not work when the home is read-only (e.g. shared in a container). Forcibly redirect flutter-engine to the same location where we redirected host-flutter-sdk-bin, using the same trick of redefining HOME as for host-flutter-sdk-bin. Ideally, we'd like to have some way to share this with all flutter-based packages, but we so far have only a few of them, so it is too early to even think about some commonalities (even less so about a shared infra). So we just duplicate the setting for now, this can be revisited later. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-11-17 17:33:49 +01:00
HOME=$(HOST_FLUTTER_SDK_BIN_SDK) \
package/flutter-engine: new package There are many issues with this package: - The release tarballs from https://github.com/flutter/engine are in no state to compile. They are only for the use of gclient to download a source directory structure suitable to build the Flutter engine! If you download, extract and attempt to run `./tools/gn --no-goma --no-prebuilt-dart-sdk`, you receive the error message: `No such file or directory: 'flutter/flutter/third_party/gn/gn.' But wait! Wasn't the gn binary just called? No, that's a wrapper in the Flutter source tree that formats arguments to call the real gn binary. The real gn is not provided in the tarball but is downloaded via gclient (among many other supporting repositories.) Even worse, the flutter buildsystem depends on the .git dirs being present. (https://github.com/meta-flutter/meta-flutter/issues/271) This dependency means it is not possible to create a reproducible tarball from the downloaded sources, which is why there is no .hash file provided. I have asked the flutter project to release full tarballs suitable for compiling here: https://github.com/flutter/flutter/issues/130734 - Flutter engine includes a patched copy of clang that must be used to compile. Using a Buildroot-build clang results in linking warning and errors. As such, we depend on LLVM_ARCH_SUPPORTS but use the included clang for building. On the plus side, this saves time having to compile clang. - flutter-engine relies on the "PUB_CACHE", that is provided by flutter-sdk, so we need a build dependency, even if no tool from host-flutter-sdk-bin is used to build flutter-engine Tested with: - Debian 11 and 12 - Ubuntu 18.04, 20.04, and 22.04 - Fedora 38 - Per-package directories Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> [yann.morin.1998@free.fr: - search gclient.py from PATH - indent shell script with 4 spaces - reorganise schell script with prepare/cleanup - tweak comment about weirdness of flutter buildsystem - use suitable-extactor and TAR_OPTIONS - use FLUTTER_SDK_BIN_PUB_CACHE - add dependency to host-futter-sdk-bin (Adam) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-09-19 22:42:49 +02:00
$(HOST_DIR)/bin/ninja \
-j $(PARALLEL_JOBS) \
-C $(FLUTTER_ENGINE_BUILD_DIR)
endef
# Flutter-engine builds several host applications use for flutter development.
# One of those applications is gen_snapshot, which turns applications into
# usable .so files for the target architecture. Compiling a host version of
# flutter-engine would result in binaries producing host-architecture
# flutter applications .so files. As such, copy gen_snapshot to the host
# directory here and name it flutter_gen_snapshot for clarity.
FLUTTER_ENGINE_GEN_SNAPSHOT = $(HOST_DIR)/bin/flutter_gen_snapshot
define FLUTTER_ENGINE_INSTALL_GEN_SNAPSHOT
$(INSTALL) -D -m 0755 $(FLUTTER_ENGINE_BUILD_DIR)/clang_x64/gen_snapshot \
$(HOST_DIR)/bin/flutter_gen_snapshot
endef
FLUTTER_ENGINE_POST_INSTALL_STAGING_HOOKS += FLUTTER_ENGINE_INSTALL_GEN_SNAPSHOT
define FLUTTER_ENGINE_INSTALL_STAGING_CMDS
$(foreach i,$(FLUTTER_ENGINE_INSTALL_FILES),
$(INSTALL) -D -m 0755 $(FLUTTER_ENGINE_BUILD_DIR)/so.unstripped/$(i) \
$(STAGING_DIR)/usr/lib/$(i); \
)
$(INSTALL) -D -m 0755 $(FLUTTER_ENGINE_BUILD_DIR)/flutter_embedder.h \
$(STAGING_DIR)/usr/include/flutter_embedder.h
$(INSTALL) -D -m 0755 $(FLUTTER_ENGINE_BUILD_DIR)/icudtl.dat \
$(STAGING_DIR)/usr/share/flutter/$(FLUTTER_ENGINE_RUNTIME_MODE)/data/icudtl.dat
endef
define FLUTTER_ENGINE_INSTALL_TARGET_CMDS
$(foreach i,$(FLUTTER_ENGINE_INSTALL_FILES),
$(INSTALL) -D -m 0755 $(FLUTTER_ENGINE_BUILD_DIR)/so.unstripped/$(i) \
$(TARGET_DIR)/usr/lib/$(i); \
)
$(INSTALL) -D -m 0755 $(FLUTTER_ENGINE_BUILD_DIR)/icudtl.dat \
$(TARGET_DIR)/usr/share/flutter/$(FLUTTER_ENGINE_RUNTIME_MODE)/data/icudtl.dat
endef
$(eval $(generic-package))
Reference in New Issue Copy Permalink