Too many configuration options
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
There are a huge number of configuration options that board files can set, some of which should be user specified. We need a way to document them, to track them and to select them, both at firmware image build time (for the defaults) and possibly at runtime from the recovery shell (using the CBFS or flashtool based writer).
Difficulty: hard
Reward: three stars
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the configuration options set by board files and identifying how defaults are selected during firmware image builds. Then examine the recovery shell and the CBFS or flashtool-based writer paths; done should include a defined way to document, track, select, and apply these options at build time and possibly at runtime.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, cli, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100