3 # The release package to use for the tests contained within the directory
5 # This applies to components which rely on ^/projects/release-pkg support
6 # (see UPDATING XXXXXXXXX / svn revision r298107).
9 # Directory into which the Kyuafile provided by this directory will be
12 # This is always a subdirectory of ${TESTSBASE}/. The remainder of the
13 # path has to match the relative path within the source tree in which
14 # these files are found modulo the tests/ component at the end.
16 # For example: if this Makefile were in src/bin/cp/tests/, its TESTSDIR
17 # would point at ${TESTSBASE}/bin/cp/.
18 TESTSDIR= ${TESTSBASE}/share/examples/tests/tap
20 # List of test programs to build. Note that we can build more than one
21 # test from a single directory, and this is expected.
22 TAP_TESTS_C= printf_test
25 # Tell bsd.test.mk that we are providing a hand-crafted Kyuafile in this
26 # directory. We do so because the file in this directory exists for
27 # documentation purposes.
29 # In general, however, you should NOT define KYUAFILE at all to allow
30 # bsd.test.mk auto-generate one for you based on the PLAIN_TESTS_*
31 # definitions from above.
34 # Install file1 and file2 as files via bsd.prog.mk. Please note the intentional
35 # ${PACKAGE} namespace of files.
37 # The basic semantics of this are the same as FILES in bsd.prog.mk, e.g. the
38 # installation of the files can be manipulated via ${PACKAGE}FILESDIR,
39 # ${PACKAGE}FILESMODE, etc.
41 # Please see comment above about ${PACKAGE}. Feel free to omit the ${PACKAGE}
42 # namespace if release package support isn't needed.
43 ${PACKAGE}FILES+= file1
47 @echo "File 1" > ${.TARGET}
49 .include <bsd.test.mk>