summaryrefslogtreecommitdiff
path: root/m4
diff options
context:
space:
mode:
authorG. Branden Robinson <g.branden.robinson@gmail.com>2023-03-01 06:06:47 -0600
committerG. Branden Robinson <g.branden.robinson@gmail.com>2023-03-02 04:19:43 -0600
commit1ec02e805e2448bb17a27e3d9398cc83fd272743 (patch)
tree7996c15be1bf37890389f0827f9ae6bc761ac210 /m4
parent5a420e557b61146341c025f45998abc971fe346d (diff)
downloadgroff-git-1ec02e805e2448bb17a27e3d9398cc83fd272743.tar.gz
[mom]: Always generate test script.
[mom]: Generate test script even if we'll skip it. * contrib/mom/examples/test-mom.sh.in: Check availability of required pdfinfo(1) and pdfimages(1) commands at test time; skip if they aren't present. * contrib/mom/mom.am [!HAVE_PDFTOOLS]: Generate the test script even if these tools aren't available. This approach also has the slight advantage that if you build groff, then install these tools after building (or even testing), you can simply run the tests again with "make check" without having to "make distclean" and start all over. As a developer, I find it confusing when the (total) quantity of test scripts bounces around from one host environment to another.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions