Embeddable setup with QEmacs and TCC

Slava Barinov e63f577fa4 doc: Add README il y a 3 mois
busybox @ 371fe9f71d e075faaa61 Initial commit il y a 7 mois
musl @ 8fd5d03187 26275ac0ea chore: Bump versions il y a 3 mois
qemacs @ 990b1fbeeb e075faaa61 Initial commit il y a 7 mois
tcc @ f52b480f89 26275ac0ea chore: Bump versions il y a 3 mois
.gitmodules c97d51cd40 chore: Remove unused modules il y a 3 mois
README.md e63f577fa4 doc: Add README il y a 3 mois
bbconfig e075faaa61 Initial commit il y a 7 mois
build.sh e63f577fa4 doc: Add README il y a 3 mois

README.md

Minimal C Development Environment

Why?

I don't have any particular reason not to have a working C compiler everywhere you go.

Components

The resulting directory is ~8.5 MiB.

Usage

Can be used in limited environments when you need some quick and dirty in-place development. I keep it inside my initramfs just in case.

TCC usage in the environment

The script only builds static version of musl so the only working binaries will be static unless you provide your own Libc.

Adding as initramfs

My /usr/src/linux/.config file contains the line

CONFIG_INITRAMFS_SOURCE="/usr/src/initramfs/base /usr/src/initramfs/list"

In this case the base is the resulting directory of the build, and the list file contains some additional tools from my host system I need inside initramfs (like lvm).