> Date: Sat, 17 Jan 2026 13:03:27 +0100 > From: [email protected] > Cc: Gavin Smith <[email protected]>, [email protected] > > > Oh, so the "--enable-c-texi2any" configure-time option defaults to > > "no", not to "detect"? I thought it defaults to "detect", because > > "./configure --help" says "Use texi2any program implemented in C if > > possible", and I see ctexi2any.exe was built as part of the build, so > > evidently that _was_ possible. > > Indeed, whether ctexi2any.exe can be build is detected. > "--enable-c-texi2any" is not about building ctexi2any, but whether it is > this implementaiton of texi2any rather than the Perl one that it used in > tests and is installed. There is no "detect" value for this option, > actually, as it does not make sense. I think that it is the --help > message that is misleading. > > What about: > "Use texi2any program implemented in C if built"
Yes, that's better. Maybe also change the name of the option, since options that start with --enable or --disable are usually for optional features that are used if enabled. > > Then why isn't it used by the test > > suite (and not installed, as I say in my previous message)? > > For now, we prefer testing and installing the Perl implementation. The > speed difference is minimal, and the Perl implementation is better tested. > > As long as there is a need of Perl for indices sorting, the two > implementations are gonna be similar. OK, thanks. But if ctexi2any is not installed, neither should be the DLLs that it uses, libtexinfo*.dll, right? Or are they used by some other parts of the package?
