Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I compile with
PATH=/opt/bin:$PATH ; export PATH
LD_LIBRARY_PATH=/opt/lib:$LD_LIBRARY_PATH ; export LD_LIBRARY_PATH
./configure --prefix=/opt --enable-contrast --enable-extras
ldd ufraw-gimp | grep gegl shows: libgegl-0.2.so.0 => /usr/lib64/libgegl-0.2.so.0 (0x00007fe61ebdd000)
The correct libgegl-0.2 is in /opt/lib
Right now ufraw does not export directly into gimp-2.9 from gimp master; I've got a bug on this problem. I'm wondering if ufraw is looking in the wrong place for libgegl-0.2
Niels Kristian Bech Jensen
It looks like a linker configuration problem. Make sure that /opt/lib is the first line in /etc/ld.so.conf and run ldconfig as root.
Regarding the export to gimp problem: Make sure the 'gimp' exists in /opt/bin. It is probably a symbolic link to 'gimp-2.9'.
I'll take a 'my-duh' for starting ufraw in /opt/bin. I'm now using a wrapper script that includes LD_LIBRARY_PATH=/opt/lib.
My problem is that ufraw / gimp (from git master) no longer can export (or whatever you call it) a file directly into gimp from ufraw.
I'm wondering: can anyone, using the latest ufraw from cvs and gimp / gegl / babl from their git masters open a raw image in ufraw and transfer it to gimp?