06-12-2025, 09:30 PM
It was quite long-winded at the beginning.
Since I can run several Gimp versions in parallel my development structure for a given version looks like this:
Since I can run several Gimp versions in parallel my development structure for a given version looks like this:
Code:
/Gimp-dev/2.10.34
├── build
│ ├── babl
│ ├── gegl
│ ├── gimp
│ ├── GIMP-Lensfun
│ ├── GMIC-3.1.6
│ ├── libmypaint
│ ├── mypaint-brushes
│ ├── pango-1.47.0
│ └── resynthesizer
├── extra
└── run
├── bin
├── etc
├── include
├── lib
├── libexec
└── share
- the root (/Gimp-dev/2.10.34 here) contains a script that is sourced to set up the proper environment
- build holds the source directories (git pull from repos for babl/gegl/gimp, tarballs for others)
- as you can see Gimp added a requirement for a recent version of pango so I had to add it to the mix.
- the "prefix" points to the run directory
- after a successful build the products are installed under run (so for instance the Gimp executable ends up as /Gimp-dev/2.10.34/run/bin/gimp-2.10.
- I start Gimp through a script that sets up the proper PATH/LD_LIBRAY_PATH/GI_TYPELIB_PATH and Gimp profile directory