Re: Pango

[ludo@gnu.org (Ludovic Courtès)]

Andreas Enge <andreas@enge.fr> skribis:

> Am Samstag, 15. Juni 2013 schrieb Ludovic Courtès:
>> 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.
>
> Maybe, but then guix also needs to use pkg-config to find out the right -I 
> flags.
>
> Currently, when trying "guix build gtk", which has pango as input, the 
> CPATH contains
>    /nix/store/ac9zyl88qyp6gbidcyrzj8rdngbkqppr-pango-1.34.1/include ,

This one is not needed, but it doesn’t harm.

> whereas pango.pc contains the line
>    Cflags: -I${includedir}/pango-1.0
> And compilation stops with the expected error:
> In file included from ../gdk/gdkscreen.h:32:0,
>                  from ../gdk/gdkapplaunchcontext.h:31,
>                  from ../gdk/gdk.h:32,
>                  from gtkaccelgroup.h:35,
>                  from gtkaccelgroup.c:31:
> ../gdk/gdktypes.h:37:25: fatal error: pango/pango.h: No such file or 
> directory

Did you pass pkg-config as an input of GTK+?

Normally, if you do so, PKG_CONFIG_PATH gets defined appropriately, and
then I would expect the build system of GTK+ to use ‘pkg-config pango
--cflags’ in its CFLAGS.

Ludo’.