eafb370e52
The check-package tool requires some PyPi package to be installed before it can run. This is typically done by manually installing them into the user's global Python environment or setting up a virtual environment, then manually installing each dependency. Python recently defined a format for managing script dependencies as inline metadata[1]. This can be used with the `uv` tool to run a Python script and automatically install the minimum required version of Python and PyPi dependencies. With this change, it's now possible to run check-package with uv run -s ./utils/check-package Note that, because check-package does not have the '.py' file extension we must specify the `-s` or `--script` argument. That argument was added very recently in release 0.4.19[2]. I set the minimum python to 3.9 as that is the oldest version still supported[3]. I verified 3.9 works by running uv run -p 3.9 -s ./utils/check-package `git ls-tree -r --name-only HEAD` --ignore-list=.checkpackageignore [1] https://packaging.python.org/en/latest/specifications/inline-script-metadata/#script-type [2] https://github.com/astral-sh/uv/releases/tag/0.4.19 [3] https://devguide.python.org/versions/ Signed-off-by: Brandon Maier <brandon.maier@collins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> (cherry picked from commit 6ffcdb52e80b63e68c890aed52ff7f4d00e079b8) Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
|---|---|---|
| .github | ||
| .gitlab/issue_templates | ||
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .b4-config | ||
| .checkpackageignore | ||
| .clang-format | ||
| .defconfig | ||
| .editorconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .shellcheckrc | ||
| CHANGES | ||
| Config.in | ||
| Config.in.legacy | ||
| COPYING | ||
| DEVELOPERS | ||
| Makefile | ||
| Makefile.legacy | ||
| README | ||
Buildroot is a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation. The documentation can be found in docs/manual. You can generate a text document with 'make manual-text' and read output/docs/manual/manual.text. Online documentation can be found at http://buildroot.org/docs.html To build and use the buildroot stuff, do the following: 1) run 'make menuconfig' 2) select the target architecture and the packages you wish to compile 3) run 'make' 4) wait while it compiles 5) find the kernel, bootloader, root filesystem, etc. in output/images You do not need to be root to build or run buildroot. Have fun! Buildroot comes with a basic configuration for a number of boards. Run 'make list-defconfigs' to view the list of provided configurations. Please feed suggestions, bug reports, insults, and bribes back to the buildroot mailing list: buildroot@buildroot.org You can also find us on #buildroot on OFTC IRC. If you would like to contribute patches, please read https://buildroot.org/manual.html#submitting-patches