oxidecomputer / oxidecomputer/hubris
Allow kernel to be built without app table
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
Kernel depends on the contents of the app table at runtime but only the location of the table at build time. Since the app table includes the entry point of each task, it necessarily depends on having built all of the tasks. If we use tricks similar to how peer tasks are resolved, the compilation of the kernel will no longer be dependent on the build output of the tasks.
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 tracing how the kernel consumes the app table at runtime and how its location is supplied at build time. Compare that path with the existing peer-task resolution approach, then define how kernel compilation can avoid task build outputs while preserving app-table entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100