microsoft / microsoft/rust-symcrypt
Investigate removing .lib for linking
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 72
- Forks
- 15
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 11
Description
You can set bindgen to only use the .dll instead of requiring both the .lib and .dll
via:
let bindings = bindgen::Builder::default() .header("inc/wrapper.h") .clang_arg("-v") .dynamic_library_name("SymCryptLib")
This will cause errors with unresolved errors for pub static variables exported from SymCrypt. Investigate if there is a way to circumvent this so that we can only rely on the .dll
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 with the bindgen configuration using inc/wrapper.h and dynamic_library_name("SymCryptLib"). Investigate why DLL-only linking leaves exported pub static variables unresolved and determine whether SymCrypt can be linked without the .lib; done means documenting a viable approach or confirming that both files remain required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, cryptography
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100