On Sun, May 6, 2012 at 10:26 PM, Paul Cercueil <p...@crapouillou.net> wrote:
>
> Hello,
>
> I've been trying to integrate the EFL libraries inside our small
> distribution built using Buildroot. However, I am facing a nasty
> problem: the installed .pc files (that are used by pkg-config) do
> contain incorrect paths.
>
> For instance, evas.pc will contain "-I${includedir}/evas-1
> -I/opt/toolchain/usr/include/eina-1". As a result, the ./configure
> script for (ie.) Edje will prepend its --prefix to those paths, which
> will become "-I/opt/toolchain/usr/include/evas-1
> -I/opt/toolchain/opt/toolchain/usr/include/eina-1".
>
> By looking at the source code, it appears that $EINA_CFLAGS is
> referenced on evas.pc.in. That value is initialized by pkg-config on the
> ./configure script. Usually, using $EINA_CFLAGS on eina.pc.in should be
> fine; but Buildroot sets the PKG_CONFIG_SYSROOT_DIR environment
> variable, which is prepended to the paths returned by pkg-config. I
> believe that environment variable should be cleared before pkg-config is
> called.I'm really wondering why EINA_CFLAGS appears in evas.pc.in. It should not. The Cflags value in evas.pc.in should contain the path needed to find evas, that's all. Same comment for EINA_LIBS. Vincent ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
