GIMPTOOL-2.0(1)

πŸ“¦
version 2.10.36 Β· 3 versions
, in ubuntu noble

πŸŽ€ NAME πŸŽ€

gimptool-2.0 β€” the little script that does a whole bunch of GIMPy things for you, no cap πŸ’–


✨ SYNOPSIS ✨

gimptool-2.0 [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help]
[--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--msvc-
syntax] [--bindir] [--sbindir] [--libexecdir] [--datadir] [--sysconfdir]
[--sharedstatedir] [--localstatedir] [--libdir] [--infodir] [--mandir]
[--includedir] [--gimpplugindir] [--gimpdatadir] [--libs] [--libs-noui]
[--cflags] [--cflags-noi] [--build plug-in.c] [--build-strip plug-in.c]
[--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-
in.c] [--install-bin plug-in] [--install-admin-strip plug-in.c]
[--install-bin-strip plug-in] [--install-admin-bin plug-in]
[--install-script script.scm] [--install-admin-script script.scm]
[--uninstall-bin plug-in] [--uninstall-admin-bin plug-in]
[--uninstall-script script.scm] [--uninstall-admin-script script.scm]

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay bestie, listen. gimptool-2.0 is that girl who can, among other things, build plug-ins or scripts for you and install them β€” as long as they're shipped as one single source file. One file. That's the vibe. 🫢

She's also the one your other programs call when they need to know what libraries and include-paths GIMP was compiled with. To pull that off, gimptool-2.0 uses pkg-config. ✨

Real talk though: if you're writing a Makefile, please just call pkg-config directly instead of calling gimptool-2.0. That's the recommended move, fr fr. πŸ’…

πŸ’… OPTIONS πŸ’…

