microsoft / microsoft/rust-symcrypt
Document work flow for developing on static linking
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 15
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 11
Description
Note that jitterentropy needs to be inited
Not that symcrypt needs to be inited
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 locating the repository's existing development documentation and static-linking workflow. Verify where jitterentropy and SymCrypt initialization are described or handled, then document the required initialization steps so a developer can follow the static-linking workflow without missing either dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100