I was trying to run the tests on Windows, and this triggers make asdf.pdf.
My windows box does not have texi2pdf.
It seems inappropriate that in order to test ASDF you have to build the manual.
Note that this seems to have changed from before minimakefile -- I used to be able to run the tests on Windows.
Fare -- any idea what changed to break this?
thanks, r
On 12/31/15 Dec 31 -1:41 PM, Robert Goldman wrote:
I was trying to run the tests on Windows, and this triggers make asdf.pdf.
My windows box does not have texi2pdf.
It seems inappropriate that in order to test ASDF you have to build the manual.
Note that this seems to have changed from before minimakefile -- I used to be able to run the tests on Windows.
Fare -- any idea what changed to break this?
Doh. Now I see: the TEST-BASIC and TEST deftestcmds have (DOC) in them.
Faré -- any objection to removing (DOC) from the TEST command?
thanks, r
On Thu, Dec 31, 2015 at 2:41 PM, Robert Goldman rpgoldman@sift.net wrote:
I was trying to run the tests on Windows, and this triggers make asdf.pdf.
My windows box does not have texi2pdf.
It seems inappropriate that in order to test ASDF you have to build the manual.
Note that this seems to have changed from before minimakefile -- I used to be able to run the tests on Windows.
Fare -- any idea what changed to break this?
I didn't follow all the changes from before minimakefile, but at least some targets have always built the documentation before running the tests. This can be fixed by removing doc from some or all of these functions: grep -B3 '[^a-z]doc[^a-z]' tools/test-* Or maybe by tweaking the doc to not fail, or to detect the existence of texi2pdf, etc. Or worked around by calling directly the targets that you want beside doc.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Be wiser than other people if you can; but do not tell them so. — Chesterfield
-
Faré -
Robert Goldman