meson

13892 Commits

76 Branches

171 Tags

74 MiB

Tag: Branch: Tree: 84e437179d

Commit Graph

Author	SHA1	Message	Date
Eli Schwartz	5a7b8d86d0	use a more informative error message for invoking meson in a subdir Explicitly mention that the project definition is invalid, and clarify that project is `project()` -- a function. Also try to walk the directory tree upward, and if there are parent meson.build files, just say this isn't the project root, and "maybe you meant to run meson there instead?" This won't catch calls to subdir('foo/bar') but we can't be perfect, only better than before and catch the majority of such cases, and hopefully it's a lot more clear if meson protests that the project is "invalid, there is no project() function", where the user should look for a potential solution. Fixes #3426	3 years ago
Dylan Baker	29ef4478df	compilers/d: Add b_ndebug support D lang compilers have an option -release (or similar) which turns off asserts, contracts, and other runtime type checking. This patch wires that up to the b_ndebug flag. Fixes #7082	5 years ago
Jon Turney	3cff11a75b	Add expected stdout for failing-meson and warning-meson tests Initially produced using: for d in "test cases/failing/"* ; do rm -r _build ; ./meson.py setup "$d" _build \| grep ERROR >"$d"/expected_stdout.txt; done then converted to json with jq using: jq --raw-input --slurp 'split("\n") \| {stdout: map({line: select(. != "")})}' expected_stdout.txt >test.json or merged with existing json using: jq --slurp '.[0] + .[1]' test.json expected.json >test.json.new v2: Add some comments to explain the match when it isn't totally obvious v3: Add or adjust existing re: in expected output to handle '/' or '\' path separators appearing in message, not location. v4: Put expected stdout in test.json, rather than a separate expected_stdout.txt file Park comments in an unused 'comments' key, as JSON doesn't have a syntax for comments	5 years ago

Author

SHA1

Message

Date

Eli Schwartz

5a7b8d86d0

use a more informative error message for invoking meson in a subdir

Explicitly mention that the project definition is invalid, and clarify
that project is `project()` -- a function.

Also try to walk the directory tree upward, and if there are parent
meson.build files, just say this isn't the project root, and "maybe you
meant to run meson there instead?"

This won't catch calls to subdir('foo/bar') but we can't be perfect,
only better than before and catch the *majority* of such cases, and
hopefully it's a lot more clear if meson protests that the project is
"invalid, there is no project() function", where the user should look
for a potential solution.

Fixes #3426

3 years ago

Dylan Baker

29ef4478df

compilers/d: Add b_ndebug support

D lang compilers have an option -release (or similar) which turns off
asserts, contracts, and other runtime type checking. This patch wires
that up to the b_ndebug flag.

Fixes #7082

5 years ago

Jon Turney

3cff11a75b

Add expected stdout for failing-meson and warning-meson tests

Initially produced using:

  for d in "test cases/failing/"* ; do rm -r _build ; ./meson.py setup "$d" _build | grep ERROR >"$d"/expected_stdout.txt; done

then converted to json with jq using:

  jq --raw-input --slurp 'split("\n") | {stdout: map({line: select(. != "")})}' expected_stdout.txt >test.json

or merged with existing json using:

  jq --slurp '.[0] + .[1]' test.json expected.json >test.json.new

v2:
Add some comments to explain the match when it isn't totally obvious

v3:
Add or adjust existing re: in expected output to handle '/' or '\' path
separators appearing in message, not location.

v4:
Put expected stdout in test.json, rather than a separate expected_stdout.txt file
Park comments in an unused 'comments' key, as JSON doesn't have a syntax for comments

5 years ago

2 Commits (84e437179da05db10aa2457322c54f4ec8be61f1)