Let's say that you are building it somewhere like /opt
Let's also say that your babl/gegl are in /opt/babl and /opt/gegl respectively.
Then, I would do the following:
export PKG_CONFIG_PATH=/opt/babl/lib/pkgconfig;/opt/gegl/lib/pkgconfig;$PKG_CONFIG_PATH
Babl has no dependencies and so you can build it first.
Then to build gegl, I would say
./configure --prefix=/opt/gegl LIBS=-L/opt/babl/lib CPPFLAGS=-I/opt/babl/include
For gimp then I would say
./configure --prefix=/opt/gimp LIBS="-L/opt/babl/lib -L/opt/gegl/lib"
CPPFLAGS="-I/opt/babl/include -I/opt/gegl/include"
etc.
Note that both gegl and gimp pick up the libraries from PKG_CONFIG_PATH
On Sun, Feb 22, 2015 at 12:14 PM, Elle Stone
<ellestone@xxxxxxxxxxxxxxxxxxxx> wrote:
> On 02/22/2015 11:27 AM, Partha Bagchi wrote:
>>
>> Welcome back. :)
>
> Thanks!
>
>> Can you not simply pass the LIB statement to configure/autogen or
>> adjust PKG_CONFIG_PATH?
>
>
> I use these commands to set up the prefix before installing and updating
> babl/GEGL/GIMP:
>
> prefix=/home/elle/code/gimpdefault/run
> exec_prefix=${prefix}
> libdir=${exec_prefix}/lib
> includedir=${prefix}/include
> datarootdir=${prefix}/share
>
> The babl/GEGL/GIMP run/lib/pkgconfig/ pc files have text like this
> (sometimes fewer or more lines):
>
> prefix=/home/elle/code/gimpdefault/run
> exec_prefix=${prefix}
> libdir=${exec_prefix}/lib
> includedir=${prefix}/include
> datarootdir=${prefix}/share
>
> Is there another step involved in passing the LIB statement to
> configure/autogen or adjusting the PKG_CONFIG_PATH?
>
> Elle
_______________________________________________
gimp-developer-list mailing list
List address: gimp-developer-list@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
