1 |
=head1 NAME |
2 |
|
3 |
staticperl - perl, libc, 100 modules, all in one 500kb file |
4 |
|
5 |
=head1 SYNOPSIS |
6 |
|
7 |
staticperl help # print the embedded documentation |
8 |
staticperl fetch # fetch and unpack perl sources |
9 |
staticperl configure # fetch and then configure perl |
10 |
staticperl build # configure and then build perl |
11 |
staticperl install # build and then install perl |
12 |
staticperl clean # clean most intermediate files (restart at configure) |
13 |
staticperl distclean # delete everything installed by this script |
14 |
staticperl cpan # invoke CPAN shell |
15 |
staticperl instmod path... # install unpacked modules |
16 |
staticperl instcpan modulename... # install modules from CPAN |
17 |
staticperl mkbundle <bundle-args...> # see documentation |
18 |
staticperl mkperl <bundle-args...> # see documentation |
19 |
staticperl mkapp appname <bundle-args...> # see documentation |
20 |
|
21 |
Typical Examples: |
22 |
|
23 |
staticperl install # fetch, configure, build and install perl |
24 |
staticperl cpan # run interactive cpan shell |
25 |
staticperl mkperl -M '"Config_heavy.pl"' # build a perl that supports -V |
26 |
staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http |
27 |
# build a perl with the above modules linked in |
28 |
staticperl mkapp myapp --boot mainprog mymodules |
29 |
# build a binary "myapp" from mainprog and mymodules |
30 |
|
31 |
=head1 DESCRIPTION |
32 |
|
33 |
This script helps you to create single-file perl interpreters |
34 |
or applications, or embedding a perl interpreter in your |
35 |
applications. Single-file means that it is fully self-contained - no |
36 |
separate shared objects, no autoload fragments, no .pm or .pl files are |
37 |
needed. And when linking statically, you can create (or embed) a single |
38 |
file that contains perl interpreter, libc, all the modules you need, all |
39 |
the libraries you need and of course your actual program. |
40 |
|
41 |
With F<uClibc> and F<upx> on x86, you can create a single 500kb binary |
42 |
that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO, |
43 |
Coro and so on. Or any other choice of modules. |
44 |
|
45 |
To see how this turns out, you can try out smallperl and bigperl, two |
46 |
pre-built static and compressed perl binaries with many and even more |
47 |
modules: just follow the links at L<http://staticperl.schmorp.de/>. |
48 |
|
49 |
The created files do not need write access to the file system (like PAR |
50 |
does). In fact, since this script is in many ways similar to PAR::Packer, |
51 |
here are the differences: |
52 |
|
53 |
=over 4 |
54 |
|
55 |
=item * The generated executables are much smaller than PAR created ones. |
56 |
|
57 |
Shared objects and the perl binary contain a lot of extra info, while |
58 |
the static nature of F<staticperl> allows the linker to remove all |
59 |
functionality and meta-info not required by the final executable. Even |
60 |
extensions statically compiled into perl at build time will only be |
61 |
present in the final executable when needed. |
62 |
|
63 |
In addition, F<staticperl> can strip perl sources much more effectively |
64 |
than PAR. |
65 |
|
66 |
=item * The generated executables start much faster. |
67 |
|
68 |
There is no need to unpack files, or even to parse Zip archives (which is |
69 |
slow and memory-consuming business). |
70 |
|
71 |
=item * The generated executables don't need a writable filesystem. |
72 |
|
73 |
F<staticperl> loads all required files directly from memory. There is no |
74 |
need to unpack files into a temporary directory. |
75 |
|
76 |
=item * More control over included files, more burden. |
77 |
|
78 |
PAR tries to be maintenance and hassle-free - it tries to include more |
79 |
files than necessary to make sure everything works out of the box. It |
80 |
mostly succeeds at this, but he extra files (such as the unicode database) |
81 |
can take substantial amounts of memory and file size. |
82 |
|
83 |
With F<staticperl>, the burden is mostly with the developer - only direct |
84 |
compile-time dependencies and L<AutoLoader> are handled automatically. |
85 |
This means the modules to include often need to be tweaked manually. |
86 |
|
87 |
All this does not preclude more permissive modes to be implemented in |
88 |
the future, but right now, you have to resolve state hidden dependencies |
89 |
manually. |
90 |
|
91 |
=item * PAR works out of the box, F<staticperl> does not. |
92 |
|
93 |
Maintaining your own custom perl build can be a pain in the ass, and while |
94 |
F<staticperl> tries to make this easy, it still requires a custom perl |
95 |
build and possibly fiddling with some modules. PAR is likely to produce |
96 |
results faster. |
97 |
|
98 |
Ok, PAR never has worked for me out of the box, and for some people, |
99 |
F<staticperl> does work out of the box, as they don't count "fiddling with |
100 |
module use lists" against it, but nevertheless, F<staticperl> is certainly |
101 |
a bit more difficult to use. |
102 |
|
103 |
=back |
104 |
|
105 |
=head1 HOW DOES IT WORK? |
106 |
|
107 |
Simple: F<staticperl> downloads, compile and installs a perl version of |
108 |
your choice in F<~/.staticperl>. You can add extra modules either by |
109 |
letting F<staticperl> install them for you automatically, or by using CPAN |
110 |
and doing it interactively. This usually takes 5-10 minutes, depending on |
111 |
the speed of your computer and your internet connection. |
112 |
|
113 |
It is possible to do program development at this stage, too. |
114 |
|
115 |
Afterwards, you create a list of files and modules you want to include, |
116 |
and then either build a new perl binary (that acts just like a normal perl |
117 |
except everything is compiled in), or you create bundle files (basically C |
118 |
sources you can use to embed all files into your project). |
119 |
|
120 |
This step is very fast (a few seconds if PPI is not used for stripping, or |
121 |
the stripped files are in the cache), and can be tweaked and repeated as |
122 |
often as necessary. |
123 |
|
124 |
=head1 THE F<STATICPERL> SCRIPT |
125 |
|
126 |
This module installs a script called F<staticperl> into your perl |
127 |
binary directory. The script is fully self-contained, and can be |
128 |
used without perl (for example, in an uClibc chroot environment). In |
129 |
fact, it can be extracted from the C<App::Staticperl> distribution |
130 |
tarball as F<bin/staticperl>, without any installation. The |
131 |
newest (possibly alpha) version can also be downloaded from |
132 |
L<http://staticperl.schmorp.de/staticperl>. |
133 |
|
134 |
F<staticperl> interprets the first argument as a command to execute, |
135 |
optionally followed by any parameters. |
136 |
|
137 |
There are two command categories: the "phase 1" commands which deal with |
138 |
installing perl and perl modules, and the "phase 2" commands, which deal |
139 |
with creating binaries and bundle files. |
140 |
|
141 |
=head2 PHASE 1 COMMANDS: INSTALLING PERL |
142 |
|
143 |
The most important command is F<install>, which does basically |
144 |
everything. The default is to download and install perl 5.12.2 and a few |
145 |
modules required by F<staticperl> itself, but all this can (and should) be |
146 |
changed - see L<CONFIGURATION>, below. |
147 |
|
148 |
The command |
149 |
|
150 |
staticperl install |
151 |
|
152 |
is normally all you need: It installs the perl interpreter in |
153 |
F<~/.staticperl/perl>. It downloads, configures, builds and installs the |
154 |
perl interpreter if required. |
155 |
|
156 |
Most of the following F<staticperl> subcommands simply run one or more |
157 |
steps of this sequence. |
158 |
|
159 |
If it fails, then most commonly because the compiler options I selected |
160 |
are not supported by your compiler - either edit the F<staticperl> script |
161 |
yourself or create F<~/.staticperl> shell script where your set working |
162 |
C<PERL_CCFLAGS> etc. variables. |
163 |
|
164 |
To force recompilation or reinstallation, you need to run F<staticperl |
165 |
distclean> first. |
166 |
|
167 |
=over 4 |
168 |
|
169 |
=item F<staticperl version> |
170 |
|
171 |
Prints some info about the version of the F<staticperl> script you are using. |
172 |
|
173 |
=item F<staticperl fetch> |
174 |
|
175 |
Runs only the download and unpack phase, unless this has already happened. |
176 |
|
177 |
=item F<staticperl configure> |
178 |
|
179 |
Configures the unpacked perl sources, potentially after downloading them first. |
180 |
|
181 |
=item F<staticperl build> |
182 |
|
183 |
Builds the configured perl sources, potentially after automatically |
184 |
configuring them. |
185 |
|
186 |
=item F<staticperl install> |
187 |
|
188 |
Wipes the perl installation directory (usually F<~/.staticperl/perl>) and |
189 |
installs the perl distribution, potentially after building it first. |
190 |
|
191 |
=item F<staticperl cpan> [args...] |
192 |
|
193 |
Starts an interactive CPAN shell that you can use to install further |
194 |
modules. Installs the perl first if necessary, but apart from that, |
195 |
no magic is involved: you could just as well run it manually via |
196 |
F<~/.staticperl/perl/bin/cpan>. |
197 |
|
198 |
Any additional arguments are simply passed to the F<cpan> command. |
199 |
|
200 |
=item F<staticperl instcpan> module... |
201 |
|
202 |
Tries to install all the modules given and their dependencies, using CPAN. |
203 |
|
204 |
Example: |
205 |
|
206 |
staticperl instcpan EV AnyEvent::HTTPD Coro |
207 |
|
208 |
=item F<staticperl instsrc> directory... |
209 |
|
210 |
In the unlikely case that you have unpacked perl modules around and want |
211 |
to install from these instead of from CPAN, you can do this using this |
212 |
command by specifying all the directories with modules in them that you |
213 |
want to have built. |
214 |
|
215 |
=item F<staticperl clean> |
216 |
|
217 |
Deletes the perl source directory (and potentially cleans up other |
218 |
intermediate files). This can be used to clean up files only needed for |
219 |
building perl, without removing the installed perl interpreter. |
220 |
|
221 |
At the moment, it doesn't delete downloaded tarballs. |
222 |
|
223 |
The exact semantics of this command will probably change. |
224 |
|
225 |
=item F<staticperl distclean> |
226 |
|
227 |
This wipes your complete F<~/.staticperl> directory. Be careful with this, |
228 |
it nukes your perl download, perl sources, perl distribution and any |
229 |
installed modules. It is useful if you wish to start over "from scratch" |
230 |
or when you want to uninstall F<staticperl>. |
231 |
|
232 |
=back |
233 |
|
234 |
=head2 PHASE 2 COMMANDS: BUILDING PERL BUNDLES |
235 |
|
236 |
Building (linking) a new F<perl> binary is handled by a separate |
237 |
script. To make it easy to use F<staticperl> from a F<chroot>, the script |
238 |
is embedded into F<staticperl>, which will write it out and call for you |
239 |
with any arguments you pass: |
240 |
|
241 |
staticperl mkbundle mkbundle-args... |
242 |
|
243 |
In the oh so unlikely case of something not working here, you |
244 |
can run the script manually as well (by default it is written to |
245 |
F<~/.staticperl/mkbundle>). |
246 |
|
247 |
F<mkbundle> is a more conventional command and expect the argument |
248 |
syntax commonly used on UNIX clones. For example, this command builds |
249 |
a new F<perl> binary and includes F<Config.pm> (for F<perl -V>), |
250 |
F<AnyEvent::HTTPD>, F<URI> and a custom F<httpd> script (from F<eg/httpd> |
251 |
in this distribution): |
252 |
|
253 |
# first make sure we have perl and the required modules |
254 |
staticperl instcpan AnyEvent::HTTPD |
255 |
|
256 |
# now build the perl |
257 |
staticperl mkperl -M'"Config_heavy.pl"' -MAnyEvent::Impl::Perl \ |
258 |
-MAnyEvent::HTTPD -MURI::http \ |
259 |
--add 'eg/httpd httpd.pm' |
260 |
|
261 |
# finally, invoke it |
262 |
./perl -Mhttpd |
263 |
|
264 |
As you can see, things are not quite as trivial: the L<Config> module has |
265 |
a hidden dependency which is not even a perl module (F<Config_heavy.pl>), |
266 |
L<AnyEvent> needs at least one event loop backend that we have to |
267 |
specify manually (here L<AnyEvent::Impl::Perl>), and the F<URI> module |
268 |
(required by L<AnyEvent::HTTPD>) implements various URI schemes as extra |
269 |
modules - since L<AnyEvent::HTTPD> only needs C<http> URIs, we only need |
270 |
to include that module. I found out about these dependencies by carefully |
271 |
watching any error messages about missing modules... |
272 |
|
273 |
Instead of building a new perl binary, you can also build a standalone |
274 |
application: |
275 |
|
276 |
# build the app |
277 |
staticperl mkapp app --boot eg/httpd \ |
278 |
-MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI::http |
279 |
|
280 |
# run it |
281 |
./app |
282 |
|
283 |
=head3 OPTION PROCESSING |
284 |
|
285 |
All options can be given as arguments on the command line (typically |
286 |
using long (e.g. C<--verbose>) or short option (e.g. C<-v>) style). Since |
287 |
specifying a lot of modules can make the command line very cumbersome, |
288 |
you can put all long options into a "bundle specification file" (with or |
289 |
without C<--> prefix) and specify this bundle file instead. |
290 |
|
291 |
For example, the command given earlier could also look like this: |
292 |
|
293 |
staticperl mkperl httpd.bundle |
294 |
|
295 |
And all options could be in F<httpd.bundle>: |
296 |
|
297 |
use "Config_heavy.pl" |
298 |
use AnyEvent::Impl::Perl |
299 |
use AnyEvent::HTTPD |
300 |
use URI::http |
301 |
add eg/httpd httpd.pm |
302 |
|
303 |
All options that specify modules or files to be added are processed in the |
304 |
order given on the command line (that affects the C<--use> and C<--eval> |
305 |
options at the moment). |
306 |
|
307 |
=head3 PACKAGE SELECTION WORKFLOW |
308 |
|
309 |
F<staticperl mkbundle> has a number of options to control package |
310 |
selection. This section describes how they interact with each other. Also, |
311 |
since I am still a newbie w.r.t. these issues, maybe future versions of |
312 |
F<staticperl> will change this, so watch out :) |
313 |
|
314 |
The idiom "in order" means "in order that they are specified on the |
315 |
commandline". If you use a bundle specification file, then the options |
316 |
will be processed as if they were given in place of the bundle file name. |
317 |
|
318 |
=over 4 |
319 |
|
320 |
=item 1. apply all C<--use>, C<--eval>, C<--add>, C<--addbin> and |
321 |
C<--incglob> options, in order. |
322 |
|
323 |
In addition, C<--use> and C<--eval> dependencies will be added when the |
324 |
options are processed. |
325 |
|
326 |
=item 2. apply all C<--include> and C<--exclude> options, in order. |
327 |
|
328 |
All this step does is potentially reduce the number of files already |
329 |
selected or found in phase 1. |
330 |
|
331 |
=item 3. find all modules (== F<.pm> files), gather their static archives |
332 |
(F<.a>) and AutoLoader splitfiles (F<.ix> and F<.al> files), find any |
333 |
extra libraries they need for linking (F<extralibs.ld>) and optionally |
334 |
evaluate any F<.packlist> files. |
335 |
|
336 |
This step is required to link against XS extensions and also adds files |
337 |
required for L<AutoLoader> to do it's job. |
338 |
|
339 |
=back |
340 |
|
341 |
After this, all the files selected for bundling will be read and processed |
342 |
(stripped), the bundle files will be written, and optionally a new F<perl> |
343 |
or application binary will be linked. |
344 |
|
345 |
=head3 MKBUNDLE OPTIONS |
346 |
|
347 |
=over 4 |
348 |
|
349 |
=item --verbose | -v |
350 |
|
351 |
Increases the verbosity level by one (the default is C<1>). |
352 |
|
353 |
=item --quiet | -q |
354 |
|
355 |
Decreases the verbosity level by one. |
356 |
|
357 |
=item --strip none|pod|ppi |
358 |
|
359 |
Specify the stripping method applied to reduce the file of the perl |
360 |
sources included. |
361 |
|
362 |
The default is C<pod>, which uses the L<Pod::Strip> module to remove all |
363 |
pod documentation, which is very fast and reduces file size a lot. |
364 |
|
365 |
The C<ppi> method uses L<PPI> to parse and condense the perl sources. This |
366 |
saves a lot more than just L<Pod::Strip>, and is generally safer, |
367 |
but is also a lot slower (some files take almost a minute to strip - |
368 |
F<staticperl> maintains a cache of stripped files to speed up subsequent |
369 |
runs for this reason). Note that this method doesn't optimise for raw file |
370 |
size, but for best compression (that means that the uncompressed file size |
371 |
is a bit larger, but the files compress better, e.g. with F<upx>). |
372 |
|
373 |
Last not least, if you need accurate line numbers in error messages, |
374 |
or in the unlikely case where C<pod> is too slow, or some module gets |
375 |
mistreated, you can specify C<none> to not mangle included perl sources in |
376 |
any way. |
377 |
|
378 |
=item --perl |
379 |
|
380 |
After writing out the bundle files, try to link a new perl interpreter. It |
381 |
will be called F<perl> and will be left in the current working |
382 |
directory. The bundle files will be removed. |
383 |
|
384 |
This switch is automatically used when F<staticperl> is invoked with the |
385 |
C<mkperl> command (instead of C<mkbundle>): |
386 |
|
387 |
# build a new ./perl with only common::sense in it - very small :) |
388 |
staticperl mkperl -Mcommon::sense |
389 |
|
390 |
=item --app name |
391 |
|
392 |
After writing out the bundle files, try to link a new standalone |
393 |
program. It will be called C<name>, and the bundle files get removed after |
394 |
linking it. |
395 |
|
396 |
The difference to the (mutually exclusive) C<--perl> option is that the |
397 |
binary created by this option will not try to act as a perl interpreter - |
398 |
instead it will simply initialise the perl interpreter, clean it up and |
399 |
exit. |
400 |
|
401 |
This switch is automatically used when F<staticperl> is invoked with the |
402 |
C<mkapp> command (instead of C<mkbundle>): |
403 |
|
404 |
To let it do something useful you I<must> add some boot code, e.g. with |
405 |
the C<--boot> option. |
406 |
|
407 |
Example: create a standalone perl binary that will execute F<appfile> when |
408 |
it is started. |
409 |
|
410 |
staticperl mkbundle --app myexe --boot appfile |
411 |
|
412 |
=item --use module | -Mmodule |
413 |
|
414 |
Include the named module and all direct dependencies. This is done by |
415 |
C<require>'ing the module in a subprocess and tracing which other modules |
416 |
and files it actually loads. If the module uses L<AutoLoader>, then all |
417 |
splitfiles will be included as well. |
418 |
|
419 |
Example: include AnyEvent and AnyEvent::Impl::Perl. |
420 |
|
421 |
staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl |
422 |
|
423 |
Sometimes you want to load old-style "perl libraries" (F<.pl> files), or |
424 |
maybe other weirdly named files. To do that, you need to quote the name in |
425 |
single or double quotes. When given on the command line, you probably need |
426 |
to quote once more to avoid your shell interpreting it. Common cases that |
427 |
need this are F<Config_heavy.pl> and F<utf8_heavy.pl>. |
428 |
|
429 |
Example: include the required files for F<perl -V> to work in all its |
430 |
glory (F<Config.pm> is included automatically by this). |
431 |
|
432 |
# bourne shell |
433 |
staticperl mkbundle --use '"Config_heavy.pl"' |
434 |
|
435 |
# bundle specification file |
436 |
use "Config_heavy.pl" |
437 |
|
438 |
The C<-Mmodule> syntax is included as an alias that might be easier to |
439 |
remember than C<use>. Or maybe it confuses people. Time will tell. Or |
440 |
maybe not. Argh. |
441 |
|
442 |
=item --eval "perl code" | -e "perl code" |
443 |
|
444 |
Sometimes it is easier (or necessary) to specify dependencies using perl |
445 |
code, or maybe one of the modules you use need a special use statement. In |
446 |
that case, you can use C<eval> to execute some perl snippet or set some |
447 |
variables or whatever you need. All files C<require>'d or C<use>'d in the |
448 |
script are included in the final bundle. |
449 |
|
450 |
Keep in mind that F<mkbundle> will only C<require> the modules named |
451 |
by the C<--use> option, so do not expect the symbols from modules you |
452 |
C<--use>'d earlier on the command line to be available. |
453 |
|
454 |
Example: force L<AnyEvent> to detect a backend and therefore include it |
455 |
in the final bundle. |
456 |
|
457 |
staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect' |
458 |
|
459 |
# or like this |
460 |
staticperl mkbundle -MAnyEvent --eval 'use AnyEvent; AnyEvent::detect' |
461 |
|
462 |
Example: use a separate "bootstrap" script that C<use>'s lots of modules |
463 |
and include this in the final bundle, to be executed automatically. |
464 |
|
465 |
staticperl mkbundle --eval 'do "bootstrap"' --boot bootstrap |
466 |
|
467 |
=item --boot filename |
468 |
|
469 |
Include the given file in the bundle and arrange for it to be executed |
470 |
(using a C<require>) before anything else when the new perl is |
471 |
initialised. This can be used to modify C<@INC> or anything else before |
472 |
the perl interpreter executes scripts given on the command line (or via |
473 |
C<-e>). This works even in an embedded interpreter. |
474 |
|
475 |
=item --usepacklist |
476 |
|
477 |
Read F<.packlist> files for each distribution that happens to match a |
478 |
module name you specified. Sounds weird, and it is, so expect semantics to |
479 |
change somehow in the future. |
480 |
|
481 |
The idea is that most CPAN distributions have a F<.pm> file that matches |
482 |
the name of the distribution (which is rather reasonable after all). |
483 |
|
484 |
If this switch is enabled, then if any of the F<.pm> files that have been |
485 |
selected match an install distribution, then all F<.pm>, F<.pl>, F<.al> |
486 |
and F<.ix> files installed by this distribution are also included. |
487 |
|
488 |
For example, using this switch, when the L<URI> module is specified, then |
489 |
all L<URI> submodules that have been installed via the CPAN distribution |
490 |
are included as well, so you don't have to manually specify them. |
491 |
|
492 |
=item --incglob pattern |
493 |
|
494 |
This goes through all library directories and tries to match any F<.pm> |
495 |
and F<.pl> files against the extended glob pattern (see below). If a file |
496 |
matches, it is added. This switch will automatically detect L<AutoLoader> |
497 |
files and the required link libraries for XS modules, but it will I<not> |
498 |
scan the file for dependencies (at the moment). |
499 |
|
500 |
This is mainly useful to include "everything": |
501 |
|
502 |
--incglob '*' |
503 |
|
504 |
Or to include perl libraries, or trees of those, such as the unicode |
505 |
database files needed by many other modules: |
506 |
|
507 |
--incglob '/unicore/**.pl' |
508 |
|
509 |
=item --add file | --add "file alias" |
510 |
|
511 |
Adds the given (perl) file into the bundle (and optionally call it |
512 |
"alias"). This is useful to include any custom files into the bundle. |
513 |
|
514 |
Example: embed the file F<httpd> as F<httpd.pm> when creating the bundle. |
515 |
|
516 |
staticperl mkperl --add "httpd httpd.pm" |
517 |
|
518 |
It is also a great way to add any custom modules: |
519 |
|
520 |
# specification file |
521 |
add file1 myfiles/file1 |
522 |
add file2 myfiles/file2 |
523 |
add file3 myfiles/file3 |
524 |
|
525 |
=item --binadd file | --add "file alias" |
526 |
|
527 |
Just like C<--add>, except that it treats the file as binary and adds it |
528 |
without any processing. |
529 |
|
530 |
You should probably add a C</> prefix to avoid clashing with embedded |
531 |
perl files (whose paths do not start with C</>), and/or use a special |
532 |
directory, such as C</res/name>. |
533 |
|
534 |
You can later get a copy of these files by calling C<staticperl::find |
535 |
"alias">. |
536 |
|
537 |
=item --include pattern | -i pattern | --exclude pattern | -x pattern |
538 |
|
539 |
These two options define an include/exclude filter that is used after all |
540 |
files selected by the other options have been found. Each include/exclude |
541 |
is applied to all files found so far - an include makes sure that the |
542 |
given files will be part of the resulting file set, an exclude will |
543 |
exclude files. The patterns are "extended glob patterns" (see below). |
544 |
|
545 |
For example, to include everything, except C<Devel> modules, but still |
546 |
include F<Devel::PPPort>, you could use this: |
547 |
|
548 |
--incglob '*' -i '/Devel/PPPort.pm' -x '/Devel/**' |
549 |
|
550 |
=item --static |
551 |
|
552 |
When C<--perl> is also given, link statically instead of dynamically. The |
553 |
default is to link the new perl interpreter fully dynamic (that means all |
554 |
perl modules are linked statically, but all external libraries are still |
555 |
referenced dynamically). |
556 |
|
557 |
Keep in mind that Solaris doesn't support static linking at all, and |
558 |
systems based on GNU libc don't really support it in a usable fashion |
559 |
either. Try uClibc if you want to create fully statically linked |
560 |
executables, or try the C<--staticlibs> option to link only some libraries |
561 |
statically. |
562 |
|
563 |
=item --staticlib libname |
564 |
|
565 |
When not linking fully statically, this option allows you to link specific |
566 |
libraries statically. What it does is simply replace all occurances of |
567 |
C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic> |
568 |
option. |
569 |
|
570 |
This will have no effect unless the library is actually linked against, |
571 |
specifically, C<--staticlib> will not link against the named library |
572 |
unless it would be linked against anyway. |
573 |
|
574 |
Example: link libcrypt statically into the binary. |
575 |
|
576 |
staticperl mkperl -MIO::AIO --staticlib crypt |
577 |
|
578 |
# ldopts might nwo contain: |
579 |
# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread |
580 |
|
581 |
=item any other argument |
582 |
|
583 |
Any other argument is interpreted as a bundle specification file, which |
584 |
supports most long options (without extra quoting), one option per line. |
585 |
|
586 |
=back |
587 |
|
588 |
=head3 EXTENDED GLOB PATTERNS |
589 |
|
590 |
Some options of F<staticperl mkbundle> expect an I<extended glob |
591 |
pattern>. This is neither a normal shell glob nor a regex, but something |
592 |
in between. The idea has been copied from rsync, and there are the current |
593 |
matching rules: |
594 |
|
595 |
=over 4 |
596 |
|
597 |
=item Patterns starting with F</> will be a anchored at the root of the library tree. |
598 |
|
599 |
That is, F</unicore> will match the F<unicore> directory in C<@INC>, but |
600 |
nothing inside, and neither any other file or directory called F<unicore> |
601 |
anywhere else in the hierarchy. |
602 |
|
603 |
=item Patterns not starting with F</> will be anchored at the end of the path. |
604 |
|
605 |
That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the |
606 |
hierarchy, but not any directories of the same name. |
607 |
|
608 |
=item A F<*> matches any single component. |
609 |
|
610 |
That is, F</unicore/*.pl> would match all F<.pl> files directly inside |
611 |
C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*> |
612 |
will not match slashes. |
613 |
|
614 |
=item A F<**> matches anything. |
615 |
|
616 |
That is, F</unicore/**.pl> would match all F<.pl> files under F</unicore>, |
617 |
no matter how deeply nested they are inside subdirectories. |
618 |
|
619 |
=item A F<?> matches a single character within a component. |
620 |
|
621 |
That is, F</Encode/??.pm> matches F</Encode/JP.pm>, but not the |
622 |
hypothetical F</Encode/J/.pm>, as F<?> does not match F</>. |
623 |
|
624 |
=back |
625 |
|
626 |
=head2 F<STATICPERL> CONFIGURATION AND HOOKS |
627 |
|
628 |
During (each) startup, F<staticperl> tries to source some shell files to |
629 |
allow you to fine-tune/override configuration settings. |
630 |
|
631 |
In them you can override shell variables, or define shell functions |
632 |
("hooks") to be called at specific phases during installation. For |
633 |
example, you could define a C<postinstall> hook to install additional |
634 |
modules from CPAN each time you start from scratch. |
635 |
|
636 |
If the env variable C<$STATICPERLRC> is set, then F<staticperl> will try |
637 |
to source the file named with it only. Otherwise, it tries the following |
638 |
shell files in order: |
639 |
|
640 |
/etc/staticperlrc |
641 |
~/.staticperlrc |
642 |
$STATICPERL/rc |
643 |
|
644 |
Note that the last file is erased during F<staticperl distclean>, so |
645 |
generally should not be used. |
646 |
|
647 |
=head3 CONFIGURATION VARIABLES |
648 |
|
649 |
=head4 Variables you I<should> override |
650 |
|
651 |
=over 4 |
652 |
|
653 |
=item C<EMAIL> |
654 |
|
655 |
The e-mail address of the person who built this binary. Has no good |
656 |
default, so should be specified by you. |
657 |
|
658 |
=item C<CPAN> |
659 |
|
660 |
The URL of the CPAN mirror to use (e.g. L<http://mirror.netcologne.de/cpan/>). |
661 |
|
662 |
=item C<EXTRA_MODULES> |
663 |
|
664 |
Additional modules installed during F<staticperl install>. Here you can |
665 |
set which modules you want have to installed from CPAN. |
666 |
|
667 |
Example: I really really need EV, AnyEvent, Coro and AnyEvent::AIO. |
668 |
|
669 |
EXTRA_MODULES="EV AnyEvent Coro AnyEvent::AIO" |
670 |
|
671 |
Note that you can also use a C<postinstall> hook to achieve this, and |
672 |
more. |
673 |
|
674 |
=back |
675 |
|
676 |
=head4 Variables you might I<want> to override |
677 |
|
678 |
=over 4 |
679 |
|
680 |
=item C<STATICPERL> |
681 |
|
682 |
The directory where staticperl stores all its files |
683 |
(default: F<~/.staticperl>). |
684 |
|
685 |
=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ... |
686 |
|
687 |
Usually set to C<1> to make modules "less inquisitive" during their |
688 |
installation, you can set any environment variable you want - some modules |
689 |
(such as L<Coro> or L<EV>) use environment variables for further tweaking. |
690 |
|
691 |
=item C<PERL_VERSION> |
692 |
|
693 |
The perl version to install - default is currently C<5.12.2>, but C<5.8.9> |
694 |
is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is |
695 |
about as big as 5.12.2). |
696 |
|
697 |
=item C<PERL_PREFIX> |
698 |
|
699 |
The prefix where perl gets installed (default: F<$STATICPERL/perl>), |
700 |
i.e. where the F<bin> and F<lib> subdirectories will end up. |
701 |
|
702 |
=item C<PERL_CONFIGURE> |
703 |
|
704 |
Additional Configure options - these are simply passed to the perl |
705 |
Configure script. For example, if you wanted to enable dynamic loading, |
706 |
you could pass C<-Dusedl>. To enable ithreads (Why would you want that |
707 |
insanity? Don't! Use L<forks> instead!) you would pass C<-Duseithreads> |
708 |
and so on. |
709 |
|
710 |
More commonly, you would either activate 64 bit integer support |
711 |
(C<-Duse64bitint>), or disable large files support (-Uuselargefiles), to |
712 |
reduce filesize further. |
713 |
|
714 |
=item C<PERL_CC>, C<PERL_CCFLAGS>, C<PERL_OPTIMIZE>, C<PERL_LDFLAGS>, C<PERL_LIBS> |
715 |
|
716 |
These flags are passed to perl's F<Configure> script, and are generally |
717 |
optimised for small size (at the cost of performance). Since they also |
718 |
contain subtle workarounds around various build issues, changing these |
719 |
usually requires understanding their default values - best look at |
720 |
the top of the F<staticperl> script for more info on these, and use a |
721 |
F<~/.staticperlrc> to override them. |
722 |
|
723 |
Most of the variables override (or modify) the corresponding F<Configure> |
724 |
variable, except C<PERL_CCFLAGS>, which gets appended. |
725 |
|
726 |
=back |
727 |
|
728 |
=head4 Variables you probably I<do not want> to override |
729 |
|
730 |
=over 4 |
731 |
|
732 |
=item C<MAKE> |
733 |
|
734 |
The make command to use - default is C<make>. |
735 |
|
736 |
=item C<MKBUNDLE> |
737 |
|
738 |
Where F<staticperl> writes the C<mkbundle> command to |
739 |
(default: F<$STATICPERL/mkbundle>). |
740 |
|
741 |
=item C<STATICPERL_MODULES> |
742 |
|
743 |
Additional modules needed by C<mkbundle> - should therefore not be changed |
744 |
unless you know what you are doing. |
745 |
|
746 |
=back |
747 |
|
748 |
=head3 OVERRIDABLE HOOKS |
749 |
|
750 |
In addition to environment variables, it is possible to provide some |
751 |
shell functions that are called at specific times. To provide your own |
752 |
commands, just define the corresponding function. |
753 |
|
754 |
Example: install extra modules from CPAN and from some directories |
755 |
at F<staticperl install> time. |
756 |
|
757 |
postinstall() { |
758 |
rm -rf lib/threads* # weg mit Schaden |
759 |
instcpan IO::AIO EV |
760 |
instsrc ~/src/AnyEvent |
761 |
instsrc ~/src/XML-Sablotron-1.0100001 |
762 |
instcpan Anyevent::AIO AnyEvent::HTTPD |
763 |
} |
764 |
|
765 |
=over 4 |
766 |
|
767 |
=item preconfigure |
768 |
|
769 |
Called just before running F<./Configur> in the perl source |
770 |
directory. Current working directory is the perl source directory. |
771 |
|
772 |
This can be used to set any C<PERL_xxx> variables, which might be costly |
773 |
to compute. |
774 |
|
775 |
=item postconfigure |
776 |
|
777 |
Called after configuring, but before building perl. Current working |
778 |
directory is the perl source directory. |
779 |
|
780 |
Could be used to tailor/patch config.sh (followed by F<sh Configure -S>) |
781 |
or do any other modifications. |
782 |
|
783 |
=item postbuild |
784 |
|
785 |
Called after building, but before installing perl. Current working |
786 |
directory is the perl source directory. |
787 |
|
788 |
I have no clue what this could be used for - tell me. |
789 |
|
790 |
=item postinstall |
791 |
|
792 |
Called after perl and any extra modules have been installed in C<$PREFIX>, |
793 |
but before setting the "installation O.K." flag. |
794 |
|
795 |
The current working directory is C<$PREFIX>, but maybe you should not rely |
796 |
on that. |
797 |
|
798 |
This hook is most useful to customise the installation, by deleting files, |
799 |
or installing extra modules using the C<instcpan> or C<instsrc> functions. |
800 |
|
801 |
The script must return with a zero exit status, or the installation will |
802 |
fail. |
803 |
|
804 |
=back |
805 |
|
806 |
=head1 ANATOMY OF A BUNDLE |
807 |
|
808 |
When not building a new perl binary, C<mkbundle> will leave a number of |
809 |
files in the current working directory, which can be used to embed a perl |
810 |
interpreter in your program. |
811 |
|
812 |
Intimate knowledge of L<perlembed> and preferably some experience with |
813 |
embedding perl is highly recommended. |
814 |
|
815 |
C<mkperl> (or the C<--perl> option) basically does this to link the new |
816 |
interpreter (it also adds a main program to F<bundle.>): |
817 |
|
818 |
$Config{cc} $(cat bundle.ccopts) -o perl bundle.c $(cat bundle.ldopts) |
819 |
|
820 |
=over 4 |
821 |
|
822 |
=item bundle.h |
823 |
|
824 |
A header file that contains the prototypes of the few symbols "exported" |
825 |
by bundle.c, and also exposes the perl headers to the application. |
826 |
|
827 |
=over 4 |
828 |
|
829 |
=item staticperl_init () |
830 |
|
831 |
Initialises the perl interpreter. You can use the normal perl functions |
832 |
after calling this function, for example, to define extra functions or |
833 |
to load a .pm file that contains some initialisation code, or the main |
834 |
program function: |
835 |
|
836 |
XS (xsfunction) |
837 |
{ |
838 |
dXSARGS; |
839 |
|
840 |
// now we have items, ST(i) etc. |
841 |
} |
842 |
|
843 |
static void |
844 |
run_myapp(void) |
845 |
{ |
846 |
staticperl_init (); |
847 |
newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$"); |
848 |
eval_pv ("require myapp::main", 1); // executes "myapp/main.pm" |
849 |
} |
850 |
|
851 |
=item staticperl_xs_init (pTHX) |
852 |
|
853 |
Sometimes you need direct control over C<perl_parse> and C<perl_run>, in |
854 |
which case you do not want to use C<staticperl_init> but call them on your |
855 |
own. |
856 |
|
857 |
Then you need this function - either pass it directly as the C<xs_init> |
858 |
function to C<perl_parse>, or call it from your own C<xs_init> function. |
859 |
|
860 |
=item staticperl_cleanup () |
861 |
|
862 |
In the unlikely case that you want to destroy the perl interpreter, here |
863 |
is the corresponding function. |
864 |
|
865 |
=item PerlInterpreter *staticperl |
866 |
|
867 |
The perl interpreter pointer used by staticperl. Not normally so useful, |
868 |
but there it is. |
869 |
|
870 |
=back |
871 |
|
872 |
=item bundle.ccopts |
873 |
|
874 |
Contains the compiler options required to compile at least F<bundle.c> and |
875 |
any file that includes F<bundle.h> - you should probably use it in your |
876 |
C<CFLAGS>. |
877 |
|
878 |
=item bundle.ldopts |
879 |
|
880 |
The linker options needed to link the final program. |
881 |
|
882 |
=back |
883 |
|
884 |
=head1 RUNTIME FUNCTIONALITY |
885 |
|
886 |
Binaries created with C<mkbundle>/C<mkperl> contain extra functions, which |
887 |
are required to access the bundled perl sources, but might be useful for |
888 |
other purposes. |
889 |
|
890 |
In addition, for the embedded loading of perl files to work, F<staticperl> |
891 |
overrides the C<@INC> array. |
892 |
|
893 |
=over 4 |
894 |
|
895 |
=item $file = staticperl::find $path |
896 |
|
897 |
Returns the data associated with the given C<$path> |
898 |
(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>), which is basically |
899 |
the UNIX path relative to the perl library directory. |
900 |
|
901 |
Returns C<undef> if the file isn't embedded. |
902 |
|
903 |
=item @paths = staticperl::list |
904 |
|
905 |
Returns the list of all paths embedded in this binary. |
906 |
|
907 |
=back |
908 |
|
909 |
=head1 FULLY STATIC BINARIES - BUILDROOT |
910 |
|
911 |
To make truly static (Linux-) libraries, you might want to have a look at |
912 |
buildroot (L<http://buildroot.uclibc.org/>). |
913 |
|
914 |
Buildroot is primarily meant to set up a cross-compile environment (which |
915 |
is not so useful as perl doesn't quite like cross compiles), but it can also compile |
916 |
a chroot environment where you can use F<staticperl>. |
917 |
|
918 |
To do so, download buildroot, and enable "Build options => development |
919 |
files in target filesystem" and optionally "Build options => gcc |
920 |
optimization level (optimize for size)". At the time of writing, I had |
921 |
good experiences with GCC 4.4.x but not GCC 4.5. |
922 |
|
923 |
To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections |
924 |
-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386> |
925 |
doesn't decrease codesize much, but it makes the file much more |
926 |
compressible. |
927 |
|
928 |
If you don't need Coro or threads, you can go with "linuxthreads.old" (or |
929 |
no thread support). For Coro, it is highly recommended to switch to a |
930 |
uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201 |
931 |
snapshot) and enable NPTL, otherwise Coro needs to be configured with the |
932 |
ultra-slow pthreads backend to work around linuxthreads bugs (it also uses |
933 |
twice the address space needed for stacks). |
934 |
|
935 |
If you use C<linuxthreads.old>, then you should also be aware that |
936 |
uClibc shares C<errno> between all threads when statically linking. See |
937 |
L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a |
938 |
workaround (And L<https://bugs.uclibc.org/2089> for discussion). |
939 |
|
940 |
C<ccache> support is also recommended, especially if you want |
941 |
to play around with buildroot options. Enabling the C<miniperl> |
942 |
package will probably enable all options required for a successful |
943 |
perl build. F<staticperl> itself additionally needs either C<wget> |
944 |
(recommended, for CPAN) or C<curl>. |
945 |
|
946 |
As for shells, busybox should provide all that is needed, but the default |
947 |
busybox configuration doesn't include F<comm> which is needed by perl - |
948 |
either make a custom busybox config, or compile coreutils. |
949 |
|
950 |
For the latter route, you might find that bash has some bugs that keep |
951 |
it from working properly in a chroot - either use dash (and link it to |
952 |
F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's |
953 |
built-in ash shell. |
954 |
|
955 |
Finally, you need F</dev/null> inside the chroot for many scripts to work |
956 |
- F<cp /dev/null output/target/dev> or bind-mounting your F</dev> will |
957 |
both provide this. |
958 |
|
959 |
After you have compiled and set up your buildroot target, you can copy |
960 |
F<staticperl> from the C<App::Staticperl> distribution or from your |
961 |
perl f<bin> directory (if you installed it) into the F<output/target> |
962 |
filesystem, chroot inside and run it. |
963 |
|
964 |
=head1 RECIPES / SPECIFIC MODULES |
965 |
|
966 |
This section contains some common(?) recipes and information about |
967 |
problems with some common modules or perl constructs that require extra |
968 |
files to be included. |
969 |
|
970 |
=head2 MODULES |
971 |
|
972 |
=over 4 |
973 |
|
974 |
=item utf8 |
975 |
|
976 |
Some functionality in the utf8 module, such as swash handling (used |
977 |
for unicode character ranges in regexes) is implemented in the |
978 |
C<"utf8_heavy.pl"> library: |
979 |
|
980 |
-M'"utf8_heavy.pl"' |
981 |
|
982 |
Many Unicode properties in turn are defined in separate modules, |
983 |
such as C<"unicore/Heavy.pl"> and more specific data tables such as |
984 |
C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables |
985 |
are big (7MB uncompressed, although F<staticperl> contains special |
986 |
handling for those files), so including them on demand by your application |
987 |
only might pay off. |
988 |
|
989 |
To simply include the whole unicode database, use: |
990 |
|
991 |
--incglob '/unicore/*.pl' |
992 |
|
993 |
=item AnyEvent |
994 |
|
995 |
AnyEvent needs a backend implementation that it will load in a delayed |
996 |
fashion. The L<AnyEvent::Impl::Perl> backend is the default choice |
997 |
for AnyEvent if it can't find anything else, and is usually a safe |
998 |
fallback. If you plan to use e.g. L<EV> (L<POE>...), then you need to |
999 |
include the L<AnyEvent::Impl::EV> (L<AnyEvent::Impl::POE>...) backend as |
1000 |
well. |
1001 |
|
1002 |
If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn |
1003 |
functions), you also need to include C<"AnyEvent/Util/idna.pl"> and |
1004 |
C<"AnyEvent/Util/uts46data.pl">. |
1005 |
|
1006 |
Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include |
1007 |
everything. |
1008 |
|
1009 |
=item Carp |
1010 |
|
1011 |
Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of |
1012 |
perl 5.12.2 (maybe earlier), this dependency no longer exists. |
1013 |
|
1014 |
=item Config |
1015 |
|
1016 |
The F<perl -V> switch (as well as many modules) needs L<Config>, which in |
1017 |
turn might need L<"Config_heavy.pl">. Including the latter gives you |
1018 |
both. |
1019 |
|
1020 |
=item Term::ReadLine::Perl |
1021 |
|
1022 |
Also needs L<Term::ReadLine::readline>, or C<--usepacklist>. |
1023 |
|
1024 |
=item URI |
1025 |
|
1026 |
URI implements schemes as separate modules - the generic URL scheme is |
1027 |
implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If |
1028 |
you need to use any of these schemes, you should include these manually, |
1029 |
or use C<--usepacklist>. |
1030 |
|
1031 |
=back |
1032 |
|
1033 |
=head2 RECIPES |
1034 |
|
1035 |
=over 4 |
1036 |
|
1037 |
=item Linking everything in |
1038 |
|
1039 |
To link just about everything installed in the perl library into a new |
1040 |
perl, try this: |
1041 |
|
1042 |
staticperl mkperl --strip ppi --incglob '*' |
1043 |
|
1044 |
=item Getting rid of netdb function |
1045 |
|
1046 |
The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent> |
1047 |
and so on) that few applications use. You can avoid compiling them in by |
1048 |
putting the following fragment into a C<preconfigure> hook: |
1049 |
|
1050 |
preconfigure() { |
1051 |
for sym in \ |
1052 |
d_getgrnam_r d_endgrent d_endgrent_r d_endhent \ |
1053 |
d_endhostent_r d_endnent d_endnetent_r d_endpent \ |
1054 |
d_endprotoent_r d_endpwent d_endpwent_r d_endsent \ |
1055 |
d_endservent_r d_getgrent d_getgrent_r d_getgrgid_r \ |
1056 |
d_getgrnam_r d_gethbyaddr d_gethent d_getsbyport \ |
1057 |
d_gethostbyaddr_r d_gethostbyname_r d_gethostent_r \ |
1058 |
d_getlogin_r d_getnbyaddr d_getnbyname d_getnent \ |
1059 |
d_getnetbyaddr_r d_getnetbyname_r d_getnetent_r \ |
1060 |
d_getpent d_getpbyname d_getpbynumber d_getprotobyname_r \ |
1061 |
d_getprotobynumber_r d_getprotoent_r d_getpwent \ |
1062 |
d_getpwent_r d_getpwnam_r d_getpwuid_r d_getsent \ |
1063 |
d_getservbyname_r d_getservbyport_r d_getservent_r \ |
1064 |
d_getspnam_r d_getsbyname |
1065 |
# d_gethbyname |
1066 |
do |
1067 |
PERL_CONFIGURE="$PERL_CONFIGURE -U$sym" |
1068 |
done |
1069 |
} |
1070 |
|
1071 |
This mostly gains space when linking staticaly, as the functions will |
1072 |
likely not be linked in. The gain for dynamically-linked binaries is |
1073 |
smaller. |
1074 |
|
1075 |
Also, this leaves C<gethostbyname> in - not only is it actually used |
1076 |
often, the L<Socket> module also exposes it, so leaving it out usually |
1077 |
gains little. Why Socket exposes a C function that is in the core already |
1078 |
is anybody's guess. |
1079 |
|
1080 |
=back |
1081 |
|
1082 |
=head1 AUTHOR |
1083 |
|
1084 |
Marc Lehmann <schmorp@schmorp.de> |
1085 |
http://software.schmorp.de/pkg/staticperl.html |