ninja-build/ninja

Grammar for build specification

Open

#510 opened on Feb 25, 2013

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

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

Tech stack
cpp
Domain
documentationbuild system
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
Formal grammar basicsNinja build file format
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Study the existing documentation of the build file format at https://github.com/martine/ninja/blob/e758e8d0e014c1442ab5973541a3a1cc59dc97cb/doc/manual.asciidoc#writing your own ninja files. Define a formal grammar (e.g., EBNF) covering all syntax elements. Ensure consistency with the current implementation. Consider contributing the grammar file to the repository with appropriate format.