Separate ANGLE additions into separate crate that depends on unmodified ANGLE build
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 48
- Forks
- 30
- Avg merge
- 16h 45m
- Merged PRs (30d)
- 5
Description
The presence of a Rust crate that calls C functions that are compiled into in the ANGLE static library makes it hard to deal with the DLL mess that exists on Windows. If the additions to the ANGLE API could live in a separate library and crate that depends on an angle-sys crate that is just the unmodified ANGLE sources, that would be easier to reason about.
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
The issue names no files or tests. Start by tracing how the current Rust crate builds ANGLE and calls its C functions, then identify where the ANGLE sources and additions are combined. Done means the additions are in a separate library and crate, while the angle-sys crate builds unmodified ANGLE sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100