From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Pango
Date: Sat, 15 Jun 2013 15:17:14 +0200 [thread overview]
Message-ID: <8738sja4yt.fsf@gnu.org> (raw)
In-Reply-To: <201306151012.24926.andreas@enge.fr> (Andreas Enge's message of "Sat, 15 Jun 2013 10:12:24 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> The include files for pango reside in
> include/pango-1.0/pango/
> Then the main include file
> include/pango-1.0/pango/pango.h
> includes lines like
> #include <pango/pango-attributes.h>
> without the pango-1.0.
>
> I see three solutions:
>
> One can modify the CPATH to include pango-1.0; I do not know how to do this
> automatically so that each and every dependency of pango profits from it.
>
> One can modify each header file (of gtk+, for instance) including
> pango/pango.h to include pango-1.0/pango/pango.h instead, which would be
> rather tedious in the long run.
>
> Or one can add a symlink
> pango -> pango-1.0/pango
Here’s a fourth one: do not change anything. :-)
Normally pango-1.0.pc has -I.../include/pango-1.0 in its Cflags, doesn’t it?
That is a common convention for “parallel installability”, and it
requires users to use pkg-config to find out what the right -I flags
are.
HTH,
Ludo’.
next prev parent reply other threads:[~2013-06-15 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 21:19 Demain Andreas Enge
2013-06-13 21:37 ` Demain Andreas Enge
2013-06-13 23:49 ` Demain Cyril Roelandt
2013-06-14 7:52 ` Demain Andreas Enge
2013-06-14 12:29 ` Demain Ludovic Courtès
2013-06-14 21:25 ` Pango Andreas Enge
2013-06-14 21:34 ` Pango Andreas Enge
2013-06-15 8:12 ` Pango Andreas Enge
2013-06-15 8:29 ` Pango Andreas Enge
2013-06-15 13:17 ` Ludovic Courtès [this message]
2013-06-15 13:31 ` Pango Andreas Enge
2013-06-15 13:49 ` Pango Ludovic Courtès
2013-06-15 14:07 ` Pango Andreas Enge
[not found] ` <87sj0j3yzh.fsf@gnu.org>
2013-06-15 20:55 ` Pango Andreas Enge
2013-06-15 12:57 ` Pango Ludovic Courtès
2013-06-15 1:58 ` Pango Cyril Roelandt
2013-06-15 7:13 ` Pango Andreas Enge
2013-06-15 13:14 ` Pango Ludovic Courtès
2013-06-15 12:56 ` Pango Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8738sja4yt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.