Currently, one may only specify one list of arguments that are passed to
several scripts (BR2_ROOTFS_PRE_BUILD_SCRIPT, BR2_ROOTFS_POST_BUILD_SCRIPT,
BR2_ROOTFS_POST_FAKEROOT_SCRIPT and BR2_ROOTFS_POST_IMAGE_SCRIPT_ARGS).
So one has to be careful that the arguments for these scripts do noti
collide.
To allow specifiying dedicated arguments to each type of scripts, new
config options are introduced. For backward compatibility the value of
BR2_ROOTFS_POST_SCRIPT_ARGS is still passed to the scripts. But now one
can add specific arguments from the new config option.
Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
[yann.morin.1998@free.fr:
- mention common args in help texts
- slight coding style beautification
- slight rewording in commit log
]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Currently, we pass BR2_ROOTFS_POST_SCRIPT_ARGS to each of the scripts in
BR2_ROOTFS_PRE_BUILD_SCRIPT, but the option is not exposed in menuconfig
when only pre-build scripts are used.
Add the pre-build scripts to the condition exposing the extra args
option.
Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Drop patch which is now upstream.
CONTRIBUTING.md hash changed due to details added:
5481ba1568
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Reviewed-By: Marcus Hoffmann <buildroot@bubu1.eu>
Tested-by: Marcus Hoffmann <buildroot@bubu1.eu>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Removed patch 0001 and instead added new configure option
--disable-multi-os-directory which was added upstream:
877ea9bf9a
Removed patch 0003 due to various upstream fixes for mips soft-float
support since its addition in 2016:
https://github.com/libffi/libffi/commits/master/src/mips
Renumbered remaining patch.
Updated license hash due to copyright year bump:
91739a1a91
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Reviewed-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Tested-by: Adam Duskett <adam.duskett@amarulasolutions.com>
[yann.morin.1998@free.fr: fix check-package]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
- Drop patch (already in version)
- Drop LOG4CXX_IGNORE_CVES as CVE-2023-31038 has been fixed in 1.1.0
- Add unixodbc optional dependency
https://logging.apache.org/log4cxx/latest_stable/changelog.html#1.1.0
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
We need to migrate python-bleak to the pep517 poetry-core backend
as setuptools is not supported when building with a pep517 frontend.
This package currently builds using setuptools as we do not yet
use setuptools with a pep517 build frontend. The package contains
a setuptools fallback which only can be used when using setuptools
without a pep517 frontend as the pep517 frontend will only use the
build backend specified in the package pyproject.toml which is
poetry-core and not setuptools.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
We need to add a patch which selects the correct flit build
backend.
As flit is configured as the pep517 build backend for aiologstash
we need to migrate from setuptools to flit prior to migrating
setuptools to pep517 as the frontend will not fall back to using
setuptools once migrated.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
When building with a pep517 frontend we need to use the specified
build backend as opposed to the fallback setuptools build which
only works when not building with a pep517 frontend.
Fixes:
ERROR Backend 'hatchling.build' is not available.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
When migrating to setuptools with pep517 support we need to add
host-python-cython which is a pep517 build dependency for pyyaml.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
[Arnout: order dependencies alphabetically]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
We need to migrate python-terminaltables to the pep517 poetry-core
backend as setuptools is not supported when building with a pep517
frontend.
This package currently builds using setuptools as we do not yet
use setuptools with a pep517 build frontend. The package contains
a setuptools fallback which only can be used when using setuptools
without a pep517 frontend as the pep517 frontend will only use the
build backend specified in the package pyproject.toml which is
poetry-core and not setuptools. Thus, specifying setuptools as the build
backend is simply wrong.
The current release of python-terminaltables still uses poetry rather
than poetry-core as a build backend. poetry is much more heavyweight, it
would need to pull in a large number of build dependencies. Therefore,
include an upstream patch to switch from poetry to poetry-core.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
[Arnout: use a patch instead of sed]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
When migrating to setuptools with pep517 support we need to add
host-python-cython which is a pep517 build dependency for
python-sqlalchemy.
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Tested-By: Flávio Tapajós <flavio.tapajos@newtesc.com.br>
Signed-off-by: Flávio Tapajós <flavio.tapajos@newtesc.com.br>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
(cherry picked from commit cc34b5b2ab)
[Peter: drop Makefile/Vagrantfile changes]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
(cherry picked from commit c2e4b76d03)
[Peter: drop Makefile/Vagrantfile changes]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
David's e-mail is bouncing:
<david.bachelart@bbright.com>: host aspmx.l.google.com[2a00:1450:400c:c0c::1a]
said: 550-5.1.1 The email account that you tried to reach does not exist.
Please try 550-5.1.1 double-checking the recipient's email address for
typos or 550-5.1.1 unnecessary spaces. For more information, go to 550
5.1.1 https://support.google.com/mail/?p=NoSuchUser
n19-20020a05600c4f9300b00414111d4396si2497070wmq.117 - gsmtp (in reply to
RCPT TO command)
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
This is the current version on main branch.
For Apache-2.0 licensed fonts, there are new fonts, and fonts that
have been removed.
For OFL-1.0 fonts, there are new fonts, fonts removed, but also fonts
where the license file has changed. In this latter case, the changes
are http:// to https:// in some URLs, copyright year changes, a minor
update of the OFL license (from Feb 1, 2007 to Feb 26, 2007, which has
a small rewording), text rewrapping.
Signed-off-by: Christian Hitz <christian.hitz@bbv.ch>
[Thomas: extracted from
https://patchwork.ozlabs.org/project/buildroot/patch/20240228145013.411919-2-christian@klarinett.li/,
added details about license file changes]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The current command listed in the hash file to generate the list of
license files hashes does not sort files. Due to this, depending on
who runs the command, the result can potentially be different.
In order to address this, this commit changes the command to sort
license files, and updates the hash file accordingly.
Signed-off-by: Christian Hitz <christian.hitz@bbv.ch>
[Thomas: extract from
https://patchwork.ozlabs.org/project/buildroot/patch/20240228145013.411919-2-christian@klarinett.li/
into a separate patch]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
In commit ebe5d9edfe ("boot, package,
support, toolchain: switch to 2 spaces for the hash file"), all hash
files were migrated to use 2 spaces as the separator.
However, in the googlefontdirectory hash file, a command is present in
a comment to indicate how to generate the part of the hash file that
provides the list of license file hashes. This command was not updated
as part of ebe5d9edfe, so it still emits
a result in which a single space is used a separator between the hash
type (sha256) and the hash value.
This commit fixes that by using a 2-space separator.
Signed-off-by: Christian Hitz <christian.hitz@bbv.ch>
[Thomas: extracted from
https://patchwork.ozlabs.org/project/buildroot/patch/20240228145013.411919-2-christian@klarinett.li/
into a separate patch]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
(cherry picked from commit 9a3d34139b)
[Peter: drop Makefile change]
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Add 0005-skip-configuration-dependency-if-unit-tests-are-disa.patch, which
fixes gtk+-3.0 being an unconditional requirement.
Other changes:
Flutter 3.19.x made Wayland and X11 an unconditional requirement, resulting in
the following errors when compiling:
"""
../../flutter/third_party/swiftshader/src/WSI/libWaylandClient.hpp:18:10: fatal error: 'wayland-client.h' file not found
18 | #include <wayland-client.h>
| ^~~~~~~~~~~~~~~~~~
../../flutter/third_party/swiftshader/src/WSI/WaylandSurfaceKHR.cpp:15:
../../flutter/third_party/swiftshader/src/WSI/WaylandSurfaceKHR.hpp:22:10: fatal error: 'wayland-client.h' file not found
22 | #include <wayland-client.h>
| ^~~~~~~~~~~~~~~~~~
1 error generated.
[1369/11229] CC obj/flutter/third_party/sqlite/sqlite.sqlite3.o
"""
After raising an issue found here:
https://github.com/flutter/flutter/issues/144635 and after several hours of
searching, the problem is https://github.com/flutter/buildroot/commit/d01da2716
which hardcodes the following values if building for a Linux platform:
- ozone_platform_x11 = true
- ozone_platform_wayland = true
As upstream maintainers listed the above as low priority (P3), a simple fix is
to add two additional sed calls in FLUTTER_ENGINE_VULKAN_X11_SUPPORT_FIXUP and
FLUTTER_ENGINE_VULKAN_WAYLAND_SUPPORT_FIXUP which set ozone_platform_x11 and
ozone_platform_wayland to the appropriate values.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
The maintainers of the flutter-gallery package archived the project as of
February 16, 2024. In addition, the flutter-gallery package is incompatible
with Flutter 3.19.x. Now that the flutter tests do not use this package, it
is safe to drop it.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
The maintainers of the flutter-gallery package archived the project as of
February 16, 2024. In addition, the flutter-gallery package is incompatible
with Flutter 3.19.x. Because of these problems, using the flutter-gallery
package as the testing application for Flutter is no longer reasonable nor
maintainable.
However, it is reasonable to use the flutter-markdown-example package from
flutter-packages, as it is a first-party application updated regularly and
often automatically, ensuring compatibility with the latest versions of
Flutter.
- Switch the package used for Flutter testing from flutter-gallery to
flutter-markdown-example
- Rename flutter-gallery.service to flutter-markdown-example.service
- Change /usr/share/flutter/gallery/release/ to
/usr/share/flutter/flutter_markdown_example/release/
- Run `systemctl is-active flutter-markdown-example` instead of
`systemctl is-active flutter-gallery`
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Displays a custom "Hello, World!" custom widget in a
remote Flutter widget (RFW) for use by a remote widget.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This package uses the NetworkImageWithRetry method to download the Flutter
logo. The package requires ca-certificates, or else SSL errors occur when
the application attempts to download the image.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
A Flutter plugin that manages files and interactions with file dialogs.
This package contains a dart_plugin_registrant dart file, much like the
flutter-gallery package. The build commands contain the three
lines from the flutter-gallery package referencing the
dart_plugin_registrant dart file.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This package provides two multi-sized tiles and different layouts:
Stagger and Wrap.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This package provides examples of the following animations:
- OpenContainer
- SharedAxisTransition
- FadeThroughTransisiton
- FadeScaleTransition
The package also provides a toggle that slows all the animations.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This package provides a nice-looking Gmail lookalike application using
Material 3.
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
The maintainers of the flutter-gallery package archived the project as of
February 16, 2024, necessitating a new reference package for users to port
their Flutter applications to Buildroot. The flutter-packages repository is
the perfect candidate for a reference package for several reasons:
- It contains the source code for Flutter's first-party packages.
- Many of the packages contain examples.
- Many of the examples include Linux-specific examples.
- The repository is updated regularly and often automatically, ensuring
compatibility with the latest versions of Flutter.
However, the layout of the flutter-packages repository stores all of the
examples in sub-directories, which creates an organizational problem; either
every example application is stored in packages/flutter-example-${name}, with
the version, site, site_method, license, license_files, and dependencies of
each package independent from each other, or, each example application is in a
sub-directory of the flutter-packages directory, and flutter-packages acts as
the primary source of the above variables.
As option one is a nightmare to maintain, this patch provides option two,
which only necessitates the use of two features rarely used together in
Buildroot: $(PKG_NAME)_DL_SUBDIR and $(PKG_NAME)_SOURCE. With these two options
appropriately set, each sub-package uses the flutter-packages source tarball,
which downloads once, saving time, disk space, bandwidth, and future
maintenance headaches.
Three variables in the .mk file help with subsequent patches that add more
example applications:
- FLUTTER_MARKDOWN_EXAMPLE_PKG_NAME:
- Set to the name of the application.
- FLUTTER_MARKDOWN_EXAMPLE_INSTALL_DIR:
- It uses the PKG_NAME variable to set the installation directory.
- FLUTTER_MARKDOWN_EXAMPLE_SUBDIR:
- Provides the directory in which to build the package.
With the above variables, adding subsequent packages involves minimal effort:
- Copy, paste, and rename a sub-directory to a new package name.
- Set the above variables to new names and directories.
- Check to see if there are any new build commands, such as specifying a
dart_plugin_registrant.dart file.
Another option that seems appealing is to have a single package, with the
Config.in options to select which example(s) to build. However, this option
does not work well for two reasons:
- The logic between this package and the flutter-gallery package it replaces
would be very different. As the flutter-gallery package acts as a reference
package for other users, changing the logic would make the package difficult
to parse and possibly useless for other users to use as a reference when
porting their Flutter-based applications to Buildroot.
- Not all packages in the flutter-package repository use the same directory
structure. Take, for example, the flutter-rfw-local-example. The build
directory is located at rfw/example/local, whereas most other packages are
at ${pkg_name}/example, which makes a pure-foreach loop impossible.
These packages are intended for reference, and changing the logic instead of
using the same would hinder users from attempting to port their Flutter
applications to Buildroot. As such, this option is ruled out for the above
reasons.
The first package in this series is a Markdown example application that
displays several Markdown formatting demos. However, it does not support inline
HTML. This package also lacks a dart_plugin_registrant file, and unlike the
flutter-gallery package, the lines referencing such a file are not included in
the build commands. This is not a problem, but is something to note.
Also, the `FLUTTER_RUNTIME_MODES=$(FLUTTER_ENGINE_RUNTIME_MODE)` line from the
configure commands is not copied from the flutter-gallery package, as it was
included by mistake and did not have any effecton the clean command.
Note: The version of the flutter-packages git hash is set to
947e34ce9fedcdd6750b54eb1cc74b854b49ab48, the last commit that supported
Flutter 3.16.x. Newer versions require Flutter 3.19.x
Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Upgrade Go to the latest v1.22.x point release, go1.22.1.
This requires go-bootstrap-stage3 at version go1.21.8:
See: https://go.dev/doc/go1.22#bootstraphttps://go.dev/doc/devel/release#go1.22.1
Signed-off-by: Christian Stewart <christian@aperture.us>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Add a third bootstrap stage with Go1.21.x necessary for go1.22 bootstrap.
go-bootstrap-stage1 is Go1.4.x, the final version to support bootstrap using a C
compiler (later versions require the Go compiler for bootstrapping).
See: https://go.dev/doc/install/source#bootstrapFromSource
go-bootstrap-stage2 is Go 1.19.13, the last version to support bootstrap using
the Go1.4.x compiler.
go-bootstrap-stage3 is Go 1.21.8, the last version to support bootstrap using
the Go1.19.13 compiler. Go 1.20 requires a minimum of go 1.17.13 to bootstrap.
See: https://go.dev/doc/go1.20#bootstrap
This patch is in preparation for bumping the host-go package to >go1.22.x, which
requires a minimum of Go1.20.x for bootstrap.
See: https://go.dev/doc/go1.22#bootstrap
Signed-off-by: Christian Stewart <christian@aperture.us>
[Arnout: add GOCACHE definition]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Update to the latest 1.19.x version available.
Signed-off-by: Christian Stewart <christian@aperture.us>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
The project now has its own group on github, so switch to that one. Also
update the Config.in URL to point to that one - the sourceforge project
is pretty much abandoned.
What's Changed
- add UTF-8 support for Client7z by @flyfishzy in #214
- fix issue 130 by @jinfeihan57 in 295dac8
Signed-off-by: André Zwing <nerv@dawncrow.de>
[Arnout: also update URL; extend commit message]
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Commit 24e996d14d (package/xvisor: fix build without python interpreter)
added a dependency on host-python3 for the d2c.py script, but this script
does not use any non-standard python modules so we can instead use
BR2_PYTHON3_HOST_DEPENDENCY to only build host-python3 if the build host
does not have python3.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Commit 9496ff57e5 (package/openssh: bump to version 9.7p1) dropped
0001-better-detection-of-broken-fzero-call-used-regs.patch but forgot to
drop the autoreconf. Do that now.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Commit 748fc4be21 (package/pkg-utils.mk: remove trailing slash in pkgdir
definition) broke the docs generation logic:
make manual-html
>>> Preparing the manual sources...
>>> Generating HTML manual...
a2x: ERROR: missing ASCIIDOC_FILE: /home/peko/source/buildroot/output/build/docs/manual/manual.adoc
make: *** [docs/manual/manual.mk:12: /home/peko/source/buildroot/output/docs/manual/manual.html] Error 1
As it now ends up with the .adoc file one level below
(../docs/manual/manual/manual.adoc). The reason is that the pkgdir macro is
used to define $(2)_DOCDIR, which is passed to rsync:
rsync -a docs/manual /home/peko/source/buildroot/output/build/docs/manual
Fix it by appending a / to the rsync arguments like we do elsewhere.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
- Refresh first and fourth patches
- Drop second nad third patches (already in version)
https://sourceforge.net/p/giflib/code/ci/5.2.2/tree/NEWS
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
