unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: dr.khaled.hosny@gmail.com, ebraminio@gmail.com,
	"K. Handa" <handa@gnu.org>, John Wiegley <johnw@gnu.org>,
	far.nasiri.m@gmail.com, Emacs developers <emacs-devel@gnu.org>,
	behdad@behdad.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Emacs text shaping using Harfbuzz
Date: Thu, 13 Dec 2018 15:01:38 -0500	[thread overview]
Message-ID: <CAFyQvY39qjshEywm3kPRLC1TpBgiY88JjtSLs1qi=kgzYN59EA@mail.gmail.com> (raw)
In-Reply-To: <8a7cd3a9-6d59-c5d7-ea59-f8090b966b27@cs.ucla.edu>

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

On Thu, Dec 13, 2018 at 2:48 PM Paul Eggert <eggert@cs.ucla.edu> wrote:

Yes, run './configure --with-harfbuzz'.
>

Thanks. That worked. This time the configure detected harfbuzz and it's
compiling right now.

To the Harfbuzz devs:

I have some specific notes on how to install Harfbuzz. I made these when I
installed 1.0.3.

Notes::

/freetype - last downloaded version -- 2.6/
/harfbuzz - last downloaded version -- 1.0.3/

https://bugs.freedesktop.org/show_bug.cgi?id=75652

freetype depends on harfbuzz and vice versa. To solve this chicken and egg
problem, do this.

1. First install freetype *without harfbuzz*
   #+BEGIN_SRC shell
   make distclean
   ./configure --prefix=$HOME/usr_local/${MY_OSREV} --without-harfbuzz
   make
   make install
   #+END_SRC
2. Then install harfbuzz
   #+BEGIN_SRC shell
   make distclean
   ./configure --prefix=$HOME/usr_local/${MY_OSREV}
   make
   make install
   #+END_SRC
3. Reinstall freetype *with harfbuzz*
   #+BEGIN_SRC shell
   make distclean
   ./configure --prefix=$HOME/usr_local/${MY_OSREV}
   make
   make install
   #+END_SRC

====

Does this harfbuzz/freetype cross-dependency still apply if trying to
install the latest harfbuzz version?

[-- Attachment #2: Type: text/html, Size: 1868 bytes --]

  parent reply	other threads:[~2018-12-13 20:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 15:39 Emacs text shaping using Harfbuzz Eli Zaretskii
2018-12-13 18:47 ` Paul Eggert
2018-12-13 19:31   ` Khaled Hosny
2018-12-13 19:48   ` Eli Zaretskii
2018-12-13 20:01     ` Eli Zaretskii
2018-12-13 20:23     ` Eli Zaretskii
2018-12-13 19:38 ` Kaushal Modi
2018-12-13 19:48   ` Paul Eggert
2018-12-13 19:55     ` Eli Zaretskii
2018-12-13 20:01     ` Kaushal Modi [this message]
2018-12-13 21:16 ` Richard Stallman
2018-12-13 21:43 ` Ken Brown
2018-12-13 23:23   ` Eric Abrahamsen
2018-12-14  0:55     ` Amin Bandali
2018-12-14  7:41       ` Eli Zaretskii
2018-12-14 14:40       ` Basil L. Contovounesios
2018-12-14 14:55         ` Eli Zaretskii
2018-12-14  7:40     ` Eli Zaretskii
2018-12-14  7:35   ` Eli Zaretskii
2018-12-14  1:11 ` Florian Beck
2018-12-14  2:35   ` Kaushal Modi
2018-12-14  7:46   ` Eli Zaretskii
2018-12-15  0:49     ` Paul Eggert
2018-12-16 14:09 ` Benjamin Riefenstahl
2018-12-16 15:27   ` Eli Zaretskii
2018-12-16 17:27 ` Mike Kupfer
2018-12-16 17:30   ` Eli Zaretskii

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='CAFyQvY39qjshEywm3kPRLC1TpBgiY88JjtSLs1qi=kgzYN59EA@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=behdad@behdad.org \
    --cc=dr.khaled.hosny@gmail.com \
    --cc=ebraminio@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=far.nasiri.m@gmail.com \
    --cc=handa@gnu.org \
    --cc=johnw@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).