Go to file
Maxime Ripard f1c092da8b python3: Port python2 patches to reduce the interpreter size
Some of the python2 patches were left behind when doing the python3
package. This was because the python build system can now autodetect
what packages can be built in the system.

However, some of these patches are actually useful to reduce drastically
the size of the interpreter.

This patch ports the relevant patches to the python3 package, and adds a
new patch to remove the idle3 IDE as well from the interpreter.

Fixes #5696

Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-06-28 22:02:44 +02:00
arch arm: update processor types 2013-06-16 21:12:36 +02:00
board
boot uboot: Add ELF target 2013-06-15 23:24:09 +02:00
configs configs: bump kernel in rpi_defconfig for misc fixes 2013-06-27 15:51:02 +02:00
docs Add documentation for the header style 2013-06-16 21:40:18 +02:00
fs Normalize separator size to 80 in remaining makefiles 2013-06-20 17:32:07 +02:00
linux linux: bump 3.9.x stable version 2013-06-28 11:35:07 +02:00
package python3: Port python2 patches to reduce the interpreter size 2013-06-28 22:02:44 +02:00
support Normalize separator size to 80 in remaining makefiles 2013-06-20 17:32:07 +02:00
system system/permissions: make /root group+others non-writable 2013-06-23 21:51:57 +02:00
toolchain kernel-headers: bump 3.{0, 4, 9}.x stable version 2013-06-28 11:34:58 +02:00
.defconfig
.gitignore
CHANGES
Config.in
Config.in.legacy
COPYING
Makefile Normalize separator size to 80 in remaining makefiles 2013-06-20 17:32:07 +02:00
Makefile.legacy

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) Use your shiny new root filesystem. Depending on which sort of
    root filesystem you selected, you may want to loop mount it,
    chroot into it, nfs mount it on your target device, burn it
    to flash, or whatever is appropriate for your target system.

You do not need to be root to build or run buildroot.  Have fun!

Offline build:
==============

In order to do an offline-build (not connected to the net), fetch all
selected source by issuing a
$ make source

before you disconnect.
If your build-host is never connected, then you have to copy buildroot
and your toplevel .config to a machine that has an internet-connection
and issue "make source" there, then copy the content of your dl/ dir to
the build-host.

Building out-of-tree:
=====================

Buildroot supports building out of tree with a syntax similar
to the Linux kernel. To use it, add O=<directory> to the
make command line, E.G.:

$ make O=/tmp/build

And all the output files (including .config) will be located under /tmp/build.

More finegrained configuration:
===============================

You can specify a config-file for uClibc:
$ make UCLIBC_CONFIG_FILE=/my/uClibc.config

And you can specify a config-file for busybox:
$ make BUSYBOX_CONFIG_FILE=/my/busybox.config

To use a non-standard host-compiler (if you do not have 'gcc'),
make sure that the compiler is in your PATH and that the library paths are
setup properly, if your compiler is built dynamically:
$ make HOSTCC=gcc-4.3.orig HOSTCXX=gcc-4.3-mine

Depending on your configuration, there are some targets you can use to
use menuconfig of certain packages. This includes:
$ make HOSTCC=gcc-4.3 linux-menuconfig
$ make HOSTCC=gcc-4.3 uclibc-menuconfig
$ make HOSTCC=gcc-4.3 busybox-menuconfig

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@uclibc.org