Speedup builds by generating a `config.site`
Open
Nobody has claimed this yet.
enhancement / improvement
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
Since a build runs `configure` so many times and the answers should always be the same with the cross compiler and static library setup, the values could be cached into a `config.site` file so that the tests don't need to be done over and over again.
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 locating the build scripts and the repeated configure invocations, then review how the cross compiler and static library setup is passed to configure. Determine where a config.site file could be generated and supplied consistently, and verify that builds and tests still complete without repeating unchanged checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100