TODO: use local headers if available (was: Why do headers need to be downloaded?)
Open
Nobody has claimed this yet.
Feature Request
question
- Dominant language
- Python
- Stars
- 10.7k
- Forks
- 1.9k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 5
Description
This is an issue that has been causing me a lot of trouble lately, and it causes issues like #1230 #1231 #1232 #1234
Is there an unavoidable reason for grabbing headers from the (not 100% reliable) internet to compile a module? Isn't this just something that could be included in the node package?
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 reviewing this issue and related reports #1230, #1231, #1232, and #1234 to understand the current header-download behavior and its failures. Trace the node-gyp build flow to determine where local headers could be preferred; done means compilation uses available local headers without requiring an unreliable internet download.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100