premake / premake/premake-core
buildcommands() don't support multiple commands
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 654
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
Description
The current method of specifying custom build commands (the buildcommands, buildinputs, and buildoutputs APIs) don't allow multiple rule sets, with their own inputs and outputs to be specified. The values all get lumped together during project baking and the intended associations get lost.
Probably need to bring back the previous buildrule { ... } syntax.
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 the buildcommands, buildinputs, and buildoutputs APIs through project baking, focusing on where their values are combined. Done means supporting multiple build rule sets while preserving each rule's inputs and outputs, potentially using the earlier buildrule syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100