unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Carsten Mattner <carstenmattner@googlemail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: Chong Yidong <cyd@gnu.org>, emacs-devel@gnu.org
Subject: Re: Pretest note
Date: Tue, 13 Mar 2012 11:31:25 +0100	[thread overview]
Message-ID: <CACY+HvqUhVZTt3Q_aXH3rrVQHEtzX8+GOr9dbjG-MBafhsLevg@mail.gmail.com> (raw)
In-Reply-To: <87aa3kdevf.fsf@thinkpad.tsdh.de>

On Tue, Mar 13, 2012 at 10:33 AM, Tassilo Horn <tassilo@member.fsf.org> wrote:
> If you have ImageMagick installed, then I think emacs will build with
> support for it.  So you might also want to say --without-imagemagick.
> Ditto for --without-rsvg.

Thanks Tassilo.

I don't have imagemagick or rsvg installed, but I'll add it to the list
just in case I ever happen to build on a system with.

Updated and cleaned up linux opts:
--without-selinux  --without-dbus --without-gconf \
    --without-gsettings --without-sound --without-xft --without-gpm \
    --without-tiff --without-jpeg --without-gif --without-png \
    --with-x-toolkit=no --without-gnutls --without-xml2 \
    --without-rsvg --without-imagemagick

Added --without-libxml2 to the Mac configure settings:
CFLAGS=$CFLAGS CC='gcc -arch i386' ./configure --with-ns \
    --without-gnutls --without-xml2

> That said, if you don't open images/SVGs, neither one should be the
> cause of the leak.

Makes sense.
I do wonder how --with-ns is able to make use of XPMs without linking libXpm
according to the autoconf results reports.
Should I add the same --without options to the --with-ns build?
autoconf doesn't indicate to add support for those libs but apparently
Cocoa has other means to indireclty make use of them via ImageKit or
whatever the library is called.



  reply	other threads:[~2012-03-13 10:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12  3:13 Pretest note Chong Yidong
2012-03-12  6:17 ` Jambunathan K
2012-03-12 11:08 ` Leo
2012-03-12 11:12   ` Lars Magne Ingebrigtsen
2012-03-12 11:30     ` Leo
2012-03-12 13:39 ` Carsten Mattner
2012-03-13  6:25   ` Chong Yidong
2012-03-13  9:02     ` Carsten Mattner
2012-03-13  9:16       ` Carsten Mattner
2012-03-13  9:17         ` Carsten Mattner
2012-03-13  9:33         ` Tassilo Horn
2012-03-13 10:31           ` Carsten Mattner [this message]
2012-03-13 10:46             ` Carsten Mattner
2012-03-13 10:28     ` Jan Djärv
2012-03-13 10:39     ` Jan Djärv
2012-03-14  6:24       ` Chong Yidong
2012-03-14 10:25     ` Carsten Mattner
2012-03-12 16:30 ` John Yates
2012-03-13  6:31   ` Chong Yidong
2012-03-12 22:34 ` David De La Harpe Golden
2012-03-13 13:00   ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2012-03-14 20:22 Angelo Graziosi

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=CACY+HvqUhVZTt3Q_aXH3rrVQHEtzX8+GOr9dbjG-MBafhsLevg@mail.gmail.com \
    --to=carstenmattner@googlemail.com \
    --cc=cyd@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tassilo@member.fsf.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).