From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Running external info within Emacs
Date: Sat, 01 Apr 2023 18:34:25 +0300 [thread overview]
Message-ID: <83o7o7y5tq.fsf@gnu.org> (raw)
In-Reply-To: <86y1nbpsp8.fsf@gnu.org> (message from Arash Esbati on Sat, 01 Apr 2023 16:45:07 +0200)
> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 01 Apr 2023 16:45:07 +0200
>
> > A native port is available, and you could even produce it by yourself
> > if my 32-bit port doesn't suit you for some reason. (I was wondering
> > for a long time why the MSYS2/MinGW64 project doesn't provide a native
> > Windows build of Texinfo, since the upstream project supports such a
> > build since about forever.)
>
> Using your port will be complicated, I think. Your tarball contains
> libiconv-2.dll and libintl-8.dll which are both part of MinGW64 as well
> under /ming64/bin. Not tested, but that I'm afraid that will trouble in
> $PATH in terms of who comes first.
Put the programs, with the dependency DLLs, in a separate directory.
Windows always prefers the DLLs that live in the same directory as the
executable that loads them, so if the DLLs are together with the .exe,
the order of PATH shouldn't matter.
next prev parent reply other threads:[~2023-04-01 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:56 Running external info within Emacs Arash Esbati
2023-03-30 13:17 ` Eli Zaretskii
2023-03-30 15:00 ` Arash Esbati
2023-03-30 15:56 ` Eli Zaretskii
2023-03-31 6:43 ` Arash Esbati
2023-03-31 7:10 ` Eli Zaretskii
2023-03-31 18:09 ` Arash Esbati
2023-03-31 19:07 ` Eli Zaretskii
2023-04-01 10:51 ` Arash Esbati
2023-04-01 11:37 ` Eli Zaretskii
2023-04-01 14:45 ` Arash Esbati
2023-04-01 15:34 ` Eli Zaretskii [this message]
2023-04-02 17:04 ` Arash Esbati
2023-04-02 17:14 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7o7y5tq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).