GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - bootlin/toolchains-builder

BranchesTags
Open more actions menu

Latest commit

 

History

366 Commits
366 Commits

Folders and files

NameName
Last commit message
Last commit date
.gitlab-ci
.gitlab-ci
 
 
configs
configs
 
 
docker-toolchain-build
docker-toolchain-build
 
 
docker-toolchain-test-upload
docker-toolchain-test-upload
 
 
overlay/etc/init.d
overlay/etc/init.d
 
 
.gitignore
.gitignore
 
 
.gitlab-ci.yml
.gitlab-ci.yml
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
build-toolchain.sh
build-toolchain.sh
 
 
common.sh
common.sh
 
 
readme_base.txt
readme_base.txt
 
 
test-toolchain.sh
test-toolchain.sh
 
 
update_gitlab-ci.sh
update_gitlab-ci.sh
 
 
upload-toolchain.sh
upload-toolchain.sh
 
 

Repository files navigation

Toolchains builder

The goal of this project is to automate the build of a wide range of toolchains using Buildroot.

Since making a per-toolchain configuration is not viable, some scripts have been made to allow a more flexible configuration. You can find all the config fragments in the configs folder.

update_gitlab-ci.sh

This script simply makes the different valid fragments from all the possible combinations of architecture, libc, and version, found in the configs folder.

It autocommits the generated fragments in a builds branch. The fragments are in the frags folder, and a .gitlab-ci.yaml file is created to trigger the builds if pushed to a well configured Gitlab hosted project.

build.sh

This is the main script handling the build, the test, and the packaging of the toolchain. If you typically want to recreate the whole build process, just run that as root (for chroot). It is wise to do that in some sort of container, and not on your bare system.

build_chroot.sh

This is the script called in the chroot environment, that simply builds the toolchain without testing it or packaging anything. If you simply want to reproduce the build for debugging, it's probably this script your looking for.

All these scripts can be called without arguments to get their usage information.

About

toolchains.bootlin.com

Resources

Readme
GPL-2.0 license
Activity
Custom properties

Stars

124 stars

Watchers

11 watching

Forks

31 forks
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.