1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>8.3. Installing New Plugins</title>
<link rel="stylesheet" href="gimp-help-plain.css" type="text/css" />
<link rel="stylesheet" href="gimp-help-screen.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.66.1" />
<link rel="start" href="index.html" title=" " />
<link rel="up" href="ch02s08.html" title="8. Plugins" />
<link rel="prev" href="ch02s08s02.html" title="8.2. Using Plugins" />
<link rel="next" href="ch02s08s04.html" title="8.4. Writing Plugins" />
</head>
<body>
<div xmlns="" class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center" id="chaptername">8.3. Installing New Plugins</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="ch02s08s02.html">Prev</a> </td>
<th width="60%" align="center" id="sectionname">8.3. Installing New Plugins</th>
<td width="20%" align="right"> <a accesskey="n" href="ch02s08s04.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="gimp-plugins-install"></a>8.3. Installing New Plugins</h3>
</div>
</div>
</div>
<p>
The plugins that are distributed with Gimp don't require any
special installation. Plugins that you download yourself do.
There are several scenarios,
depending on what OS you are using and how the plugin is
structured. In Linux it is usually pretty easy to install a new
plugin; in Windows, it is either easy or very hard. In any
case, the two are best considered separately.
</p>
<div class="simplesect" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a id="id3315683"></a>Linux</h4>
</div>
</div>
</div>
<p>
Most plugins fall into two categories: small ones whose source
code is distributed as a single .c file, and larger ones whose
source code is distributed as a directory containing multiple
files including a Makefile.
</p>
<p>
For a simple one-file plugin, call it
<tt class="filename">borker.c</tt>, installing it is just a
matter of running the command <span><b class="command">gimptool-2.0 --install
borker.c</b></span>. This command compiles the plugin and
installs it in your personal plugin directory,
<tt class="filename">~/gimp-2.0/plugins</tt> unless you have
changed it. This will cause it to be loaded automatically the
next time you start Gimp. You don't need to be root to do
these things; in fact, you shouldn't be. If the plugin fails
to compile, well, be creative.
</p>
<p>
Once you have installed the plugin, how do you activate it?
The menu path is determined by the plugin itself, so to answer
this you need to either look at the documentation for the
plugin (if there is any), or launch the Plugin Description
dialog (from Xtns/Plugins Details) search the plug-in by
its name and look ot the <span class="guilabel">Tree view</span> tab.
If you still don't find, finally explore the menus or look
at the source code in the Register section -- whichever is easiest.
</p>
<p>
For more complex plugins, organized as a directory with
multiple files, there ought to be a file inside called either
INSTALL or README, with instructions. If not, the best advice
is to toss the plugin in the trash and spend your time on
something else: any code written with so little concern for
the user is likely to be frustrating in myriad ways.
</p>
<p>
Some plugins (specifically those based on the Gimp Plugin
Template) are designed to be installed in the main system Gimp
directory, rather than your home directory. For these, you
will need to be root to perform the final stage of
installation ("make install").
</p>
<p>
If you install in your personal plugin directory a plugin that
has the same name as one in the system plugin directory, only
one can be loaded, and it will be the one in your home
directory. You will receive messages telling you this each
time you start Gimp. This is probably a situation best
avoided.
</p>
</div>
<div class="simplesect" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a id="id3315943"></a>Windows</h4>
</div>
</div>
</div>
<p>
Windows is a much more problematic environment for building
software than Linux. Every decent Linux distribution comes
fully supplied with tools for compiling software, and they are
all very similar in the way they work, but Windows does not
come with such tools. It is possible to set up a good
software-building environment in Windows, but it requires
either a substantial amount of money or a substantial amount
of effort and knowledge.
</p>
<p>
Windows est un environnement plus problèmatique que Linux pour la construction
de logiciels. Toute distribution décente de Linux vient avec tous les outils
nécessaires à la compilation de logiciels, et ils ont tous un mode de fonctionnement
similaire, mais Windows n'offre pas de tels outils. Il est possible de configurer
un bon environnement de développement sous Windows, mais cela nécessite
une bonne quantité d'argent ou de connaissances et d'efforts.
</p>
<p>
What this means in relation to Gimp plugins is the following:
either you have an environment in which you can build
software, or you don't. If you don't, then your best hope is
to find a precompiled version of the plugin somewhere (or
persuade somebody to compile it for you), in
which case you simply need to put it into your personal plugin
directory. If you do have an environment in which you can
build software (which for present purposes means an
environment in which you can build Gimp), then you no doubt
already know quite a bit about these things, and just need
to follow the Linux instructions.
</p>
<p>
If you would like to set up a build environment, and are ready
for the heroism involved, you can find a reasonably recent
description of how to go about it in the Gimp Wiki, at <a href="http://wiki.gimp.org/gimp/HowToCompileGimp_2fMicrosoftWindows" target="_top">
HowToCompileGimp/MicrosoftWindows </a>. Since it is a
Wiki, anybody is free to edit it, so please keep it up to date
by adding advice based on your own experiences.
</p>
</div>
<div class="simplesect" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a id="id3315937"></a>Macintosh</h4>
</div>
</div>
</div>
<p>
We could use some material here.
</p>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="ch02s08s02.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="ch02s08.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="ch02s08s04.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">8.2. Using Plugins </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> 8.4. Writing Plugins</td>
</tr>
</table>
</div>
</body>
</html>
|
