rust-lang / rust-lang/reference
Doucment how raw-dylib finds DLLs at runtime
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 607
- PR merge metrics
- PR metrics pending
Description
Was trying to use the 'raw-dylib' feature and found that things didn't quite work as I expected. Perhaps the following clarifications could be added to the docs?
- When using 'raw-dylib', where does Rust look for the DLLs at runtime?
- Can that lookup behavior be changed? For example, if I have the DLLs in a subdirectory instead of directly next to the executable, can I tell this to the compiler somehow?
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
Read the linked section in src/items/external-blocks.md, especially the raw-dylib documentation around lines 230-237. Verify where Rust looks for DLLs at runtime and whether that lookup can be changed, then update the section to answer both questions. Done means the Reference clearly describes the lookup behavior and any supported configuration limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100