On Tue, Sep 15, 2026 at 02:58:58PM +0300, Eli Zaretskii wrote: > > with $prefix, it would be > > usr/local/bin/texi2any > > usr/local/lib/texi2any/lib/libtexinfo.la > > > > or, using the autoconf/automake conventions, + CONVERTER == texi2any > > $(bindir)/texi2any > > $(libdir)/$(CONVERTER)/lib/libtexinfo.la > > > > librarydir is defined by: > > converterlibdir = $(libdir)/$(CONVERTER) > > librarydir = $(converterlibdir)/lib > > > > and the library is in librarydir, so we could also say > > > > $(bindir)/texi2any > > $(librarydir)/libtexinfo.la > > With this structure, you need to put the DLL in $(bindir). AFAIU, > using libtool will by default put it in $(librarydir)/../bin, which is > not what you want, because that directory will not be on PATH.
Indeed, but my understanding of the -bindir option to libtool is to change the default, and replace $(librarydir)/../bin by another possibility as explained on: https://www.gnu.org/software/libtool/manual/html_node/Link-mode.html what I set: -bindir $(librarydir)/../../../bin should allow to change the default such that libtool would put the DLL in $(librarydir)/../../../bin, which should be $(bindir). I cannot test, so I may be off, but it is worth trying. > The > Windows loader of DLLs looks first in the same directory where the > program which loads the DLL lives, then on PATH (this is a very severe > simplification: the actual algorithm is much more complex, but these > two places are the only ones on which you can rely for any end-user > system). -- Pat
