manually specify existing proj installation via env variables
- Dominant language
- Rust
- Stars
- 186
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
For most people, pkg-config is a great option. But for when it's not, I think conventions exist for manually specifying environment variables.
Something like:
```
PROJ_SYS_PROJ_INCLUDE_DIR=/path/to/my/proj/include PROJ_SYS_LIBRARY_PATH=/path/to/my/proj/lib cargo build
```
We don't currently support this, but we should.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the build entry point that currently relies on pkg-config for PROJ discovery. Test a build against an existing PROJ installation using PROJ_SYS_PROJ_INCLUDE_DIR and PROJ_SYS_LIBRARY_PATH, and consider the work done when those variables select the requested headers and library successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100