How can debuginfo be detected from a build.rs ?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
Does cargo define an environment variable with its value from the profile ? (I couldn't find any).
If so, is this value updated with the RUSTFLAGS/ ./cargo/config ?
The most portable way I can think of, of doing this correctly, is probably to just invoke cargo metadata from the build.rs, and just scan it for debuginfo=PAT and parse that.
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 tracing how Cargo exposes profile information to build.rs and how RUSTFLAGS, cargo/config, and cargo metadata represent debuginfo. Determine whether an existing portable value or supported mechanism exists; done should be a decided, documented approach or a clearly scoped change, since the issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100