On Fri, Jan 30, 2026 at 11:00:29PM +0100, [email protected] wrote: > On Sat, Jan 17, 2026 at 11:49:58AM +0200, Eli Zaretskii wrote: > > > > Since the tests run with Terxinfo uninstalled, I wonder whether the > > test suite harness sets things up so as to find and load the DLLs > > just built. Showing that as part of the test would go a long way > > towards flagging any issues with finding the DLLs, and will also > > indicate which parts of the code were actually tested -- the Perl code > > or the equivalent C code. Right now, I have no idea. And looking in > > config.log and Makefile's doesn't help, because I already know the > > configure script concluded the extensions could be built, and I also > > know that they were in fact built. I just don't know whether they > > were used when running the test suite. > > On that subject, I think that the best way to go is first to improve the > TEXINFO_XS=requiredifenabled such that it can be set for tests. That > would remove most if not all ambiguity on the code used. This will have > to wait for the next release. > > Once this is done, we could think again whether we want to give some > information somewhere.
See my other email - I think it should be possible to do easily now.
