Personal development fork of Iglunix-autobuild.
Go to file
aheirman fe6963e1bd Fixes, many fixes 2021-02-12 17:20:43 +01:00
bugs Init lazy-autobuild 2021-02-04 18:00:27 +01:00
dont_use_here Fixes, many fixes 2021-02-12 17:20:43 +01:00
.gitignore Fixes, many fixes 2021-02-12 17:20:43 +01:00
Dockerfile_update Init lazy-autobuild 2021-02-04 18:00:27 +01:00
LICENSE Create LICENSE 2021-02-04 18:09:29 +01:00 Typo in README 2021-02-11 12:36:40 +01:00
chroot_fetch Rename to iglunix from lazybox 2021-02-06 13:52:14 +01:00
chroot_iglunix Fixes, many fixes 2021-02-12 17:20:43 +01:00
chroot_prepare_iglunix Fixes, many fixes 2021-02-12 17:20:43 +01:00
docker_init_clean Rename to iglunix from lazybox 2021-02-06 13:52:14 +01:00
docker_port_forward Init lazy-autobuild 2021-02-04 18:00:27 +01:00
docker_remove_all_containers Init lazy-autobuild 2021-02-04 18:00:27 +01:00
docker_rm_farm Init lazy-autobuild 2021-02-04 18:00:27 +01:00
docker_start_farm Rename to iglunix from lazybox 2021-02-06 13:52:14 +01:00

Welcome, this is iglunix-autobuild. Thu GNU General Public License v3 licesed (mostly) automatic build system for Iglunix. Iglunix for the uninitiated is a inux distribution designed to not use GNU, sadly this is quit hard. GNU make is still available inside this environment.


Fase 1: Docker

This will create an llvm/musl toolchain. I've heard that you guys don't like waiting for code to be compiled. A docker swarm to the recue, completely over engineered.

Make your main pc/laptop the manager of the swarm using: docker swarm init --advertise-addr [The IP-address of your device you want to use local/global]

It will return a command that allows your other pcs to join, use it.

On the main node run: docker network create -d overlay my_docker_net

The problem is that we can't chain commands when starting a docker service create, so we'll have to modify the base abyssos/abyss:dev docker container. We'll need to dowload packages for the installation, we'll add these to the our modified package. This method might also reduce internet usage.

To initialize run docker_init_clean, this will create iglunix_abyss.tar, this will have to be manually moved to all docker nodes and then loaded using: docker load -i iglunix_abyss.tar

To start the distributed compiler docker_start_farm can be used. Prior to execution modify docker_start_farm to suit the number of jobs you need to run.

Run docker ps -a to find the container id of your work nodes and execute a shell on a node of your chosing using. This can be done as follows: docker exec -it [container id] /bin/sh

Modify DISTCC_HOSTS in compile in one container to point to all the docker distcc volunteers. Afterwards run compile. When your compiles are finished, docker_rm_farm can be used to remove the compile farm. It could be useful to leave the compile farm around for the compilation indide the chroot. This is not yet supported.

Fase 2: Chroot

This part is significantly less over engineerd (luckily). There are 4 commands the user should be aware of, they are writen in chronological order.

  • chroot_prepare_iglunix

    This creates the chroot and cleans the most important locations (/lib, /bin, /sbin, /usr, /iglunix, /etc).

  • chroot_fetch

    This command will fetch the sources needed to get curl working inside the chroot. And some files for to be used inside the chroot environment. This command will automatically be execute by chroot_prepare_iglunix. It is NOT NEEDED to be manually exected. But it can be.

  • chroot_iglunix

    This will chroot into the Iglunix environment.

  • inside_chroot

    This is the script that has to be executed inside the chroot to compile all the required apckages in the correct order. This will also generate a

Fase 3: Boot

Use virt-manager or qemu to boot the iglunix.img.

Or execute QEMU directly with the following

qemu-system-x86_64 path/to/disk -enable-kvm -m 4096