unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building "vanilla" emacs on macOS (summary)
Date: Wed, 8 Sep 2021 16:24:37 +0100	[thread overview]
Message-ID: <YTjVta1gnlq3/Vgb@idiocy.org> (raw)
In-Reply-To: <87ee9zbwu4.fsf@codeisgreat.org>

On Wed, Sep 08, 2021 at 08:24:59AM +0530, Pankaj Jangid wrote:
> Alan Third <alan@idiocy.org> writes:
> 
> > In it's default set-up Emacs on macOS won't use libjpeg, libtiff,
> > libpng and giflib even if they're installed as those image types are
> > all built into NSImage, which is the default. So they're not
> > essential.
> 
> Ok. Then there is a bug in the generated ‘configure’ script. In my
> trials, ‘./configure’, said ‘no’ for the above libraries when I didn’t
> install the Homebrew packages and ‘yes’ otherwise.

that's true, but you don't require them as long as configure reports:

    Does Emacs use native APIs for images?                  yes (ns)

If you have both native API and the libraries built-in you can make
Emacs use either, although I can't remember off-hand how to force it
to use the libraries.

Now, if you're building Emacs 27 it won't report that, but it will
still prefer the native image API, and I'd suggest whatever else you
do you don't actually want to use giflib as the native gif support is
less buggy.
-- 
Alan Third



  reply	other threads:[~2021-09-08 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07  3:58 Building "vanilla" emacs on macOS (summary) Jean-Christophe Helary
2021-09-07 10:17 ` Pankaj Jangid
2021-09-07 11:28   ` Jean-Christophe Helary
2021-09-07 13:36   ` Jean-Christophe Helary
2021-09-07 17:49     ` Pankaj Jangid
2021-09-07 23:03   ` Alan Third
2021-09-07 23:44     ` Jean-Christophe Helary
2021-09-08  2:54     ` Pankaj Jangid
2021-09-08 15:24       ` Alan Third [this message]
2021-09-09  3:47         ` Pankaj Jangid

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=YTjVta1gnlq3/Vgb@idiocy.org \
    --to=alan@idiocy.org \
    --cc=emacs-devel@gnu.org \
    --cc=pankaj@codeisgreat.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).