History log of /netbsd-current/usr.bin/make/unit-tests/directive.mk
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 1.9 19-Nov-2023 rillig

tests/make: replace 'variable expressions' with 'expressions'


# 1.8 19-Aug-2023 rillig

make: show realistic invalid line in error message

Previously, the error message 'Invalid line' showed only the expanded
line, which might or might not show the actual problem. To be more
helpful, add the unexpanded line to the error message in case they
differ.

Remove the special handling of invalid lines that result from merge
conflicts. RCS is not commonly used anymore, and mentioning CVS was too
specific. By echoing the whole line, the patterns '<<<<<<' and '>>>>>>'
are clear enough to hint at the problem.


# 1.7 19-Aug-2023 rillig

make: add more details to error message about invalid lines


Revision tags: netbsd-10-0-RC1 netbsd-10-base
# 1.6 23-Jan-2022 rillig

tests/make: extend test suite, move old tests to 2020 scheme

The tests from envfirst.mk are now in opt-env.mk.
The tests from modword.mk are now in varmod-select-words.mk.


# 1.5 13-Dec-2021 rillig

tests/make: extend tests for parsing makefiles


Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
# 1.4 15-Nov-2020 rillig

make(1): add tests for edge cases when parsing directives


# 1.3 03-Nov-2020 rillig

make(1): move tests from directives.mk to separate tests


# 1.2 16-Aug-2020 rillig

make(1): describe the purpose of each newly added unit test dummy


# 1.1 16-Aug-2020 rillig

make(1): add dummies for fine-grained tests, one per single feature

The test names have been derived from the current manual page.

All these tests are dummies right now, and the code from the existing
tests will be moved into the new tests step by step.

This is done to prevent modmisc, escape, varmod-edge and varmisc from
growing without any bounds, and to reduce the side-effects of one test
to the others.


# 1.8 19-Aug-2023 rillig

make: show realistic invalid line in error message

Previously, the error message 'Invalid line' showed only the expanded
line, which might or might not show the actual problem. To be more
helpful, add the unexpanded line to the error message in case they
differ.

Remove the special handling of invalid lines that result from merge
conflicts. RCS is not commonly used anymore, and mentioning CVS was too
specific. By echoing the whole line, the patterns '<<<<<<' and '>>>>>>'
are clear enough to hint at the problem.


# 1.7 19-Aug-2023 rillig

make: add more details to error message about invalid lines


Revision tags: netbsd-10-base
# 1.6 23-Jan-2022 rillig

tests/make: extend test suite, move old tests to 2020 scheme

The tests from envfirst.mk are now in opt-env.mk.
The tests from modword.mk are now in varmod-select-words.mk.


# 1.5 13-Dec-2021 rillig

tests/make: extend tests for parsing makefiles


Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
# 1.4 15-Nov-2020 rillig

make(1): add tests for edge cases when parsing directives


# 1.3 03-Nov-2020 rillig

make(1): move tests from directives.mk to separate tests


# 1.2 16-Aug-2020 rillig

make(1): describe the purpose of each newly added unit test dummy


# 1.1 16-Aug-2020 rillig

make(1): add dummies for fine-grained tests, one per single feature

The test names have been derived from the current manual page.

All these tests are dummies right now, and the code from the existing
tests will be moved into the new tests step by step.

This is done to prevent modmisc, escape, varmod-edge and varmisc from
growing without any bounds, and to reduce the side-effects of one test
to the others.


# 1.6 23-Jan-2022 rillig

tests/make: extend test suite, move old tests to 2020 scheme

The tests from envfirst.mk are now in opt-env.mk.
The tests from modword.mk are now in varmod-select-words.mk.


# 1.5 13-Dec-2021 rillig

tests/make: extend tests for parsing makefiles


Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
# 1.4 15-Nov-2020 rillig

make(1): add tests for edge cases when parsing directives


# 1.3 03-Nov-2020 rillig

make(1): move tests from directives.mk to separate tests


# 1.2 16-Aug-2020 rillig

make(1): describe the purpose of each newly added unit test dummy


# 1.1 16-Aug-2020 rillig

make(1): add dummies for fine-grained tests, one per single feature

The test names have been derived from the current manual page.

All these tests are dummies right now, and the code from the existing
tests will be moved into the new tests step by step.

This is done to prevent modmisc, escape, varmod-edge and varmisc from
growing without any bounds, and to reduce the side-effects of one test
to the others.


# 1.5 13-Dec-2021 rillig

tests/make: extend tests for parsing makefiles


Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
# 1.4 15-Nov-2020 rillig

make(1): add tests for edge cases when parsing directives


# 1.3 03-Nov-2020 rillig

make(1): move tests from directives.mk to separate tests


# 1.2 16-Aug-2020 rillig

make(1): describe the purpose of each newly added unit test dummy


# 1.1 16-Aug-2020 rillig

make(1): add dummies for fine-grained tests, one per single feature

The test names have been derived from the current manual page.

All these tests are dummies right now, and the code from the existing
tests will be moved into the new tests step by step.

This is done to prevent modmisc, escape, varmod-edge and varmisc from
growing without any bounds, and to reduce the side-effects of one test
to the others.


# 1.4 15-Nov-2020 rillig

make(1): add tests for edge cases when parsing directives


# 1.3 03-Nov-2020 rillig

make(1): move tests from directives.mk to separate tests


# 1.2 16-Aug-2020 rillig

make(1): describe the purpose of each newly added unit test dummy


# 1.1 16-Aug-2020 rillig

make(1): add dummies for fine-grained tests, one per single feature

The test names have been derived from the current manual page.

All these tests are dummies right now, and the code from the existing
tests will be moved into the new tests step by step.

This is done to prevent modmisc, escape, varmod-edge and varmisc from
growing without any bounds, and to reduce the side-effects of one test
to the others.