unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: David Abrahams <dave@boost-consulting.com>
Subject: Re: image display in MinGW build?
Date: Mon, 8 May 2006 12:38:42 +0200	[thread overview]
Message-ID: <f7ccd24b0605080338k233f85b8pd1c9efd0fa832198@mail.gmail.com> (raw)
In-Reply-To: <ur735xh87.fsf@boost-consulting.com>

On 5/8/06, David Abrahams <dave@boost-consulting.com> wrote:

> But I must've done something wrong
> because I just tried again... and it worked!  Happy, happy, joy, joy.
>

Glad it is working; anyway, to help debugging if this happens again to
you, you can use the `image-types' variable (which lists the image
types known, i.e., their support was compiled in), and the
`image-type-available-p' function (which indicates whether the image
type is actually available to Emacs).

In a fully configured MinGW build, `image-types' contains '(png gif
tiff jpeg xpm xbm pbm). If any of them is missing, there was some
problem locating the library headers at compile time (assuming they
were not explicitly left out with configure.bat, of course).

If an image type does appear in `image-types', but
(image-type-available-p type) returns nil, Emacs was unable to locate
the library .DLL.

Note, however, that the result of `image-type-available-p' is cached
internally, so if one library is missing and you add it to the path
*after* using `image-type-available-p' to try to load this particular
image type, it will still return nil until you restart Emacs.

Hope this helps,

--
                    /L/e/k/t/u

  reply	other threads:[~2006-05-08 10:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08  0:58 image display in MinGW build? David Abrahams
2006-05-08  3:26 ` Eli Zaretskii
2006-05-08  4:39   ` David Abrahams
2006-05-08 10:38     ` Juanma Barranquero [this message]
2006-05-08 10:59       ` David Abrahams
2006-05-08  9:11 ` Jason Rumney
2006-05-08 10:33   ` David Abrahams

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=f7ccd24b0605080338k233f85b8pd1c9efd0fa832198@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=dave@boost-consulting.com \
    /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).