Go to file
Thomas Petazzoni c577ad692f package/pkg-python: use --single-version-externally-managed for host setuptools
Currently, host Python packages that use setuptools are installed as
Python Eggs, i.e they are installed in
$(HOST_DIR)/lib/python2.7/site-packages/Something-<version>.egg. Once
installed, each Python Egg is registered to a file called
$(HOST_DIR)/lib/python2.7/site-packages/easy-install.pth. This file is
read by the Python interpreter so that the installation location of
each Egg is added to the Python path, and can be found by the Python
interpreter.

However, the fact that the installation of different Python modules
need to update a common file is clearly not compatible with
per-package directories and top-level parallel build.

To fix this, we avoid using Python Eggs using the same
--single-version-externally-managed option that we use for target
modules. This option is normally meant for distributions packaging
Python modules, and can therefore only be used if either --record (to
record the list of files being installed) or --root is
passed. --root=/ works fine and was suggested by
https://stackoverflow.com/questions/6301003/stopping-setup-py-from-installing-as-egg/33791008#33791008.

With this change, host Python modules installed by setuptools are now
installed in the "regular" way, i.e directly in
$(HOST_DIR)/lib/python2.7/site-packages/mako for host-python-mako.

This makes the installation of host Python modules more similar to the
one of target modules, and makes it compatible with per-package
directory support and top-level parallel build.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Reviewed-by: Asaf Kahlon <asafka7@gmail.com>
Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-01-01 11:16:33 +01:00
arch arch/arm: add an armv8.3a core 2018-12-30 16:10:04 +01:00
board board/pc: ensure grub.cfg is copied to target filesystem 2018-12-31 18:45:53 +01:00
boot boot/grub: fix grub-mkimage with binutils >= 2.31 2018-12-13 21:37:08 +01:00
configs board/pc: ensure grub.cfg is copied to target filesystem 2018-12-31 18:45:53 +01:00
docs package/luarocks: add buildroot addon 2018-12-31 17:40:58 +01:00
fs fs/common.mk: make sure that static devices from packages are created 2018-12-04 21:53:14 +01:00
linux pcm-tools: new package 2018-12-08 10:44:05 +01:00
package package/pkg-python: use --single-version-externally-managed for host setuptools 2019-01-01 11:16:33 +01:00
support Makefile: offload .gitlab-ci.yml generation 2018-12-09 21:30:24 +01:00
system skeleton: use BR2_SYSTEM_DEFAULT_PATH as default PATH 2018-12-31 14:32:44 +01:00
toolchain Merge branch 'next' 2018-12-02 08:16:10 +01:00
utils utils/scanpypi: write _SOURCE only when needed 2018-12-30 17:42:32 +01:00
.defconfig
.flake8
.gitignore
.gitlab-ci.yml .gitlab-ci.yml: regenerate for proper defconfig ordering 2018-12-16 16:14:56 +01:00
.gitlab-ci.yml.in .gitlab-ci.yml: store .config files as artefacts for defconfig tests 2018-12-09 17:31:13 +01:00
CHANGES Update for 2018.02.9 2018-12-20 14:21:49 +01:00
Config.in
Config.in.legacy system cfg: remove mkpasswd MD5 format option 2018-12-15 11:33:29 +01:00
COPYING
DEVELOPERS package/libeastl: new package 2018-12-31 14:14:22 +01:00
Makefile Makefile: offload .gitlab-ci.yml generation 2018-12-09 21:30:24 +01:00
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 Freenode IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches