Copied over from the original separate work in:
https://gitlab.gnome.org/Wormnest/gimp-file-plugin-tests
After that further improved and changed and added more file format
tests.
Added meson.build files to integrate it in our build, but we do not
install it for releases.
This is an extension containing a few demo plug-ins. This is good to
demonstrate the extension format. It will also allow to disable these
plug-ins (if at some point, one doesn't want to show these demo
plug-ins anymore).
And finally it deals with the fact that our plug-in code is stupid, as
it just tries to find the first executable with the same name (minus
extension) as the plug-in folder. This doesn't go well on Windows, where
the permission system is non-existent. So our code just ends up trying
to run the first file with a similar name in a plug-in folder. As the C
goat-exercise contains both an exe and the C source (and the system
probably returns files in alphabetic order), GIMP under Windows tries to
run the C source instead of the executable (this obviously doesn't go
well).
We could try to do more complex logics, like not aborting if the first
file run fails and try the next one in the plug-in folder. Or maybe just
rename the C file to another name. But any of these is just in the end
the proof that our plug-in discovery right now is just bogus. The
extension system is explicit, not based on randomly trying out files.
Plug-ins entry points are explicitly listed in the metadata manifest.
It's done, all Python plug-ins have been either ported to the new API +
Python 3, or they have been discarded (and moved to gimp-data-extras for
whoever wants to salvage them).
Let's get rid of the outdated pygimp directory (whose code has not been
built in the master branch for years now anyway)! Woohoo!
For now the whole pygimp folder is considered deprecated and will
probably end up removed (though there are some discussions and a merge
request to possibly revive it, we'll see!).
This issue was invisible when making VPATH builds, but appeared only in
source-tree builds as gettext tools are apparently mixing source and
build files. So we need to add these in the POTFILES.skip.
(cherry picked from commit 8ec5f44f2f)
In configure.ac, add --enable-windows-installer option (off by
default), which should be set to generate the necessary files for
the installer translations during the build. Using this option is
only supported when building from git, since the installer files
are not included in source tarballs.
Rename setup.isl.desktop.in to setup.isl.in, and instruct intltool
to treat it as an .ini file explicitly.
Delete generated message files during make clean.
libgimpcolor just got translatable strings, and libgimpmath might get
them in the future, but there is no reason to scan it for translations
in the wrong domains.
The changes in /plug-ins/file-exr cause modifications of the PO
configuration. This patch adds the new file to /po-plug-ins/POTFILES.in
and the new directory to /po-python/POTFILES.skip and
/po-script-fu/POTFILES.skip
Add the automake distdir to POTFILES.skip so that a make distcheck
followed by a failed make distcheck doesn't fail with
[...]
gimp-2.7.2/tools/gimp-remote-x11.c
gimp-2.7.2/tools/gimp-remote.c
If some of these files are left out on purpose then please add them to
POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
of left out files has been written in the current directory.
2008-08-21 Sven Neumann <sven@gimp.org>
* po-*/POTFILES.skip: added desktop/gimp.desktop.in. Seems to
work
around what appears to be a bug in intltool-update (version
0.40.1).
svn path=/trunk/; revision=26694
2008-06-06 Sven Neumann <sven@gimp.org>
* POTFILES.skip: fixed the insanity using a new feature in
intltool 0.40.0 that allows us to skip whole directories.
svn path=/trunk/; revision=25897