I’ve added some extra plug-ins to the GIMP build process, and they install correctly when building natively.
I’ve used the Meson install path: gimpdatadir / 'plug-ins' / 'artbox-fu' / plugin
which puts them in the expected location: /share/gimp/3.0/plug-ins/
I notice that GIMP does not explicitly list this location in the folder preferences, however it does link to that location…
…except when GitLab creates an AppImage from the same branch, the plug-ins are nowhere to be found when I launch the AppImage. Could anyone point me in the right direction to solve this issue? I understand that the AppImage build is experimental. Perhaps it’s something I need to change in the AppImage build script?
Another thing to note, the GIMP 3.0 plug-in folder is currently empty by default, so this might be a first instance of an issue.
it’s not possible to edit the comment, it was deleted to avoid dead ends.
the AppImage was removed from the default branch, here is the AppImage ‘storage’ branch.
the data directory name stays the same for the ‘artbox’ fork.
this shared location is fine to use as a location to put the plug-ins for native building, that works;
‘plug-ins’ location for installing extra plugins by a meson and ninja build.
The AppImage is not recognising the same plug-ins folder, that’s the puzzling thing for me. Perhaps the plugins are never bundled, or perhaps the gimpdata ‘plug-ins’ folder in the default share location: /home/mark/code/gnome/share/gimp/3.0/plug-ins/
Is not recognised by the Appimage due to its isolated nature?
The script seems to take care of the bundling, where files are picked from, using the prefix generated by GitLab?
and I can’t see anything pointing to a location that might cause location problems;
This for example is absent from the yml and 2_bundle…
“$GIMP_PREFIX/build/gimp”