GIMP in 20.04

[rich2005]

You have to make a splashes folder in your user profile.

As described here: https://docs.gimp.org/2.10/en/customize-...creen.html

example: https://i.imgur.com/YO4ZS3w.jpg

[meetdilip]

Works great !! Many thanks.

[meetdilip]

How can I install GIMP through App Image ? Is it easy /safe ? Thanks.

I tried from your link in other post and landed at this page

https://github.com/aferrero2707/gimp-plu...continuous

Took the instructions and executed

1. GMIC-Gimp-2.10-linux.AppImage

2. ResynthesizerPlugin-Gimp-2.10-linux.AppImage

Now I have

/home/name/.config/GIMP-AppImage/2.10/plug-ins/

But GIMP is not reading anything from it.

[Ofnuts]

A bit more hardcore but I bit the bullet and installed Gimp from source. Not too hard, the main problem is figuring out the packages that you need. If you installed Gimp from the repos you have most of them anyway, you mostly need the development versions.

The process starts here: https://wiki.gimp.org/wiki/Hacking:Building

I can help you fill the gaps.

[meetdilip]

I am not that good. If this goes on like this, either I will downgrade to 18.04 or use GIMP with whatever available. Your ofn-erase-background is my favourite so far. Worked in snap, but now I use Discover store in Kubuntu 20.04 it is not working.

Everyone was saying using AppImage will fix it. Tried that, now I have 2 folders under .config -- GIMP and GIMP-AppImage

I know you are trying to help. But 20.04 seems to have made things hard for normal users like me. So grateful for your guidance.

[rich2005]

(05-04-2020, 01:27 AM)meetdilip Wrote: How can I install GIMP through App Image ? Is it easy /safe ? Thanks.

I tried from your link in other post and landed at this page

https://github.com/aferrero2707/gimp-plu...continuous

Took the instructions and executed

1. GMIC-Gimp-2.10-linux.AppImage

2.  ResynthesizerPlugin-Gimp-2.10-linux.AppImage

Now I have

/home/name/.config/GIMP-AppImage/2.10/plug-ins/

But GIMP is not reading anything from it.

The Resynthesizer appimage should install but have you the correct version of Gimp? Make life easy for yourself as:

The Gimp Appimage:  To recap:

Get it from  https://github.com/aferrero2707/gimp-appimage/releases/   There are different versions available. Some are 'withplugins' and contain extra library files and one or two pre-installed plugins resynthesizer and gimp_gmic_qt 

There is the current 'stable' 2.10.18 get the one with plugins
https://github.com/aferrero2707/gimp-app...4.AppImage

or there is a weekly updated pre-Gimp 2.10.20 Worth considerating, some notable bugs are fixed such as the python non-working font chooser. 
https://github.com/aferrero2707/gimp-app...4.AppImage

Installation: Copy to a folder somewhere, does not always need to be in your home folder. Make the file executable, Run it.
If you need a desktop file for a menu entry, use the kde menu editor: https://i.imgur.com/3EfBYmd.jpg

Working: 
Same as a regular gimp it makes a user profile: ~/.config/GIMP-AppImage/2.10/
Any extra resources you need fonts / brushes / scripts / plugins go there.

[rich2005]

(05-04-2020, 06:28 AM)Ofnuts Wrote: A bit more hardcore but I bit the bullet and installed Gimp from source. Not too hard, the main problem is figuring out the packages that you need. If you installed Gimp from the repos you have most of them anyway, you mostly need the development versions.

The process starts here: https://wiki.gimp.org/wiki/Hacking:Building

I can help you fill the gaps.

How about a complete rundown on the process? Did you use 'buntu 20.04?

Last time I compiled Gimp was a Gimp 2.7 so that tells you how long ago that was. Added nearly a GB in devel files (I was using PClinuxOS at the time) Came to the conclusion then, not worth the added bloat, Although these days I would use a VM.

Current situation, not looking promising. Thorsten Stettin could do with some help. I keep an eye on https://launchpad.net/~otto-kesselgulasc...le-prepare for what eventually goes in the Gimp PPA.

[meetdilip]

Thanks @rich2005

I am downloading this one. Is it ok if I go ahead and install ?

Quote:There is the current 'stable' 2.10.18 get the one with plugins
https://github.com/aferrero2707/gimp-app...4.AppImage

How to do I uninstall the previous app images ?

[rich2005]

(05-04-2020, 08:41 AM)meetdilip Wrote: I am downloading this one. Is it ok if I go ahead and install ?
...snip...
How to do I uninstall the previous app images ?

Just make sure it is 'withplugins' version

These are self-contained files. To remove, all you need to do is delete the file. 

The User profile ~/.config/GIMP-AppImage/2.10/ remains. This means the newer version can use the same setup as the last one. If you want to start afresh, then delete that as well.

[Ofnuts]

(05-04-2020, 07:57 AM)rich2005 Wrote:

(05-04-2020, 06:28 AM)Ofnuts Wrote: A bit more hardcore but I bit the bullet and installed Gimp from source. Not too hard, the main problem is figuring out the packages that you need. If you installed Gimp from the repos you have most of them anyway, you mostly need the development versions.

The process starts here: https://wiki.gimp.org/wiki/Hacking:Building

I can help you fill the gaps.

How about a complete rundown on the process? Did you use 'buntu 20.04?

