Building AsteroidOS - Revision history

Beroset: /* Build with containers */ add instructions on customizing the toolchain container

2026-07-20T14:24:06Z

Build with containers: add instructions on customizing the toolchain container

@@ Line 90: / Line 90: @@
 From a user's point of view, Docker and podman are quite similar and accept almost all of the exact same commands, but there are some difference.  The most significant differences for building Asteroid are that podman does not use a daemon and can be run "rootless" (that is, as a non-root user).  This makes some things a bit easier, but either can be used.
 == Setup ==
@@ Line 119: / Line 118: @@
 In this example, we will build AsteroidOS for <code>dory</code>(the LG G Watch).  To build for a different watch than the LG G Watch, use its corresponding codename instead of <code>dory</code> when executing the <code>docker run ...</code> command.  You can find the codenames for the supported watches on the [https://asteroidos.org/watches/ Watches page].
 Assuming that you have carefully followed the instructions so far and are in the <code>asteroid</code> directory, you can now build the software.
@@ Line 170: / Line 167: @@
 If this step was successful, you can proceed to [[#Installing|Installing]] below.
 = Installing =

Beroset: /* Building the software */ corrected previous edit

2026-07-13T12:41:08Z

Building the software: corrected previous edit

← Older revision		Revision as of 12:41, 13 July 2026
Line 141:		Line 141:
	--rm \		--rm \
	-it \		-it \
	-v "$(pwd)":/asteroid:Z \		-v "$(pwd)":/asteroid:z \
	--userns keep-id asteroidos-toolchain \		--userns keep-id asteroidos-toolchain \
	bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"		bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"
Line 165:		Line 165:
	*<code>--rm</code> Cleans up after the command is run by removing temporary container storage		*<code>--rm</code> Cleans up after the command is run by removing temporary container storage
	*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.		*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.
	*<code>-v "$(pwd)":/asteroid:Z</code> Mount the current directory (which is your asteroid git repo clone) into the container. The <code>:Z</code> tells SELinux, if it's running that this container ~~has ''exclusive access''~~ to this mount. If <code>:z</code> is used instead, it tells SELinux, if it's running, to ~~allow multiple containers to share~~ this mount. Either can be used, but the exclusive access flag ~~avoids~~ the need to re-apply security labels to all files which can take significant time when the container starts.		*<code>-v "$(pwd)":/asteroid:z</code> Mount the current directory (which is your asteroid git repo clone) into the container. The <code>:z</code> tells SELinux, if it's running that this container to allow multiple containers to share this mount. If <code>:Z</code> is used instead, it tells SELinux, if it's running, that the container has ''exclusive access'' to this mount. Either can be used, but using the exclusive access flag causes the need to re-apply security labels to all files which can take significant time when the container starts.
	*<code>--userns keep-id</code> Run as the current user inside the container		*<code>--userns keep-id</code> Run as the current user inside the container
	*<code>bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"</code> This is the command to be executed inside of the container with <code>dory</code> being the codename of your watch.		*<code>bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"</code> This is the command to be executed inside of the container with <code>dory</code> being the codename of your watch.

Beroset: /* Building the software */ Add a note about :z versus :Z for volume mount

2026-07-13T12:27:59Z

Building the software: Add a note about :z versus :Z for volume mount

← Older revision		Revision as of 12:27, 13 July 2026
Line 141:		Line 141:
	--rm \		--rm \
	-it \		-it \
	-v "$(pwd)":/asteroid:z \		-v "$(pwd)":/asteroid:Z \
	--userns keep-id asteroidos-toolchain \		--userns keep-id asteroidos-toolchain \
	bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"		bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"
Line 165:		Line 165:
	*<code>--rm</code> Cleans up after the command is run by removing temporary container storage		*<code>--rm</code> Cleans up after the command is run by removing temporary container storage
	*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.		*<code>-it</code> Attaches the terminal to the container so that we can see the output. Otherwise it would run blindly in the background.
	*<code>-v "$(pwd)":/asteroid:z</code> Mount the current directory (which is your asteroid git repo clone) into the container. The <code>:z</code> tells SELinux, if it's running, to allow multiple containers to share this mount.		*<code>-v "$(pwd)":/asteroid:Z</code> Mount the current directory (which is your asteroid git repo clone) into the container. The <code>:Z</code> tells SELinux, if it's running that this container has ''exclusive access'' to this mount. If <code>:z</code> is used instead, it tells SELinux, if it's running, to allow multiple containers to share this mount. Either can be used, but the exclusive access flag avoids the need to re-apply security labels to all files which can take significant time when the container starts.
	*<code>--userns keep-id</code> Run as the current user inside the container		*<code>--userns keep-id</code> Run as the current user inside the container
	*<code>bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"</code> This is the command to be executed inside of the container with <code>dory</code> being the codename of your watch.		*<code>bash -c "source ./prepare-build.sh dory && bitbake asteroid-image"</code> This is the command to be executed inside of the container with <code>dory</code> being the codename of your watch.

Klalofu: /* Downloading */

2026-02-06T09:45:13Z

Downloading

← Older revision		Revision as of 09:45, 6 February 2026
Line 48:		Line 48:
	\| Ubuntu \|\| <code>apt-get install git build-essential chrpath cpio diffstat gawk liblz4-tool python3 shared-mime-info texinfo wget zstd </code>		\| Ubuntu \|\| <code>apt-get install git build-essential chrpath cpio diffstat gawk liblz4-tool python3 shared-mime-info texinfo wget zstd </code>
	\|-		\|-
	\| Fedora \|\| <code>dnf install chrpath diffstat g++ lz4 perl perl-bignum python3-pip rpcgen socat texinfo</code>		\| Fedora \|\| <code>dnf install chrpath diffstat g++ lz4 perl perl-bignum python3-pip rpcgen socat texinfo patch</code>
	\|-		\|-
	\| Arch \|\| <code>pacman -Sy base-devel chrpath cpio diffstat gawk inetutils lz4 python3 rpcsvc-proto shared-mime-info texinfo wget zstd</code>		\| Arch \|\| <code>pacman -Sy base-devel chrpath cpio diffstat gawk inetutils lz4 python3 rpcsvc-proto shared-mime-info texinfo wget zstd</code>

Beroset: Edited to change old `tmp-glibc` to current `tmp` directory under `build`.

2025-10-10T00:33:55Z

Edited to change old `tmp-glibc` to current `tmp` directory under `build`.

← Older revision		Revision as of 00:33, 10 October 2025
Line 173:		Line 173:
	= Installing =		= Installing =

	After a while, whether you build with or without containers, the generated image should be available in <code>build/tmp~~-glibc~~/deploy/images/dory/</code> (for <code>dory</code> -- for other watches, the image files are in the corresponding code word directory.)		After a while, whether you build with or without containers, the generated image should be available in <code>build/tmp/deploy/images/dory/</code> (for <code>dory</code> -- for other watches, the image files are in the corresponding code word directory.)

	Install AsteroidOS using your usual device's instructions, which you can find linked from the [https://asteroidos.org/watches/ Watches page].		Install AsteroidOS using your usual device's instructions, which you can find linked from the [https://asteroidos.org/watches/ Watches page].

Beroset: /* Build with containers */ Updated Fedora version that was tested and minor formatting fixes.

2025-02-19T16:02:51Z

Build with containers: Updated Fedora version that was tested and minor formatting fixes.

← Older revision		Revision as of 16:02, 19 February 2025
Line 87:		Line 87:
	= Build with containers =		= Build with containers =

	These instructions have been tested on Ubuntu 19.04 (with Docker) and Fedora 34 (with podman), but should also be applicable to Debian Sid (at least at the time of writing). For other distributions the dependencies may have different names and you may have to install additional ones.		These instructions have been tested on Ubuntu 19.04 (with Docker) and Fedora 41 (with podman), but should also be applicable to Debian Sid (at least at the time of writing). For other distributions the dependencies may have different names and you may have to install additional ones.

	From a user's point of view, Docker and podman are quite similar and accept almost all of the exact same commands, but there are some difference. The most significant differences for building Asteroid are that podman does not use a daemon and can be run "rootless" (that is, as a non-root user). This makes some things a bit easier, but either can be used.		From a user's point of view, Docker and podman are quite similar and accept almost all of the exact same commands, but there are some difference. The most significant differences for building Asteroid are that podman does not use a daemon and can be run "rootless" (that is, as a non-root user). This makes some things a bit easier, but either can be used.
Line 119:		Line 119:

	In this example, we will build AsteroidOS for <code>dory</code>(the LG G Watch). To build for a different watch than the LG G Watch, use its corresponding codename instead of <code>dory</code> when executing the <code>docker run ...</code> command. You can find the codenames for the supported watches on the [https://asteroidos.org/watches/ Watches page].		In this example, we will build AsteroidOS for <code>dory</code>(the LG G Watch). To build for a different watch than the LG G Watch, use its corresponding codename instead of <code>dory</code> when executing the <code>docker run ...</code> command. You can find the codenames for the supported watches on the [https://asteroidos.org/watches/ Watches page].

MagneFire at 20:50, 12 December 2024

2024-12-12T20:50:40Z

← Older revision		Revision as of 20:50, 12 December 2024
Line 1:		Line 1:
	~~{{Infobox~~
	~~\|title = An amazing Infobox~~
	~~\|header1 = It works!~~
	~~\|label2 = Configured by~~
	~~\|data2 = trog~~
	~~\|label3 = Web~~
	~~\|data3 = [https://trog.qgl.org trog.qgl.org]~~
	}}

	[[Category:Developers]]		[[Category:Developers]]
	If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:		If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:

MagneFire at 20:49, 12 December 2024

2024-12-12T20:49:38Z

← Older revision		Revision as of 20:49, 12 December 2024
Line 1:		Line 1:
			{{Infobox
			\|title = An amazing Infobox
			\|header1 = It works!
			\|label2 = Configured by
			\|data2 = trog
			\|label3 = Web
			\|data3 = [https://trog.qgl.org trog.qgl.org]
			}}

	[[Category:Developers]]		[[Category:Developers]]
	If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:		If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:

MagneFire at 20:49, 12 December 2024

2024-12-12T20:49:25Z

← Older revision		Revision as of 20:49, 12 December 2024
Line 1:		Line 1:
	~~{{Infobox~~
	~~\|title = An amazing Infobox~~
	~~\|header1 = It works!~~
	~~\|label2 = Configured by~~
	~~\|data2 = trog~~
	~~\|label3 = Web~~
	~~\|data3 = [https://trog.qgl.org trog.qgl.org]~~
	}}

	[[Category:Developers]]		[[Category:Developers]]
	If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:		If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:

MagneFire at 22:06, 11 December 2024

2024-12-11T22:06:53Z

← Older revision		Revision as of 22:06, 11 December 2024
Line 1:		Line 1:
			{{Infobox
			\|title = An amazing Infobox
			\|header1 = It works!
			\|label2 = Configured by
			\|data2 = trog
			\|label3 = Web
			\|data3 = [https://trog.qgl.org trog.qgl.org]
			}}

	[[Category:Developers]]		[[Category:Developers]]
	If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]:		If you decide to compile AsteroidOS from source be aware that it’s a simple process but requires a lot of disk space (potentially more than 100GB) and the first build might take you a lot of time (hours). Report any problem to the [https://github.com/AsteroidOS/asteroid/issues issue tracker]: