| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
When we explicitly unlink the file we should return LOAD_NOT_FOUND instead of LOAD_SUCCESS
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not use os.chdir() to change the current directory inside
the run() function, as doing this prevents the temporary directory
from being removed.
Moreover, this breaks pytest invocations when adding new regression
test scripts in this directory (as done in other forks).
+ Use dict.pop() to undefine environment variables in `default_env`
dictionary.
|
| |
|
|
|
|
|
|
|
|
| |
This fixes #1966 by removing the variable name from the
lookups stack once the recursive lookup call has been performed.
Without this, any previously expanded variable could no longer
be referenced in the command, as Ninja would (incorrectly)
complain about a cyclical dependency.
|
|
|
|
|
|
|
|
|
|
|
| |
We default `ninja-indent-offset` to `2` because Meson and CMake use `1`
and `2` values accordingly, but `1` seems like too little, so use `2`.
The correctness was tested in particular on two `build.ninja` files,
one generated by Meson (1790 lines), and another by CMake (7777
lines). After setting `ninja-indent-offset` to the expected by the
file value and re-indenting whole file the buffer was left unchanged,
i.e. the calculated offset matched the ones already used.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code previously did not take into account that between the name
and assignment may be any number of space including no space at all.
It was also incorrectly highlighting in a code like
foo = bar = buzz
the `bar` as a variable, even though the `bar = buzz` is just a text
that gets assigned to `foo`, i.e. `bar` is not a variable. Fix that.
|
|
|
|
|
| |
We already did this in some, this converts the rest.
Also chmod +x on write_fake_manifests.py while here.
|
| |
|
|
|
|
|
|
|
| |
- add `ninja` prefix to functions
- improve completion of `-d` and `-t`
- stop completion if `-h`, `--help`, or `--version` is supplied
- add missing `--verbose` options
|
|
|
|
|
|
|
|
|
| |
This sorts the output of `ninja -t inputs` to make it
deterministic and remove duplicates, and adds a regression
test in output_test.py
+ Ensure all inputs are listed, not only explicit ones.
+ Document the `inputs` tool in doc/manual.asciidoc.
|
|
|
| |
https://portingguide.readthedocs.io
|
| |
|
|
|
|
|
|
| |
See comment in #1899. Also adds two tests to output_test.py which check
this behaviour by relying on Python's suprocess.check_output not piping
stderr.
|
|
|
|
| |
This just tests that the flag works.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The README file was renamed to README.md in commit
a37da20ae74c81703b1c811182fc154d95ed46fe.
|
| |
|
| |
|
|
|
|
|
| |
the previous assert would fail because on a 1-core VM, the 3 outputs
were produced sequentially from top to bottom
|
| |
|
|
|
| |
The usage of the parameter was removed a long time ago and was never cleaned up. The argument is not provided in the test.
|
|
|
| |
Also make test script works for OSX script command.
|
|
|
|
|
| |
Don't strip colors when CLICOLOR_FORCE is set to a non-zero value. This
environment variable is also used by CMake's Make back-end.
|
| |
|
| |
|
|
|
|
| |
First test checks for #1214.
|
|\
| |
| | |
Fix wrong description of script installation
|
| |
| |
| | |
The described way of installation makes zsh fail with `_arguments:comparguments:325: can only be called from completion function`. Per [zsh documentation](https://github.com/zsh-users/zsh-completions/blob/master/zsh-completions-howto.org#telling-zsh-which-function-to-use-for-completing-a-command) the correct way is to use `$fpath`.
|
|/ |
|
| |
|
|\
| |
| | |
Improve vim syntax definition
|
| |
| |
| |
| |
| | |
Only highlights comments where the ninja lexer would treat them as such.
Also correctly scopes the rule- and pool-specific variables highlighting.
|
|/
|
|
|
| |
ninja_syntax.py now supports a pool being specified for individual
builds, as well as rules.
|
| |
|
|
|
|
| |
This is used by manifest_parser_perftest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add an option to write_fake_manifest.py to generate sources expected by the
manifest. Also slightly adapt command lines to the called commands. Together
these changes mean that generated manifest can actually be executed
successfully on Linux and OSX. Also add command line options to to change the
number of targets being generated and the seed for the random number generator.
Example usage:
# create build directory in fake/build, sources in fake/src
$ python misc/write_fake_manifest.py -s ../src fake/build
# execute build in fake/build
$ ninja -C fake/build
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Bash completion script uses "-t targets all" to list the target which
is faster than "-t targets" and reports intermediary targets
(see the manual entry for the 'targets' tool).
See commit fc135c45.
|
|\
| |
| | |
Fix wrapping file paths in Writer.comment
|
| |
| |
| |
| |
| |
| | |
As pointed out by nico, we should unconditionally disable breaking of
long words in comments. It is unlikely long words that are in comments
should be split (like pathnames).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Long file names, especially with hyphens will get incorrectly wrapped by
the comment method. Pass has_path=True to prevent this type of wrapping.
This is mainly so that longer path names can show up in comments on
their on line without breaking them up.
|
|\ \
| | |
| | | |
Speed-up bash target auto-complete.
|