meta-crosstools is a repository of bitbake recipes that can be used to build both native and cross compilers for Ada, C and C++. Configuration files exists for the following host/target combos. Native in this case means x86_64-pc-linux-gnu.
| Name | Host | Target | Status | Libc | Kernel | Features |
|---|---|---|---|---|---|---|
| native | x86_64-pc-linux-gnu | x86_64-pc-linux-gnu | Ok | glibc-2.28 | 4.14 | gprbuild, c, c++, ada, gdb |
| native-mipsel | x86_64-pc-linux-gnu | mipsel-unknown-linux-gnu | Ok | eglibc-2.19 | 4.9 | c, c++, ada, gdb |
| native-rpi3 | x86_64-pc-linux-gnu | arm-unknown-linux-gnueabihf | Ok | glibc-2.24 | 4.9 | c, c++, ada, gdb |
| native-cris | x86_64-pc-linux-gnu | cris-elf | Ok | newlib-2.5.0 | 4.14 | c, c++, ada, gcc, gdb |
| native-mingw | x86_64-pc-linux-gnu | x86_64-w64-mingw32 | Ok | mingw-w64-git | N/A | c, c++, ada, gdb |
| mingw-mingw | x86_64-w64-mingw32 | x86_64-w64-mingw32 | Ok | mingw-w64-git | N/A | gprbuild, c, c++, ada, gdb |
| mingw-mipsel | x86_64-w64-mingw32 | mipsel-unknown-linux-gnu | Ok | eglibc-2.19 | 4.9 | c, c++, ada, gdb |
| mingw-rpi3 | x86_64-w64-mingw32 | arm-unknown-linux-gnueabihf | Ok | glibc-2.24 | 4.9 | c, c++, ada, gdb |
It is however easy to add support for additional toolchains.
The major usecase for this component is to be the backbone builder for tcb, which is a go/docker tool that makes it possible to build these toolchains on platforms that support go/docker.
Assuming you come frome a fresh and recent debian-based install, you can do the following to get up and running.
>sudo apt install -y build-essential gnat git locales python3 wget m4 gawk unzip nano texinfo rsync
>mkdir $HOME/toolchains
>cd toolchains
>git clone https://github.com/openembedded/bitbake.git
>git clone https://github.com/staffano/meta-crosstools.git
>export PATH=$HOME/bitbake/bin:$PATH
>export PYTHONPATH=$HOME/bitbake/bin:$PYTHONPATH
>mkdir -p $HOME/toolchains/build/conf
>printf "BBPATH = \"${TOPDIR}\"\nBBFILES ?= \"\"\nBBLAYERS ?= \"${HOME}/toolchains/meta-crosstools\"\n" >> ${HOME}/toolchains/build/conf/bblayers.conf
>printf "BB_NUMBER_THREADS = \"4\"\nMAKE_JX := \"-j6\"\n" >> ${HOME}/toolchains/build/conf/local.conf
>cd build
>bitbake -R ../meta-crosstools/conf/toolchains/native-mipsel.conf image
...
There is a dependence to having certain toolchains installed before a toolchains can be built. This dependency is expressed inside the .conf files using the following syntax:
# /// DEPENDENCIES=native,native-mingw,native-mipsel
The conf files take care of adding the path to the required toolchains relative to the ${IMAGES} variable. If you install the required toolchains elsewhere, you need to add the path to these toolchains yourself.
Say you want to build a toolchain for crosscompiling to mingw, then you first need to build the native toolchains and then the native-mingw toolchain.
>bitbake -R conf/toolchains/native.conf image
>bitbake -R conf/toolchains/native-mingw.conf imageBy running the image target, the toolchain is installed in the tmp/IMAGES directory.
| Package | Version |
|---|---|
| binutils | 2.31.1/2.281 |
| eglibc | 2.19 |
| expat | 2.1.0 |
| gcc | 8.2.0 |
| gdb | 8.1.1 |
| glibc | 2.28 / 2.242 |
| gmp | 6.1.2 |
| isl | 0.18 |
| linux-headers | 3.2 / 4.9 / 4.14 / rpi3_4.9 |
| mingw-w64 | git (master) |
| mpc | 1.0.3 |
| mpfr | 3.1.6 |
| ncurses | 6.0 |
| newlib | 2.5.0 |
1: glibc-4.9 is not compatible with binutils >= 2.29.
2: Raspbian currently relies on glibc-2.24
| Package | Version |
|---|---|
| gprbuild | git (SRCREV=23f880d69854e4900248d923c9790057da44d492) |
| xmlada | git (master) |
See License