Re: GIMP_DATA_DIR and GIMP_PLUGIN_DIR in m4macros/gimp-2.0.m4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thu, 2006-08-10 at 14:36 +0100, Toby Speight wrote:
> I'm playing around with my plug-in build system at the moment, tidying
> up the automake/autoconf stuff as I go (and as I learn about autotools -
> I'm a newbie there).  One thing I do is find the Gimp plug-in directory
> like so:
> 
> /--------
> | GIMP_LIBDIR=`$PKG_CONFIG --define-variable=prefix='DESTDIR' \
> |    --variable=gimplibdir gimp-2.0`
> \--------
> 
> On discovering Gimp's own autoconf macro file, I discover that it does
> almost what I need:
> 
> /--------
> |     GIMP_DATA_DIR=`$PKG_CONFIG $pkg_name --variable=gimpdatadir`
> |     GIMP_PLUGIN_DIR=`$PKG_CONFIG $pkg_name --variable=gimplibdir`
> \--------
> 
> The difference being that I have passed in the DESTDIR directory
> supplied by Automake and used to target the installation.  Without
> this, "make distcheck" fails because it tries to write to the real
> plug-ins directory rather than the supplied staging directory.

Yes, that has always been a problem for plug-ins. The plug-in needs to
be installed to the GIMP plug-in directory which may be somewhere
completely different than what's configured as the plug-in's prefix. I
haven't seen a workaround for this yet. If your change works well, we
should probably adopt it.


Sven


_______________________________________________
Gimp-developer mailing list
Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux