microsoft / microsoft/mu_devops
Appropriately Set Linker Subsystem Per Driver Type in Pure Rust Modules
Open
Nobody has claimed this yet.
state:backlog
- Dominant language
- Dockerfile
- Stars
- 43
- Forks
- 36
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 10
Description
Currently we set /subsystem=efi_boot_services_driver for all pure Rust binaries, which works for development, but as we get runtime service and applications, we need to appropriately set the subsystem type. @makubacki for reference.
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Start by tracing where /subsystem=efi_boot_services_driver is assigned for pure Rust binaries, then identify how driver types are represented for runtime services and applications; done means each type receives its appropriate linker subsystem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100