unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robin Hu <huxw@knight.6test.edu.cn>
Subject: How about using static link instead of dynamic loaded dlls?
Date: Thu, 05 Jun 2003 03:21:04 +0000	[thread overview]
Message-ID: <u3cipxl9b.fsf@knight.6test.edu.cn> (raw)

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%, because these versions are not binary compatible. And
   this problems can not be easily get rid of, because NtEmacs tries to
   load this dll via several names, such as libjpeg.dll jpeg-62.dll. We
   are in the hell of dlls now.

   I suggest to use static link instead of dynamic loaded dll files, or
   even more, include source files of these image libraries
   directly. 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).

   I've planned to do this, and I'd like to know if this is an
   acceptable idea before I really start doing this.

   robin.hu

             reply	other threads:[~2003-06-05  3:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  3:21 Robin Hu [this message]
2003-06-05  6:53 ` How about using static link instead of dynamic loaded dlls? Jason Rumney
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=u3cipxl9b.fsf@knight.6test.edu.cn \
    --to=huxw@knight.6test.edu.cn \
    /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).