4686fb32a0
Some projects have been removing their setup.py shims under the assumption that they are not needed due to setuptools being usable via pep517, however this is not actually the case as it is not possible to bootstrap setuptools without setup.py style builds as setuptools has a dependency on wheel when being used via pep517 which is itself not installable via pep517 as that would create a dependency cycle between wheel and setuptools(which means wheel itself must use a legacy setup.py build/installation for itself). In addition our pep517 toolchain itself requires setuptools for building/installing dependencies, although it would appear these dependencies will eventually move to flit. Until this is resolved we must use setup.py style builds for setuptools packages. Since it is not yet possible to convert setup.py based setuptools builds to pep517 based setuptools builds we simply need to execute the setuptools shim code directly if the setup.py file is missing. See: https://setuptools.pypa.io/en/latest/setuptools.html#setup-cfg-only-projects Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Tested-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> |
||
|---|---|---|
| arch | ||
| board | ||
| boot | ||
| configs | ||
| docs | ||
| fs | ||
| linux | ||
| package | ||
| support | ||
| system | ||
| toolchain | ||
| utils | ||
| .clang-format | ||
| .defconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| 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