kernelci / kernelci/tuxmake

Including external ini files for targets and arches

Open
#132 3 comments 0 reactions 0 assignees View on GitHub
gitlab issue
Dominant language
Python
Stars
6
Forks
6
Avg merge
6h 1m
Merged PRs (30d)
3

Description

***In GitLab by @a3f on Apr 7, 2021, 11:29 GMT+1:***

I tested use of tuxmake with [barebox](barebox.org/) and found that including external ini files would
be very useful:

- barebox doesn't install to `arch/$ARCH/boot/`, but to `images/`. A custom external `target.ini` could account for this.
- Compiler toolchain prefixes. I use [OSELAS.Toolchain](https://www.pengutronix.de/en/software/toolchain.html) which e.g. uses a `CROSS_COMPILE=arm-v7a-linux-gnueabihf-` prefix. Including an external `arch.ini` would allow me to customize this.

Thoughts on adding this or is this perhaps already possible?

*Migrated from GitLab: https://gitlab.com/Linaro/tuxmake/-/issues/132*

Contributor guide

Open the contributing guide

Research direction

Start by examining how target.ini and arch.ini settings are handled, including the target output path and CROSS_COMPILE values described in the issue. Define how external files would be supplied and verify that a custom target.ini can select images/ and a custom arch.ini can provide the OSELAS.Toolchain prefix.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.