Apps :: The Gimp 2.4

Quote

I think the problem might be because 'libgthread-2.0.so.0' is still linked to DSL's glib at '/usr/lib/libglib-2.0.so.0

- you're right, when I remove /usr/lib/libglib-2.0.so.0 and replace it with a link to /opt/gimp-2.4 the error goes away.

Gimp also needed a newer version of libpng than that in dsl, the compile-3.3.5 MAX_PATH error needed fixing a couple of times and then, using a usb stick as additional memory, and after a loooong "make", it compiled.

...and it works

Now comes the time to tidy up and think about the best way to format the extension. At present, I'm working with two extensions:

cairo-1.2.uci also containing the fontconfig, freetype & xorg72 libs required by cairo [2 MB]
gimp-2.4.uci also containing gtk-2 [40 MB]

I believe there are a couple of updated gtk-2 and/or cairo extensions in the making by stupid_idiot, maybe I should wait for these?

Quote

when I remove /usr/lib/libglib-2.0.so.0 and replace it with a link to /opt/gimp-2.4 the error goes away.

1. Need care with this approach with some builds - if the Makefile sets -rpath then the extension might keep looking for the newer glib in /usr/lib and not find it. May not be a problem.

stupid_idiot's recommended approach of setting the -rpath one way or another so the library can be found in the uci is better. I think you can do this in LDFLAGS if needed with the syntax

LDFLAGS="-L/path/to/lib1 -L/path/to/lib2 -R/path/to/lib1:/path/to/lib2"

Suggest always setting LD_LIBRARY_PATH in the environment before the compile as well.

(NB the Germans agreed with stupid idiot - mismatched glib).

2. A request: perhaps consider leaving the headers in those uci extensions so we can compile other stuff against them rather than have to work out how to compile pango or something all over again? Also build and include static libs as well as shared libaries so we can build static binaries against them if need be.

I can't think of the number of times I haven't bothered compiling something because it needs a newer glib than dsl's.

Thanks.

Thanks for the suggestions.

Quote

Need care with this approach with some builds - if the Makefile sets -rpath then the extension might keep looking for the newer glib in /usr/lib and not find it. May not be a problem.

- agreed, I did this just to see if I could compile gimp at all.

Quote

Suggest always setting LD_LIBRARY_PATH in the environment before the compile as well.

- after rebooting and leaving the base dsl libs in place, starting gimp from an icon with the command "LD_LIBRARY_PATH=/opt/gimp-2.4/lib:/opt/cairo-1.2/lib /opt/gimp-2.4/bin/gimp" seems to work fine.

Quote

perhaps consider leaving the headers in those uci extensions so we can compile other stuff against them

- it was my intention to do this with cairo as a minimum (but it could be done with gimp too) since several other apps seem to depend on cairo. So far I have the headers and the *la files but not the static libs, the extension would start to get seriously large® with these?

original here.