From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How about using static link instead of dynamic loaded dlls?
Date: 05 Jun 2003 07:53:49 +0100 [thread overview]
Message-ID: <u8yshypz6.fsf@jasonrumney.net> (raw)
In-Reply-To: <u3cipxl9b.fsf@knight.6test.edu.cn>
Robin Hu <huxw@knight.6test.edu.cn> writes:
> Hi everyone:
>
> Current CVS NtEmacs snapshot loads libjpeg.dll in runtime. This
> causes a problem while I have some different versions of libjpeg.dll
> in %PATH%
If you explain what problems you are having, we may be able to fix
them. Linking the image libraries statically might work well for
people like yourself who compile Emacs yourself, but in the Windows
world you are the minority I am afraid, so linking dynamically is
more flexible for binary distribution.
It should be fairly straightforward to produce a patch that allows
either static or dynamic linking as a configure option, but I do not
have time to do this myself.
> This should be helpful to avoid dll hell, and may also helpful to
> workaround VC's bug in compiling w32fns.c(this bug will not
> re-produced while compiling w32fns.c with intel c compiler, so I
> believe this is a bug of VC itself).
Please explain. It is very rare to find a bug in a compiler these
days. More often it is a particular optimization that a compiler does
that show up a subtle bug in the code.
next prev parent reply other threads:[~2003-06-05 6:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 3:21 How about using static link instead of dynamic loaded dlls? Robin Hu
2003-06-05 6:53 ` Jason Rumney [this message]
2003-06-05 9:05 ` Mike Woolley
2003-06-05 9:51 ` Jason Rumney
2003-06-05 12:28 ` Benjamin Riefenstahl
2003-06-05 10:57 ` Robin Hu
2003-06-05 12:06 ` Jason Rumney
2003-06-05 19:38 ` Juanma Barranquero
2003-06-05 21:26 ` Jason Rumney
2003-06-05 21:29 ` Juanma Barranquero
2003-06-05 21:52 ` Juanma Barranquero
2003-06-05 17:11 ` David Masterson
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=u8yshypz6.fsf@jasonrumney.net \
--to=jasonr@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).