unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Please try building with librsvg on MS-Windows
Date: Tue, 31 Dec 2013 09:58:54 +0200	[thread overview]
Message-ID: <83a9fh1mf5.fsf@gnu.org> (raw)
In-Reply-To: <loom.20131231T013316-234@post.gmane.org>

> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Tue, 31 Dec 2013 00:36:41 +0000 (UTC)
> 
> Stephen J. Turnbull <stephen <at> xemacs.org> writes:
> 
> > 
> > Juanma Barranquero writes:
> > 
> >  > Yes, I unzipped the test suite ("SVG 1.1 Second Edition test suite"
> >  > from http://www.w3.org/Graphics/SVG/WG/wiki/Test_Suite_Overview) and
> >  > it creates the whole test tree. Also, IE and Chrome do show the images
> >  > correctly, so the required files are obviously there.
> > 
> 
> I upgraded my whole librsvg suite (compile with mingw64).
> After moving /usr/local/lib/gdk-pixbuf-2.0 to <emacs_dir>/lib/gdk-pixbuf-2.0 
> and /usr/local/etc/pango to <emacs_dir>/etc/pango, I get much better results.
> 
> If it still fails for you, what is the file name ?

The file name was color-prof-01-f.svg.  But the problem was that the
binary archive I prepared included a pango.modules file that mentioned
absolute file names in a specific directory, derived from --prefix
specified at configure time.  Juanma installed librsvg in a different
place, so Pango couldn't find its modules (which are shared libraries)
and load them.

Meanwhile, I found out that keeping the file names in pango.modules
relative, without any leading directories, causes Pango to look for
them in the right place, relative to the root of its installation.  So
I uploaded fixed binary zips to resolve this issue, and it should no
longer exist.

Thanks.



      reply	other threads:[~2013-12-31  7:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 18:38 Please try building with librsvg on MS-Windows Eli Zaretskii
2013-12-23 20:18 ` Dani Moncayo
2013-12-23 20:20   ` Eli Zaretskii
2013-12-24  1:46 ` Juanma Barranquero
2013-12-24  2:34   ` Stephen J. Turnbull
2013-12-24  2:46     ` Juanma Barranquero
2013-12-24  3:40       ` Stephen J. Turnbull
2013-12-24  4:35         ` Juanma Barranquero
2013-12-24  5:37           ` Stephen J. Turnbull
2013-12-24 13:19             ` bug#16240: " Juanma Barranquero
2013-12-24 14:45               ` Stephen J. Turnbull
2013-12-24 15:13                 ` Juanma Barranquero
2013-12-24 16:33                 ` Eli Zaretskii
2013-12-24 16:31               ` Eli Zaretskii
2013-12-24 14:59             ` Yuri Khan
2013-12-24 16:02               ` Stephen J. Turnbull
2013-12-31  0:36             ` Fabrice Popineau
2013-12-31  7:58               ` Eli Zaretskii [this message]

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=83a9fh1mf5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fabrice.popineau@gmail.com \
    /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).