Toolchain Container Images - Revision history

Jneuhauser: /* Images with native Debian GCC toolchain */ Drop duplicate

2022-10-27T10:03:23Z

Images with native Debian GCC toolchain: Drop duplicate

← Older revision		Revision as of 12:03, 27 October 2022
Line 22:		Line 22:
	The images are based on the Debian (slim-varaiant) image with <tt>cmake</tt>, <tt>ccache</tt>, <tt>curl</tt>, <tt>bc</tt>, <tt>lzop</tt>, <tt>xz-utils</tt>, <tt>jq</tt> and other tools additionally installed.		The images are based on the Debian (slim-varaiant) image with <tt>cmake</tt>, <tt>ccache</tt>, <tt>curl</tt>, <tt>bc</tt>, <tt>lzop</tt>, <tt>xz-utils</tt>, <tt>jq</tt> and other tools additionally installed.
	The Debian GCC toolchain is installed via the package <tt>debian-build-essential</tt>.		The Debian GCC toolchain is installed via the package <tt>debian-build-essential</tt>.

	~~You can checkout which commands are executed for each layer, and therefore also the installed packages, if you click on a specific tag in the tag tab.~~
	For example for image [https://hub.docker.com/layers/dhelectronics/debian-build-essential/stretch-amd64/images/sha256-12438156065c6cda9e5edcc8e25e553d78a9f14c2eaaadc7e7069e2515b93911?context=repo dhelectronics/debian-build-essential:stretch-amd64].

	Tags consists of a combination of the used version of Debian and the architecture of the image (e.g. <tt>buster-amd64</tt>).		Tags consists of a combination of the used version of Debian and the architecture of the image (e.g. <tt>buster-amd64</tt>).

Jneuhauser: Remove "This is made for our VM" as it works on any docker enabled linux

2022-10-27T10:02:59Z

Remove "This is made for our VM" as it works on any docker enabled linux

← Older revision		Revision as of 12:02, 27 October 2022
Line 5:		Line 5:

	For cross developing of applications we provide Docker container images with preinstalled toolchains.		For cross developing of applications we provide Docker container images with preinstalled toolchains.
	~~These are made for use by the [[Virtual Machine for Application Development\|VM for Application Development]].~~		You need to have Docker installed ([https://docs.docker.com/engine/install/ How to install Docker]), in our [[Virtual Machine for Application Development\|VM for Application Development]] starting with Stretch Vxx Docker is preinstalled and preconfigured.
	You need to have Docker installed ([https://docs.docker.com/engine/install/ How to install Docker]), in our VM starting with Stretch Vxx Docker is preinstalled and preconfigured.
	The container images are available [https://hub.docker.com/ Docker Hub].		The container images are available [https://hub.docker.com/ Docker Hub].

			You can check which commands are executed for each layer in an image, and thus the installed packages, by clicking a specific tag in the Tag tab of an image on [https://hub.docker.com/ Docker Hub].
			Here is an example for the image [https://hub.docker.com/layers/dhelectronics/debian-build-essential/stretch-amd64/images/sha256-12438156065c6cda9e5edcc8e25e553d78a9f14c2eaaadc7e7069e2515b93911?context=repo dhelectronics/debian-build-essential:stretch-amd64].

	'''Note''': For userspace application development, we recommend using the ELBE/Yocto-SDK which came with your root filesystem.		'''Note''': For userspace application development, we recommend using the ELBE/Yocto-SDK which came with your root filesystem.
Line 18:		Line 20:
	At the Docker repository <tt>[https://hub.docker.com/r/dhelectronics/debian-build-essential dhelectronics/debian-build-essential]</tt> images with the standard native GCC toolchain of Debian are located.		At the Docker repository <tt>[https://hub.docker.com/r/dhelectronics/debian-build-essential dhelectronics/debian-build-essential]</tt> images with the standard native GCC toolchain of Debian are located.

	The images are based on the Debian (slim-varaiant) image with <tt>cmake</tt>, <tt>ccache</tt>, <tt>curl</tt>, <tt>bc</tt>, <tt>lzop</tt>, <tt>xz-utils</tt> ~~and~~ <tt>jq</tt> additionally installed.		The images are based on the Debian (slim-varaiant) image with <tt>cmake</tt>, <tt>ccache</tt>, <tt>curl</tt>, <tt>bc</tt>, <tt>lzop</tt>, <tt>xz-utils</tt>, <tt>jq</tt> and other tools additionally installed.
	The Debian GCC toolchain is installed via the package <tt>debian-build-essential</tt>.		The Debian GCC toolchain is installed via the package <tt>debian-build-essential</tt>.

			You can checkout which commands are executed for each layer, and therefore also the installed packages, if you click on a specific tag in the tag tab.
			For example for image [https://hub.docker.com/layers/dhelectronics/debian-build-essential/stretch-amd64/images/sha256-12438156065c6cda9e5edcc8e25e553d78a9f14c2eaaadc7e7069e2515b93911?context=repo dhelectronics/debian-build-essential:stretch-amd64].

	Tags consists of a combination of the used version of Debian and the architecture of the image (e.g. <tt>buster-amd64</tt>).		Tags consists of a combination of the used version of Debian and the architecture of the image (e.g. <tt>buster-amd64</tt>).

Pzimmermann: Added more Information about the symlink-script, little corrections

2020-10-08T08:15:06Z

Added more Information about the symlink-script, little corrections

Show changes

Pzimmermann: Reflect split of the crossbuild toolchains, added documentation for removing images

2020-09-25T10:31:52Z

Reflect split of the crossbuild toolchains, added documentation for removing images

← Older revision		Revision as of 12:31, 25 September 2020
Line 33:		Line 33:
	Tests have indicated that building the Linux kernel with one thread on the native armhf compiler running on an amd64 machine with emulation is about 9 times slower than building the same kernel with one thread on the same machine via a crossbuild compiler.		Tests have indicated that building the Linux kernel with one thread on the native armhf compiler running on an amd64 machine with emulation is about 9 times slower than building the same kernel with one thread on the same machine via a crossbuild compiler.

	=== Images with crossbuild GCC toolchain ===		=== Images with Debian crossbuild GCC toolchain ===

	At the Docker repository <tt>[https://hub.docker.com/r/dhelectronics/debian-cross-build-essential dhelectronics/debian-cross-build-essential]</tt> images with the GCC toolchain for crosscompiling are located.		At the Docker repository <tt>[https://hub.docker.com/r/dhelectronics/debian-cross-build-essential dhelectronics/debian-cross-build-essential]</tt> images with the Debian GCC toolchain for crosscompiling are located.

	~~The~~ images are based on the ~~Debian~~ (slim-varaiant) ~~image with~~ <tt>build-essential</tt>, <tt>~~cmake~~</tt>, <tt>ccache</tt>, <tt>curl</tt>, <tt>bc</tt>, <tt>~~lzop~~</tt>, <tt>~~xz-utils~~</tt>, <tt>jq</tt>, <tt>~~git~~</tt> and <tt>~~ketchup~~</tt> additionally installed.		All images are based on the debian images (slim varaiant) and run on an amd64 host. The standard Debian crossbuild toolchain is used. This toolchain is installed via the package <tt>crossbuild-essentail-armhf</tt>.
	~~All~~ images ~~run on an amd64 host~~.		The packages <tt>bc</tt>, <tt>bison</tt>, <tt>build-essential</tt>, <tt>ca-certificates</tt>, <tt>ccache</tt>, <tt>cmake</tt>, <tt>curl</tt>, <tt>flex</tt>, <tt>git</tt>, <tt>jq</tt>, <tt>ketchup</tt>, <tt>libssl-dev</tt>, <tt>lzop</tt> and <tt>xz-utils</tt> additionally installed, so that the images are suited to build the Linux kernel.
	~~There are two kinds of images:~~

	~~==== Debian crossbuild toolchain (~~<tt>DIST</tt>~~) ====~~		The tags have the schema <tt>DIST</tt>-<tt>ARCH</tt>:

	~~These images are using the standard Debian crossbuild toolchain for~~ <tt>~~armhf~~</tt>. ~~This toolchain is installed via the package~~ <tt>~~crossbuild-essentail-armhf~~</tt>.		* '''<tt>DIST</tt>''': Determines which debian version the container image is based on.
	At the ~~moment there~~ are ~~images based on~~ <tt>~~stretch~~</tt> ~~and~~ <tt>~~buster~~</tt> ~~available~~.		* '''<tt>ARCH</tt>''': Determines which the architecture for which the cross toolchain builds. Note that the architecture names of Docker are used as an example Debian's <tt>armhf</tt> corresponds to <tt>arm32v7</tt>.

	==== Linaro/ARM toolchain (<tt>DIST</tt>-linaro-<tt>X</tt>) ====		=== Images with Linaro/ARM toolchain (<tt>DIST</tt>-linaro-<tt>X</tt>) ===

	These images use the toolchain of Linaro (up to GCC 7) or ARM (beginning with GCC 8) ~~in the version <tt>X</tt>~~ and uses ~~Debian <tt>DIST</tt>~~ as a basis for this image ~~(e.g. stretch-linaro-8)~~.		At the Docker repository <tt>[https://hub.docker.com/r/dhelectronics/linaro-cross-build dhelectronics/linaro-cross-build]</tt> images with the Linaro/ARM GCC toolchain for crosscompiling are located.

			These images use the toolchain of Linaro (up to GCC 7) or ARM (beginning with GCC 8) and uses the debian-slim image as a basis for this image.
	The toolchain is installed inside <tt>/opt</tt> and the <tt>PATH</tt>-variable is extened to include the directory with the binaries of the toolchain.		The toolchain is installed inside <tt>/opt</tt> and the <tt>PATH</tt>-variable is extened to include the directory with the binaries of the toolchain.
	At the ~~moment all~~ images are based on Debian <tt>~~stretch~~</tt> ~~and~~ the ~~GCC~~ versions 4.9, ~~6, 7 and 8~~ are ~~available~~.		The packages <tt>bc</tt>, <tt>bison</tt>, <tt>build-essential</tt>, <tt>ca-certificates</tt>, <tt>ccache</tt>, <tt>cmake</tt>, <tt>curl</tt>, <tt>flex</tt>, <tt>git</tt>, <tt>jq</tt>, <tt>ketchup</tt>, <tt>libssl-dev</tt>, <tt>lzop</tt> and <tt>xz-utils</tt> additionally installed, so that the images are suited to build the Linux kernel.

			The tags have the schema '''<tt>DIST</tt>-<tt>ARCH</tt>-<tt>VERSION</tt>''':

			* '''<tt>DIST</tt>''': Determines which debian version the container image is based on.
			* '''<tt>ARCH</tt>''': Determines which the architecture for which the cross toolchain builds. Note that the architecture names of Docker are used as an example Debian's `armhf` corresponds to <tt>arm32v7</tt>.
			* '''<tt>VERSION</tt>''': Determines which version of the toolchain is used. There are two kinds of versions: '''<tt>X.Y\[.Z\]-yyyy.mm</tt>''' does explictly point to a specific version of the toolchain. '''<tt>X</tt>''' points to the latest version of the major version of the toolchain, of which a image is existing. It is possible that some versions of the toolchain are skipped.

	== Using the containers ==		== Using the containers ==
Line 111:		Line 118:

	<nowiki>sudo docker-symlink-wrapper.py set-version cross-build stretch-linaro-6</nowiki>		<nowiki>sudo docker-symlink-wrapper.py set-version cross-build stretch-linaro-6</nowiki>

			=== Remove images which aren't needed anymore ===

			If you want to delete a container image which you do not need anymore you can enter:

			<tt>docker image rm <imagename+tag></tt>

			If you download a newer version of an image, the old version won't be automaticly removed, the old image won't be accessible by its name and tag. This kind of image is called "dangling image". To remove all dangling images (so they won't take any space on disk) you can enter

			<tt>docker image prune</tt>

	== Extend the container with libraries ==		== Extend the container with libraries ==

Pzimmermann at 07:03, 21 September 2020

2020-09-21T07:03:07Z

← Older revision		Revision as of 09:03, 21 September 2020
Line 58:		Line 58:
	You can start the container with the current work directory mounted into the container:		You can start the container with the current work directory mounted into the container:

	<tt>$ docker run -it --rm --mount type=bind,src=$(pwd)/,dst=$(pwd) --workdir $(pwd) dhelectronics/debian-cross-build-essential:buster</tt>		<tt>$ docker run -it --rm --mount type=bind,src=$(pwd)/,dst=$(pwd) --workdir $(pwd) --user $(id -u):$(id -g) dhelectronics/debian-cross-build-essential:buster</tt>

	After the container has started a console is open, now you can run any command to build the application (e.g. <tt>make all</tt>).		After the container has started a console is open, now you can run any command to build the application (e.g. <tt>make all</tt>).
Line 67:		Line 67:
	Alternativly you can call the build command directly at the run command of the container:		Alternativly you can call the build command directly at the run command of the container:

	<tt>$ docker run -it --rm --mount type=bind,src=$(pwd)/,dst=$(pwd) --workdir $(pwd) dhelectronics/debian-cross-build-essential:buster make all</tt>		<tt>$ docker run -it --rm --mount type=bind,src=$(pwd)/,dst=$(pwd) --workdir $(pwd) --user $(id -u):$(id -g) dhelectronics/debian-cross-build-essential:buster make all</tt>

	=== Use the symlink wrapper ===		=== Use the symlink wrapper ===

Pzimmermann at 10:42, 18 September 2020

2020-09-18T10:42:10Z

Pzimmermann at 09:30, 16 September 2020

2020-09-16T09:30:12Z

@@ Line 99: / Line 99: @@
 Now the symlinks are installed and every call to <tt>arm-linux-gnueabihf-gcc</tt> and the other symlinks will go into the container.
 To get the list of available versions of the toolchain you can use the following command:
@@ Line 109: / Line 111: @@
 == Extend the container with libraries ==
 === Create a modified container image ===
 === Install libraries at runtime ===

Pzimmermann at 14:43, 15 September 2020

2020-09-15T14:43:13Z

@@ Line 72: / Line 72: @@
 This script can create symlinks which point into container.
 If one of these symlink is called the script itself is called and the script does start the apropiate container for this symlink and calls the command inside of it and passes all arguments.
-It is possible to set the tag of the container image which should be started.
+It is possible to set the tag of the container image which should be started. This example uses the debian-cross-build-toolchain, what the commands are doing exactly, [[Docker_Symlink_Wrapper#Available_Commands|look at the documentation]].
 == Extend the container with libraries ==

Pzimmermann: Created page with "DH electronics provides Docker images with preinstalled toolchains. TOC == Introduction == For cross developing of applications we provide Docker container images with..."

2020-09-14T14:34:48Z

Created page with "DH electronics provides Docker images with preinstalled toolchains. __TOC__ == Introduction == For cross developing of applications we provide Docker container images with..."

New page

DH electronics provides Docker images with preinstalled toolchains.
__TOC__

== Introduction ==

For cross developing of applications we provide Docker container images with preinstalled toolchains.
These are made for use by the [[Virtual Machine for Application Development|VM for Application Development]].
You need to have Docker installed ([https://docs.docker.com/engine/install/ How to install Docker]), in our VM starting with Stretch Vxx Docker is preinstalled and preconfigured.
The container images are available [https://hub.docker.com/ Docker Hub].

'''Note''': For userspace application development, we recommend using the ELBE/Yocto-SDK which came with your root filesystem.
This is because the SDKs comes with all needed development headers and libraries for its respective root filesystem.

== Available Toolchains ==

=== Images with native Debian GCC toolchain ===

At the Docker repository <tt>[https://hub.docker.com/r/dhelectronics/debian-build-essential dhelectronics/debian-build-essential]</tt> images with the standard native GCC toolchain of Debian are located.

The images are based on the Debian (slim-varaiant) image with <tt>cmake</tt>, <tt>ccache</tt>, <tt>curl</tt>, <tt>bc</tt>, <tt>lzop</tt>, <tt>xz-utils</tt> and <tt>jq</tt> additionally installed.
The Debian GCC toolchain is installed via the package <tt>debian-build-essential</tt>.

Tags consists of a combination of the used version of Debian and the architecture of the image (e.g. <tt>buster-amd64</tt>).
Currently there is any combination of the Debian versions <tt>jessie</tt>, <tt>stretch</tt> and <tt>buster</tt> with the architectures <tt>amd64</tt>, <tt>arm32v5</tt> and <tt>arm32v7</tt> is possible.
Note that Docker uses another names for distinguishing the different architectures of ARM processors: <tt>arm32v5</tt> corresponds to Debian's <tt>armel</tt> while <tt>arm32v7</tt> corresponds to Debian's <tt>armhf</tt> architecture.

You can use QEMU's user mode emulation for running the ARM-containers on an amd64-machine, the resulting software of a build still runs on the respective ARM architecture.
To use this you have to install the packages <tt>binfmt-support</tt> and <tt>qemu-user-static</tt> on the host.
To activate this for the container:
* If your host is on Debian '''stretch or earlier''', you have to include the usermode emulator into the container at the start of your container. This can be done with a bind mount. Add the option <tt>--mount type=bind,src=/usr/bin/qemu-arm-static,dst=/usr/bin/qemu-arm-static</tt> to the run command of the container.
* If your host is on Debian '''buster or later''', this works automaticly. You don't have to alter the run command of the container.

=== Images with crossbuild GCC toolchain ===

At the Docker repository <tt>[https://hub.docker.com/r/dhelectronics/debian-cross-build-essential dhelectronics/debian-cross-build-essential]</tt> images with the GCC toolchain for crosscompiling are located.

The images are based on the Debian (slim-varaiant) image with <tt>build-essential</tt>, <tt>cmake</tt>, <tt>ccache</tt>, <tt>curl</tt>, <tt>bc</tt>, <tt>lzop</tt>, <tt>xz-utils</tt>, <tt>jq</tt>, <tt>git</tt> and <tt>ketchup</tt> additionally installed.
All images run on an amd64 host.
There are two kinds of images:

==== Debian crossbuild toolchain (<tt>DIST</tt>) ====

These images are using the standard Debian crossbuild toolchain for <tt>armhf</tt>. This toolchain is installed via the package <tt>crossbuild-essentail-armhf</tt>.
At the moment there are images based on <tt>stretch</tt> and <tt>buster</tt> available.

==== Linaro/ARM toolchain (<tt>DIST</tt>-linaro-<tt>X</tt>) ====

These images use the toolchain of Linaro (up to GCC 7) or ARM (beginning with GCC 8) in the version <tt>X</tt> and uses Debian <tt>DIST</tt> as a basis for this image (e.g. stretch-linaro-8).
The toolchain is installed inside <tt>/opt</tt> and the <tt>PATH</tt>-variable is extened to include the directory with the binaries of the toolchain.
At the moment all images are based on Debian <tt>stretch</tt> and the GCC versions 4.9, 6, 7 and 8 are available.

== Using the containers ==

=== Open console inside the container ===

You can start the container with the current work directory mounted into the container:

<tt>$ docker run -it --rm --mount type=bind,src=./,dst=/workdir dhelectronics/debian-cross-build-essential:buster</tt>

After the container has started a console is open, now you can run any command to build the application (e.g. <tt>make all</tt>).
When the build is finished, you can quit the console with <tt>CTRL+D</tt>.

=== Call the buildsystem at container start ===

Alternativly you can call the build command directly at the run command of the container:

<tt>$ docker run -it --rm --mount type=bind,src=./,dst=/workdir dhelectronics/debian-cross-build-essential:buster make all</tt>

=== Use the symlink wrapper ===

We created a python script called <tt>[[Docker Symlink Wrapper|docker-symlink-wrapper.py]]</tt> (Not yet downloadable).
This script can create symlinks which point into container.
If one of these symlink is called the script itself is called and the script does start the apropiate container for this symlink and calls the command inside of it and passes all arguments.
It is possible to set the tag of the container image which should be started.

== Extend the container with libraries ==

=== Create a modified container image ===

=== Install libraries at runtime ===

← Older revision		Revision as of 12:42, 18 September 2020
Line 30:		Line 30:
	* If your host is on Debian '''stretch or earlier''', you have to include the usermode emulator into the container at the start of your container. This can be done with a bind mount. Add the option <tt>--mount type=bind,src=/usr/bin/qemu-arm-static,dst=/usr/bin/qemu-arm-static</tt> to the run command of the container.		* If your host is on Debian '''stretch or earlier''', you have to include the usermode emulator into the container at the start of your container. This can be done with a bind mount. Add the option <tt>--mount type=bind,src=/usr/bin/qemu-arm-static,dst=/usr/bin/qemu-arm-static</tt> to the run command of the container.
	* If your host is on Debian '''buster or later''', this works automaticly. You don't have to alter the run command of the container.		* If your host is on Debian '''buster or later''', this works automaticly. You don't have to alter the run command of the container.
			Note that running a conatiner on emulated hardware affects the performance of the compiler.
			Tests have indicated that building the Linux kernel with one thread on the native armhf compiler running on an amd64 machine with emulation is about 9 times slower than building the same kernel with one thread on the same machine via a crossbuild compiler.

	=== Images with crossbuild GCC toolchain ===		=== Images with crossbuild GCC toolchain ===
Line 56:		Line 58:
	You can start the container with the current work directory mounted into the container:		You can start the container with the current work directory mounted into the container:

	<tt>$ docker run -it --rm --mount type=bind,src=./,dst=/workdir dhelectronics/debian-cross-build-essential:buster</tt>		<tt>$ docker run -it --rm --mount type=bind,src=$(pwd)/,dst=$(pwd) --workdir $(pwd) dhelectronics/debian-cross-build-essential:buster</tt>

	After the container has started a console is open, now you can run any command to build the application (e.g. <tt>make all</tt>).		After the container has started a console is open, now you can run any command to build the application (e.g. <tt>make all</tt>).
Line 65:		Line 67:
	Alternativly you can call the build command directly at the run command of the container:		Alternativly you can call the build command directly at the run command of the container:

	<tt>$ docker run -it --rm --mount type=bind,src=./,dst=/workdir dhelectronics/debian-cross-build-essential:buster make all</tt>		<tt>$ docker run -it --rm --mount type=bind,src=$(pwd)/,dst=$(pwd) --workdir $(pwd) dhelectronics/debian-cross-build-essential:buster make all</tt>

	=== Use the symlink wrapper ===		=== Use the symlink wrapper ===