unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Emanuele Giaquinta <emanuele.giaquinta@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: configure.in fix
Date: Sat, 5 Jul 2008 13:03:42 +0200	[thread overview]
Message-ID: <20080705110342.GA30287@orion.lan> (raw)
In-Reply-To: <x2d4lto0g4.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

On Fri, Jul 04, 2008 at 04:31:55PM -0400, Glenn Morris wrote:

> You have quite a few changes installed now, and should probably sign
> papers if you want to contribute more. Let me know if you are willing.

My contributions so far have been almost trivial, do they sum up to a
significant contribution?

> I know you have another configure.in patch that never (?) got applied.
> http://lists.gnu.org/archive/html/emacs-devel/2008-02/msg01918.html
> 
> Is it still needed?

It is needed to detect at configure time the availability of a recent
enough fontconfig version, as opposed to fail at build time. The
attached patch should be better.

> Also on this topic, can anyone tell me if HAVE_FREETYPE is required
> for the new font code, or can it work without it?

It can work without it, see line 523 in src/Makefile.in.

[-- Attachment #2: configure-fontconfig.diff --]
[-- Type: text/x-diff, Size: 1073 bytes --]

diff --git a/configure.in b/configure.in
index 310e5a5..7195ab6 100644
--- a/configure.in
+++ b/configure.in
@@ -1765,6 +1765,8 @@ either XPointer or XPointer*.])dnl
 fi
 
 ### Start of font-backend section.
+PKG_CHECK_MODULES(FONTCONFIG, fontconfig >= 2.2.0, HAVE_FC=yes, HAVE_FC=no)
+test "${HAVE_FC}" = "no" && with_freetype=no
 
 ## Use -lXft if available, unless `--with-freetype=no' nor `--with-xft=no'.
 HAVE_XFT=maybe
@@ -1808,16 +1810,11 @@ if test "${HAVE_XFT}" = "yes"; then
   dnl As we use Xft, we anyway use freetype.
   dnl In this case, there's no need of additional CFLAGS and LIBS.
   HAVE_FREETYPE=yes
+  FONTCONFIG_CFLAGS=
+  FONTCONFIG_LIBS=
 elif test "x${with_freetype}" != "xno"; then
 
   PKG_CHECK_MODULES(FREETYPE, freetype2, HAVE_FREETYPE=yes, HAVE_FREETYPE=no)
-  if test "${HAVE_FREETYPE}" = "yes"; then
-    PKG_CHECK_MODULES(FONTCONFIG, fontconfig, HAVE_FC=yes, HAVE_FC=no)
-    if test "${HAVE_FC}" = "no"; then
-      dnl Without fontconfig, we can't use freetype at the moment.
-      HAVE_FREETYPE=no
-    fi
-  fi
 fi
 
 HAVE_LIBOTF=no

  reply	other threads:[~2008-07-05 11:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 14:10 configure.in fix Emanuele Giaquinta
2008-07-04 20:31 ` Glenn Morris
2008-07-05 11:03   ` Emanuele Giaquinta [this message]
2008-07-08  7:18     ` Glenn Morris
2008-07-09  7:28       ` Glenn Morris

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=20080705110342.GA30287@orion.lan \
    --to=emanuele.giaquinta@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.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).