ninja-build/ninja

Grammar for build specification

Open

#510 opened on Feb 25, 2013

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (1,544 forks)batch import
help wanted

Repository metrics

Stars
 (10,194 stars)
PR merge metrics
 (Avg merge 39d 3h) (10 merged PRs in 30d)

Description

The build file format is described to some degree. I would appreciate if a corresponding grammar file will be provided so that documentation and data exchange can be improved in consistent ways.

Contributor guide

Research direction
Study the current build file format description in the manual (https://github.com/ninja build/ninja/blob/e758e8d0e014c1442ab5973541a3a1cc59dc97cb/doc/manual.asciidoc) and create a formal grammar using a standard notation such as BNF or EBNF.
Tech stack
cpp
Domain
build systemdocumentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50