RSS/Atom feed Twitter
Site is read-only, email is disabled

gegl build problem (babl include)

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 3 messages available
Toggle history

Please log in to manage your subscriptions.

gegl build problem (babl include) Mason Thomas 18 Jul 19:52
  gegl build problem (babl include) Martin Nordholts 18 Jul 19:59
   gegl build problem (babl include) Mason Thomas 18 Jul 21:29
Mason Thomas
2009-07-18 19:52:10 UTC (over 15 years ago)

gegl build problem (babl include)

Hi,

I am having some difficulty building the most recent gegl (from a git clone). I cloned the babl repository and successfully built that, but the gegl build stops when it tries to include in gegl/buffers/gegl-tile-source.h.

Note I am building these libraries in a local directory. For babl I do: ./autogen.sh --prefix=/home/mason/localinstall make
make install

and for gegl I use: BABL_LIBS=/home/mason/localinstall/lib BABL_CFLAGS="-O2" ./autogen.sh --prefix=/home/mason/localinstall make

The make fails when trying to include the babl header. Should the configure script catch the different location of the babl directories, or is there a commonly understood step I am missing?

Thanks,

-Mason

__________________

Martin Nordholts
2009-07-18 19:59:34 UTC (over 15 years ago)

gegl build problem (babl include)

On 07/18/2009 07:52 PM, Mason Thomas wrote:

Hi,

I am having some difficulty building the most recent gegl (from a git clone). I cloned the babl repository and successfully built that, but the gegl build stops when it tries to include in gegl/buffers/gegl-tile-source.h.

Note I am building these libraries in a local directory. For babl I do: ./autogen.sh --prefix=/home/mason/localinstall make
make install

and for gegl I use: BABL_LIBS=/home/mason/localinstall/lib BABL_CFLAGS="-O2" ./autogen.sh --prefix=/home/mason/localinstall
make

Hi Mason,

Instead of setting the BABL_LIBS/CFLAGS manually you should use pkg-config. To use pkg-config you set the PKG_CONFIG_PATH=/home/mason/localinstall/lib/pkgconfig

But there is an even better trick, the config.site. Put this content in the file /home/mason/localinstall/share/config.site:

export CFLAGS="-g -O0" export PKG_CONFIG_PATH="/home/mason/li/lib/pkgconfig:$PKG_CONFIG_PATH" export LD_LIBRARY_PATH="/home/mason/li/lib:$LD_LIBRARY_PATH"

and then that file will be sourced automatically whenever you invoke configure with that prefix. This means that the Makefile.am build dependencies that are setup are managed correctly and most of the time it is enough to make after a git pull --rebase.

HTH, Martin

Mason Thomas
2009-07-18 21:29:59 UTC (over 15 years ago)

gegl build problem (babl include)

Date: Sat, 18 Jul 2009 20:01:57 +0200

On 07/18/2009 07:52 PM, Mason Thomas wrote:

Hi,

I am having some difficulty building the most recent gegl (from a git clone). I cloned the babl repository and successfully built that, but the gegl build stops when it tries to include in gegl/buffers/gegl-tile-source.h.

Note I am building these libraries in a local directory. For babl I do: ./autogen.sh --prefix=/home/mason/localinstall make
make install

and for gegl I use: BABL_LIBS=/home/mason/localinstall/lib BABL_CFLAGS="-O2" ./autogen.sh --prefix=/home/mason/localinstall
make

Hi Mason,

Instead of setting the BABL_LIBS/CFLAGS manually you should use pkg-config. To use pkg-config you set the PKG_CONFIG_PATH=/home/mason/localinstall/lib/pkgconfig

But there is an even better trick, the config.site. Put this content in the file /home/mason/localinstall/share/config.site:

export CFLAGS="-g -O0" export PKG_CONFIG_PATH="/home/mason/li/lib/pkgconfig:$PKG_CONFIG_PATH" export LD_LIBRARY_PATH="/home/mason/li/lib:$LD_LIBRARY_PATH"

and then that file will be sourced automatically whenever you invoke configure with that prefix. This means that the Makefile.am build dependencies that are setup are managed correctly and most of the time it is enough to make after a git pull --rebase.

HTH, Martin

Yes, that worked. Many thanks.

-Mason

__________________