gimptool-2.0 accepts the following options:

  • --version β€” Prints out the version of GIMP you currently have installed, straight to standard output. πŸ‘‘
  • --help β€” Prints the help blurb, showing you the commandline options people actually use the most.
  • --quiet β€” Runs quietly, no echoing any of the build commands. Shhh. πŸ™ˆ
  • --silent β€” Runs silently, no echoing any of the build commands. Literally the same thing as --quiet.
  • -n β€” Test mode. It prints the commands but does not actually execute them. Perfect for dry runs when you're just testing. 🧚
  • --just-print β€” Test mode. Prints the commands but doesn't actually execute them. Same as -n.
  • --dry-run β€” Test mode. Prints the commands but doesn't actually execute them. Same as -n.
  • --recon β€” Test mode. Prints the commands but doesn't actually execute them. Same as -n.
  • --msvc-syntax β€” Useful on Windows πŸͺŸ. Outputs the compiler and linker flags in the syntax that Microsoft's toolchain wants. It gets passed along to the pkg-config command that does most of gimptool-2.0's work.
  • --bindir β€” Outputs the bindir used to install the GIMP.
  • --sbindir β€” Outputs the sbindir used to install the GIMP.
  • --libexecdir β€” Outputs the libexecdir used to install the GIMP.
  • --datadir β€” Outputs the datadir used to install the GIMP.
  • --sysconfdir β€” Outputs the sysconfdir used to install the GIMP.
  • --sharedstatedir β€” Outputs the sharedstatedir used to install the GIMP.
  • --localstatedir β€” Outputs the localstatedir used to install the GIMP.
  • --libdir β€” Outputs the libdir used to install the GIMP.
  • --infodir β€” Outputs the infodir used to install the GIMP.
  • --mandir β€” Outputs the mandir used to install the GIMP.
  • --includedir β€” Outputs the includedir used to install the GIMP.
  • --gimpdatadir β€” Outputs the actual directory where the GIMP data files got installed. πŸ“
  • --gimpplugindir β€” Outputs the actual directory where the GIMP plug-ins got installed. πŸ”Œ
  • --build plug-in.c β€” Compiles and links plug-in.c into a GIMP plug-in. πŸ”₯
  • --build-strip plug-in.c β€” Compiles, links, and strips plug-in.c into a GIMP plug-in.
  • --install plug-in.c β€” Compiles, links, and installs plug-in.c into the user's personal GIMP plug-in directory ($XDG_CONFIG_HOME/GIMP/2.10/plug-ins).
  • --install-strip plug-in.c β€” Compiles, links, strips, and installs plug-in.c into the user's personal GIMP plug-in directory ($XDG_CONFIG_HOME/GIMP/2.10/plug-ins).
  • --install-admin plug-in.c β€” Compiles, links, and installs plug-in.c into the system-wide GIMP plug-in directory (/usr/lib/gimp/2.0/plug-ins). Big admin energy πŸ‘‘
  • --install-bin plug-in β€” Installs plug-in into the user's personal GIMP plug-in directory ($XDG_CONFIG_HOME/GIMP/2.10/plug-ins).
  • --install-admin-bin plug-in β€” Installs plug-in into the system-wide GIMP plug-in directory (/usr/lib/gimp/2.0/plug-ins).
  • --install-bin-strip plug-in β€” Installs a stripped plug-in into the user's personal GIMP plug-in directory ($XDG_CONFIG_HOME/GIMP/2.10/plug-ins).
  • --install-admin-bin-strip plug-in β€” Installs a stripped plug-in into the system-wide GIMP plug-in directory (/usr/lib/gimp/2.0/plug-ins).
  • --install-script script.scm β€” Installs script.scm into the user's personal GIMP script directory ($XDG_CONFIG_HOME/GIMP/2.10/scripts).
  • --install-admin-script script.scm β€” Installs script.scm into the system-wide GIMP script directory (${datarootdir}/gimp/2.0/scripts).
  • --uninstall-bin plug-in β€” Uninstalls plug-in from the user's personal GIMP plug-in directory ($XDG_CONFIG_HOME/GIMP/2.10/plug-ins). Bye bestie 😭
  • --uninstall-admin-bin plug-in β€” Uninstalls plug-in from the system-wide GIMP plug-in directory (/usr/lib/gimp/2.0/plug-ins).
  • --uninstall-script script.scm β€” Uninstalls script.scm from the user's personal GIMP script directory ($XDG_CONFIG_HOME/GIMP/2.10/scripts).
  • --uninstall-admin-script script.scm β€” Uninstalls script.scm from the system-wide GIMP script directory (${datarootdir}/gimp/2.0/scripts).
  • --libs β€” Prints the linker flags you need to link a GIMP plug-in. πŸ”—
  • --libs-noui β€” Prints the linker flags you need to link a GIMP plug-in, for plug-ins that don't need the GTK+ libraries.
  • --cflags β€” Prints the compiler flags you need to compile a GIMP plug-in.
  • --clags-noui β€” Prints the compiler flags you need to compile a GIMP plug-in, for plug-ins that don't need the GTK+ libraries.
  • --prefix=PREFIX β€” If you specify it, use PREFIX instead of the installation prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option also gets used for the exec prefix if --exec-prefix wasn't specified. ⚠️ It must be specified before any --libs or --cflags options.
  • --exec-prefix=PREFIX β€” If you specify it, use PREFIX instead of the installation exec prefix that GIMP was built with when computing the output for the --cflags and --libs options. ⚠️ This option must be specified before any --libs or --cflags options.

🌸 ENVIRONMENT 🌸

  • CC β€” to get the name of the C compiler you want. πŸ› οΈ
  • CFLAGS β€” to get the preferred flags to pass to the C compiler for plug-in building.
  • LDFLAGS β€” to get the preferred flags for passing to the linker.
  • LIBS β€” for passing extra libs that might be needed in the build process. For example, LIBS=-lintl.
  • PKG_CONFIG β€” to get the location of the pkg-config program that's used to determine details about your glib, pango, gtk+ and gimp installation. 🧚

🌈 SEE ALSO 🌈

gimp(1), gimprc(5), pkg-config(1)


πŸ’œ AUTHORS πŸ’œ

gimptool was written by Manish Singh (yosh@gimp.org), and it's based on gtk-config by Owen Taylor (owen@gtk.org). Iconic lineage honestly. ✨

This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins (adrian@gimp.org) and Marc Lehmann (pcg@goof.com>).


And that's the whole page bestie β€” brought to you by the GIMP Manual Pages, Version 2.10.36, and this absolute queen of a manual entry: GIMPTOOL-2.0(1). Go build something cute. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from