unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sascha Wilde <wilde@sha-bang.de>
To: martin rudalics <rudalics@gmx.at>
Cc: "Miles Bader" <miles@gnu.org>,
	"Nick Roberts" <nickrob@snap.net.nz>,
	"Jan Djärv" <jan.h.d@swipnet.se>,
	emacs-devel@gnu.org
Subject: Re: new image library "requirements"
Date: Mon, 18 Jun 2007 17:37:58 +0200	[thread overview]
Message-ID: <m2bqfd9stl.fsf@kenny.sha-bang.de> (raw)
In-Reply-To: <46763FE1.8000906@gmx.at> (martin rudalics's message of "Mon\, 18 Jun 2007 10\:18\:41 +0200")

martin rudalics <rudalics@gmx.at> wrote:

>> Maybe it should make a human-understandable report of missing
>> functionality at the very end of the configure run:
>
> I support that.

+1

>> ----  WARNING ----
>> The following functionalities will be missing in your compilation of
>> Emacs because of missing development libraries (specify
>> -without-FEATURE to omit warning about such a missing feature):
>>
>> jpeg: used for displaying jpeg image files
>> tiff: used for displaying tiff image files
>> xpm: used for displaying xpm image files and color icons
>> alsa: used for playing sounds from within Emacs
>
> Including a short description of the consequences when such a
> functionality is missing.

Please don't make this unnecessary verbose.  I think "The following
functionalities will be missing ... displaying jpeg image files"
perfectly clear.  People building complex software like emacs from
source should be able to understand this messages and its
consequences.

sascha
-- 
Sascha Wilde
"The primary difference [...] is that the Java program will reliably
and obviously crash, whereas the C program will do something obscure."  
   -- Java Language Tutorial

  reply	other threads:[~2007-06-18 15:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17  0:07 new image library "requirements" Miles Bader
2007-06-18  6:01 ` Jan Djärv
2007-06-18  6:09   ` Nick Roberts
2007-06-18  7:34     ` David Kastrup
2007-06-18  8:18       ` martin rudalics
2007-06-18 15:37         ` Sascha Wilde [this message]
2007-06-18 15:39           ` Lennart Borgman (gmail)
2007-06-18 19:26       ` Eli Zaretskii
2007-06-19  5:54         ` Jan Djärv
2007-06-19  6:06           ` Eli Zaretskii
2007-06-19  7:28             ` David Kastrup
2007-06-19  7:53               ` Jason Rumney
2007-06-19 22:27               ` Richard Stallman
2007-06-20  1:08                 ` Stefan Monnier
2007-06-19 22:26         ` Richard Stallman
2007-06-20  1:07           ` Stefan Monnier
2007-06-20 17:35             ` Richard Stallman
2007-06-20  3:18           ` Eli Zaretskii
2007-06-20  5:38             ` David Kastrup
2007-06-20  5:50             ` Jan Djärv
2007-06-20  7:30               ` David Kastrup
2007-06-20  7:37                 ` Glenn Morris
2007-06-20 22:17               ` Jason Rumney
2007-06-20 17:35             ` Richard Stallman
2007-06-20 19:39               ` Jan Djärv
2007-06-21 17:32                 ` Richard Stallman
2007-06-19 10:41       ` Richard Stallman
2007-06-19 11:14         ` David Kastrup
2007-06-19 11:16         ` Nick Roberts
2007-06-19 12:09           ` Jan Djärv
2007-06-19 21:12             ` Nick Roberts
2007-06-20  5:43               ` Jan Djärv
2007-06-20 13:28               ` Richard Stallman
2007-06-18  7:30   ` David Kastrup

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=m2bqfd9stl.fsf@kenny.sha-bang.de \
    --to=wilde@sha-bang.de \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=miles@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=rudalics@gmx.at \
    /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).