Last time I compiled Gimp was a Gimp 2.7 so that tells you how long ago that was. Added nearly a GB in devel files (I was using PClinuxOS at the time) Came to the conclusion then, not worth the added bloat, Although these days I would use a VM.

Current situation, not looking promising. Thorsten Stettin could do with some help. I keep an eye on https://launchpad.net/~otto-kesselgulasc...le-prepare for what eventually goes in the Gimp PPA.

No, still on 19.10. Not sure the PPA problems are due to 20.04... the PPA has been stalled well before 20.04 came out.

A complete rundown would duplicate a lot of the linked page. Of course I could go down to source management and compiler theory, but I think it's best if you try, stall, ask, and so forth.

In addition to the page above, my environment looks like this (I have both 2.10 and 2.99...)

Code:

[top directory]
.
├── 2.10
│   ├── build
│   │   ├── babl
│   │   ├── gegl
│   │   ├── gimp
│   │   ├── libmypaint
│   │   └── mypaint-brushes
│   ├── run
│   │   ├── bin
│   │   ├── etc
│   │   ├── include
│   │   ├── lib
│   │   ├── libexec
│   │   └── share
│   └── setenv
├── 2.99
│   ├── build
│   │   ├── babl
│   │   ├── gegl
│   │   ├── gimp
│   │   ├── libmypaint
│   │   └── mypaint-brushes
│   ├── run
│   │   ├── bin
│   │   ├── etc
│   │   ├── include
│   │   ├── lib
│   │   ├── libexec
│   │   └── share
│   └── setenv

• In both branches, build is where the source code is, run are the executables
  
• Everything in the tree above are directories, except setenv which is a small script that sets environment variables (attached, you have to "source" it, ie . setenv or source setenv, otherwise it runs in a subshell and the environment variables are set in the subshell which is of little use). It set variables relative to itself, so don't move it.
  
• babl/gegl/my_paint stuff are identical in both 2.10 and 2.99 branches, I could possibly optimize that (or even have share the run beytween 2.10 and 2.99) but I will do it later.
  
• When you do the initial git clone you must be  in build, cloning will create the directories under it. Later git commands require to be passed in the package directory (gimp, gegl...)
  
• You need to install:
  • build/compile utilities: build-essentials meson ninja-build
    
  • development packages: libglib2.0-dev-bin libgtk-3-dev gobject-introspection python-cairo-dev python-gtk2-dev
    
• If the meson builds fail, try removing the contents of the _build directory
  
• By default compiling gets your the 2.99 version with latest changes
  
• For 2.10, all other packages are the same, in Gimp:
  • git checkout GIMP_2_10_18 (I don't know what to check out to pull the latest 2.10 fixes)
    
  • Only the "classic" build (autogen+make) is available for 2.10
    
• If you want to update the code, issue git pull in the directory of the relevant package. In most cases you can just recompile (make or ninja steps).
  
• To execute Gimp, you have to use the same environment (so run appropriate setenv for the version you launch).
  
  

My current setenv:

Code:

#! /bin/bash
# Shebang for kate, this file must be sourced

export GIMP_PREFIX=$(readlink -e $(dirname $(readlink -e $BASH_SOURCE))/run)
echo "GIMP_PREFIX:" $GIMP_PREFIX

# Used to find programs/tools during build
export PATH="${GIMP_PREFIX}/bin:$PATH"

# Used to detect the build dependencies
export PKG_CONFIG_PATH="${GIMP_PREFIX}/lib/pkgconfig:${GIMP_PREFIX}/share/pkgconfig"

# Used to find the glib-introspection dependencies
export XDG_DATA_DIRS="${GIMP_PREFIX}/share:/usr/share:$XDG_DATA_DIRS"

# Used to find the libraries at runtime
export LD_LIBRARY_PATH="${GIMP_PREFIX}/lib:${LD_LIBRARY_PATH}"

# Used by Autotools to find its tools
#export ACLOCAL_FLAGS="-I $INSTALL_PREFIX/share/aclocal $ACLOCAL_FLAGS"
#export ACLOCAL_FLAGS="-I $GIMP_PREFIX/share/aclocal $ACLOCAL_FLAGS"
export ACLOCAL_FLAGS="-I $GIMP_PREFIX/share/aclocal -I /usr/share/aclocal"

# Note: if you don't include the default value of XDG_DATA_DIRS, you may get a compile error trying to read a PNG icon file. You could try using this in that case:
# export XDG_DATA_DIRS="${GIMP_PREFIX}/share:/usr/local/share:/usr/share"

# For Debian or derivatives (Ubuntu, Mint…) only:
# Additionally to the previous commands (not in replacement), update some variables this way if you use a Debian derivative:

arch="$(dpkg-architecture -qDEB_HOST_MULTIARCH 2> /dev/null)"
export PKG_CONFIG_PATH="${GIMP_PREFIX}/lib/${arch}/pkgconfig:${GIMP_PREFIX}/share/${arch}/pkgconfig:$PKG_CONFIG_PATH"
export LD_LIBRARY_PATH="${GIMP_PREFIX}/lib/${arch}:$LD_LIBRARY_PATH"

# Number or parallel compiles and others  (# of available procs -2, for me)
export PROCS=6

# Missing directory
mkdir -p $GIMP_PREFIX/share/aclocal

Enjoy