… | |
… | |
14 | staticperl cpan # invoke CPAN shell |
14 | staticperl cpan # invoke CPAN shell |
15 | staticperl instmod path... # install unpacked modules |
15 | staticperl instmod path... # install unpacked modules |
16 | staticperl instcpan modulename... # install modules from CPAN |
16 | staticperl instcpan modulename... # install modules from CPAN |
17 | staticperl mkbundle <bundle-args...> # see documentation |
17 | staticperl mkbundle <bundle-args...> # see documentation |
18 | staticperl mkperl <bundle-args...> # see documentation |
18 | staticperl mkperl <bundle-args...> # see documentation |
|
|
19 | staticperl mkapp appname <bundle-args...> # see documentation |
19 | |
20 | |
20 | Typical Examples: |
21 | Typical Examples: |
21 | |
22 | |
22 | staticperl install # fetch, configure, build and install perl |
23 | staticperl install # fetch, configure, build and install perl |
23 | staticperl cpan # run interactive cpan shell |
24 | staticperl cpan # run interactive cpan shell |
24 | staticperl mkperl -M '"Config_heavy.pl"' # build a perl that supports -V |
25 | staticperl mkperl -M '"Config_heavy.pl"' # build a perl that supports -V |
25 | staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http |
26 | staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http |
26 | # build a perl with the above modules linked in |
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 |
27 | |
30 | |
28 | =head1 DESCRIPTION |
31 | =head1 DESCRIPTION |
29 | |
32 | |
30 | This script helps you creating single-file perl interpreters, or embedding |
33 | This script helps you creating single-file perl interpreters, or embedding |
31 | a perl interpreter in your applications. Single-file means that it is |
34 | a perl interpreter in your applications. Single-file means that it is |
… | |
… | |
81 | Maintaining your own custom perl build can be a pain in the ass, and while |
84 | Maintaining your own custom perl build can be a pain in the ass, and while |
82 | F<staticperl> tries to make this easy, it still requires a custom perl |
85 | F<staticperl> tries to make this easy, it still requires a custom perl |
83 | build and possibly fiddling with some modules. PAR is likely to produce |
86 | build and possibly fiddling with some modules. PAR is likely to produce |
84 | results faster. |
87 | results faster. |
85 | |
88 | |
|
|
89 | Ok, PAR never has worked for me out of the box, and for some people, |
|
|
90 | F<staticperl> does work out of the box, as they don't count "fiddling with |
|
|
91 | module use lists" against it, but nevertheless, F<staticperl> is certainly |
|
|
92 | a bit more difficult to use. |
|
|
93 | |
86 | =back |
94 | =back |
87 | |
95 | |
88 | =head1 HOW DOES IT WORK? |
96 | =head1 HOW DOES IT WORK? |
89 | |
97 | |
90 | Simple: F<staticperl> downloads, compile and installs a perl version of |
98 | Simple: F<staticperl> downloads, compile and installs a perl version of |
… | |
… | |
184 | command by specifying all the directories with modules in them that you |
192 | command by specifying all the directories with modules in them that you |
185 | want to have built. |
193 | want to have built. |
186 | |
194 | |
187 | =item F<staticperl clean> |
195 | =item F<staticperl clean> |
188 | |
196 | |
189 | Runs F<make distclean> in the perl source directory (and potentially |
197 | Deletes the perl source directory (and potentially cleans up other |
190 | cleans up other intermediate files). This can be used to clean up |
198 | intermediate files). This can be used to clean up files only needed for |
191 | intermediate files without removing the installed perl interpreter. |
199 | building perl, without removing the installed perl interpreter, or to |
|
|
200 | force a re-build from scratch. |
|
|
201 | |
|
|
202 | At the moment, it doesn't delete downloaded tarballs. |
192 | |
203 | |
193 | =item F<staticperl distclean> |
204 | =item F<staticperl distclean> |
194 | |
205 | |
195 | This wipes your complete F<~/.staticperl> directory. Be careful with this, |
206 | This wipes your complete F<~/.staticperl> directory. Be careful with this, |
196 | it nukes your perl download, perl sources, perl distribution and any |
207 | it nukes your perl download, perl sources, perl distribution and any |
… | |
… | |
236 | (required by L<AnyEvent::HTTPD>) implements various URI schemes as extra |
247 | (required by L<AnyEvent::HTTPD>) implements various URI schemes as extra |
237 | modules - since L<AnyEvent::HTTPD> only needs C<http> URIs, we only need |
248 | modules - since L<AnyEvent::HTTPD> only needs C<http> URIs, we only need |
238 | to include that module. I found out about these dependencies by carefully |
249 | to include that module. I found out about these dependencies by carefully |
239 | watching any error messages about missing modules... |
250 | watching any error messages about missing modules... |
240 | |
251 | |
|
|
252 | Instead of building a new perl binary, you can also build a standalone |
|
|
253 | application: |
|
|
254 | |
|
|
255 | # build the app |
|
|
256 | staticperl mkapp app --boot eg/httpd \ |
|
|
257 | -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI::http |
|
|
258 | |
|
|
259 | # run it |
|
|
260 | ./app |
|
|
261 | |
241 | =head3 OPTION PROCESSING |
262 | =head3 OPTION PROCESSING |
242 | |
263 | |
243 | All options can be given as arguments on the command line (typically |
264 | All options can be given as arguments on the command line (typically |
244 | using long (e.g. C<--verbose>) or short option (e.g. C<-v>) style). Since |
265 | using long (e.g. C<--verbose>) or short option (e.g. C<-v>) style). Since |
245 | specifying a lot of modules can make the command line very cumbersome, |
266 | specifying a lot of modules can make the command line very cumbersome, |
… | |
… | |
304 | C<mkperl> command (instead of C<mkbundle>): |
325 | C<mkperl> command (instead of C<mkbundle>): |
305 | |
326 | |
306 | # build a new ./perl with only common::sense in it - very small :) |
327 | # build a new ./perl with only common::sense in it - very small :) |
307 | staticperl mkperl -Mcommon::sense |
328 | staticperl mkperl -Mcommon::sense |
308 | |
329 | |
|
|
330 | =item --app name |
|
|
331 | |
|
|
332 | After writing out the bundle files, try to link a new standalone |
|
|
333 | program. It will be called C<name>, and the bundle files get removed after |
|
|
334 | linking it. |
|
|
335 | |
|
|
336 | The difference to the (mutually exclusive) C<--perl> option is that the |
|
|
337 | binary created by this option will not try to act as a perl interpreter - |
|
|
338 | instead it will simply initialise the perl interpreter, clean it up and |
|
|
339 | exit. |
|
|
340 | |
|
|
341 | This switch is automatically used when F<staticperl> is invoked with the |
|
|
342 | C<mkapp> command (instead of C<mkbundle>): |
|
|
343 | |
|
|
344 | To let it do something useful you I<must> add some boot code, e.g. with |
|
|
345 | the C<--boot> option. |
|
|
346 | |
|
|
347 | Example: create a standalone perl binary that will execute F<appfile> when |
|
|
348 | it is started. |
|
|
349 | |
|
|
350 | staticperl mkbundle --app myexe --boot appfile |
|
|
351 | |
309 | =item --use module | -Mmodule |
352 | =item --use module | -Mmodule |
310 | |
353 | |
311 | Include the named module and all direct dependencies. This is done by |
354 | Include the named module and all direct dependencies. This is done by |
312 | C<require>'ing the module in a subprocess and tracing which other modules |
355 | C<require>'ing the module in a subprocess and tracing which other modules |
313 | and files it actually loads. If the module uses L<AutoLoader>, then all |
356 | and files it actually loads. If the module uses L<AutoLoader>, then all |
… | |
… | |
383 | # specification file |
426 | # specification file |
384 | add file1 myfiles/file1 |
427 | add file1 myfiles/file1 |
385 | add file2 myfiles/file2 |
428 | add file2 myfiles/file2 |
386 | add file3 myfiles/file3 |
429 | add file3 myfiles/file3 |
387 | |
430 | |
|
|
431 | =item --binadd "file" | --add "file alias" |
|
|
432 | |
|
|
433 | Just like C<--add>, except that it treats the file as binary and adds it |
|
|
434 | without any processing. |
|
|
435 | |
|
|
436 | You should probably add a C</> prefix to avoid clashing with embedded |
|
|
437 | perl files (whose paths do not start with C</>), and/or use a special |
|
|
438 | directory, such as C</res/name>. |
|
|
439 | |
|
|
440 | You can later get a copy of these files by calling C<staticperl::find |
|
|
441 | "alias">. |
|
|
442 | |
388 | =item --static |
443 | =item --static |
389 | |
444 | |
390 | When C<--perl> is also given, link statically instead of dynamically. The |
445 | When C<--perl> is also given, link statically instead of dynamically. The |
391 | default is to link the new perl interpreter fully dynamic (that means all |
446 | default is to link the new perl interpreter fully dynamic (that means all |
392 | perl modules are linked statically, but all external libraries are still |
447 | perl modules are linked statically, but all external libraries are still |
… | |
… | |
429 | =item C<EMAIL> |
484 | =item C<EMAIL> |
430 | |
485 | |
431 | The e-mail address of the person who built this binary. Has no good |
486 | The e-mail address of the person who built this binary. Has no good |
432 | default, so should be specified by you. |
487 | default, so should be specified by you. |
433 | |
488 | |
|
|
489 | =item C<CPAN> |
|
|
490 | |
|
|
491 | The URL of the CPAN mirror to use (e.g. L<http://mirror.netcologne.de/cpan/>). |
|
|
492 | |
|
|
493 | =item C<EXTRA_MODULES> |
|
|
494 | |
|
|
495 | Additional modules installed during F<staticperl install>. Here you can |
|
|
496 | set which modules you want have to installed from CPAN. |
|
|
497 | |
|
|
498 | Example: I really really need EV, AnyEvent, Coro and AnyEvent::AIO. |
|
|
499 | |
|
|
500 | EXTRA_MODULES="EV AnyEvent Coro AnyEvent::AIO" |
|
|
501 | |
|
|
502 | Note that you can also use a C<postinstall> hook to achieve this, and |
|
|
503 | more. |
|
|
504 | |
434 | =back |
505 | =back |
435 | |
506 | |
436 | =head4 Variables you might I<want> to override |
507 | =head4 Variables you might I<want> to override |
437 | |
508 | |
438 | =over 4 |
509 | =over 4 |
439 | |
510 | |
|
|
511 | =item C<STATICPERL> |
|
|
512 | |
|
|
513 | The directory where staticperl stores all its files |
|
|
514 | (default: F<~/.staticperl>). |
|
|
515 | |
|
|
516 | =item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ... |
|
|
517 | |
|
|
518 | Usually set to C<1> to make modules "less inquisitive" during their |
|
|
519 | installation, you can set any environment variable you want - some modules |
|
|
520 | (such as L<Coro> or L<EV>) use environment variables for further tweaking. |
|
|
521 | |
440 | =item C<PERLVER> |
522 | =item C<PERL_VERSION> |
441 | |
523 | |
442 | The perl version to install - default is currently C<5.12.2>, but C<5.8.9> |
524 | The perl version to install - default is currently C<5.12.2>, but C<5.8.9> |
443 | is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is |
525 | is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is |
444 | about as big as 5.12.2). |
526 | about as big as 5.12.2). |
445 | |
527 | |
446 | =item C<CPAN> |
|
|
447 | |
|
|
448 | The URL of the CPAN mirror to use (e.g. L<http://mirror.netcologne.de/cpan/>). |
|
|
449 | |
|
|
450 | =item C<EXTRA_MODULES> |
|
|
451 | |
|
|
452 | Additional modules installed during F<staticperl install>. Here you can |
|
|
453 | set which modules you want have to installed from CPAN. |
|
|
454 | |
|
|
455 | Example: I really really need EV, AnyEvent, Coro and IO::AIO. |
|
|
456 | |
|
|
457 | EXTRA_MODULES="EV AnyEvent Coro IO::AIO" |
|
|
458 | |
|
|
459 | Note that you can also use a C<postinstall> hook to achieve this, and |
|
|
460 | more. |
|
|
461 | |
|
|
462 | =item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ... |
|
|
463 | |
|
|
464 | Usually set to C<1> to make modules "less inquisitive" during their |
|
|
465 | installation, you can set any environment variable you want - some modules |
|
|
466 | (such as L<Coro> or L<EV>) use environment variables for further tweaking. |
|
|
467 | |
|
|
468 | =item C<STATICPERL> |
|
|
469 | |
|
|
470 | The directory where staticperl stores all its files |
|
|
471 | (default: F<~/.staticperl>). |
|
|
472 | |
|
|
473 | =item C<PREFIX> |
528 | =item C<PERL_PREFIX> |
474 | |
529 | |
475 | The prefix where perl gets installed (default: F<$STATICPERL/perl>), |
530 | The prefix where perl gets installed (default: F<$STATICPERL/perl>), |
476 | i.e. where the F<bin> and F<lib> subdirectories will end up. |
531 | i.e. where the F<bin> and F<lib> subdirectories will end up. |
|
|
532 | |
|
|
533 | =item C<PERL_CONFIGURE> |
|
|
534 | |
|
|
535 | Additional Configure options - these are simply passed to the perl |
|
|
536 | Configure script. For example, if you wanted to enable dynamic loading, |
|
|
537 | you could pass C<-Dusedl>. To enable ithreads (Why would you want that |
|
|
538 | insanity? Don't! Use L<forks> instead!) you would pass C<-Duseithreads> |
|
|
539 | and so on. |
|
|
540 | |
|
|
541 | More commonly, you would either activate 64 bit integer support |
|
|
542 | (C<-Duse64bitint>), or disable large files support (-Uuselargefiles), to |
|
|
543 | reduce filesize further. |
477 | |
544 | |
478 | =item C<PERL_CPPFLAGS>, C<PERL_OPTIMIZE>, C<PERL_LDFLAGS>, C<PERL_LIBS> |
545 | =item C<PERL_CPPFLAGS>, C<PERL_OPTIMIZE>, C<PERL_LDFLAGS>, C<PERL_LIBS> |
479 | |
546 | |
480 | These flags are passed to perl's F<Configure> script, and are generally |
547 | These flags are passed to perl's F<Configure> script, and are generally |
481 | optimised for small size (at the cost of performance). Since they also |
548 | optimised for small size (at the cost of performance). Since they also |
… | |
… | |
518 | instcpan Anyevent::AIO AnyEvent::HTTPD |
585 | instcpan Anyevent::AIO AnyEvent::HTTPD |
519 | } |
586 | } |
520 | |
587 | |
521 | =over 4 |
588 | =over 4 |
522 | |
589 | |
|
|
590 | =item preconfigure |
|
|
591 | |
|
|
592 | Called just before running F<./Configur> in the perl source |
|
|
593 | directory. Current working directory is the perl source directory. |
|
|
594 | |
|
|
595 | This can be used to set any C<PERL_xxx> variables, which might be costly |
|
|
596 | to compute. |
|
|
597 | |
523 | =item postconfigure |
598 | =item postconfigure |
524 | |
599 | |
525 | Called after configuring, but before building perl. Current working |
600 | Called after configuring, but before building perl. Current working |
526 | directory is the perl source directory. |
601 | directory is the perl source directory. |
527 | |
602 | |
528 | Could be used to tailor/patch config.sh (followed by F<./Configure -S>) or |
603 | Could be used to tailor/patch config.sh (followed by F<sh Configure -S>) |
529 | do any other modifications. |
604 | or do any other modifications. |
530 | |
605 | |
531 | =item postbuild |
606 | =item postbuild |
532 | |
607 | |
533 | Called after building, but before installing perl. Current working |
608 | Called after building, but before installing perl. Current working |
534 | directory is the perl source directory. |
609 | directory is the perl source directory. |
… | |
… | |
654 | |
729 | |
655 | =back |
730 | =back |
656 | |
731 | |
657 | =head1 FULLY STATIC BINARIES - BUILDROOT |
732 | =head1 FULLY STATIC BINARIES - BUILDROOT |
658 | |
733 | |
659 | To make truly static (linux-) libraries, you might want to have a look at |
734 | To make truly static (Linux-) libraries, you might want to have a look at |
660 | buildroot (L<http://buildroot.uclibc.org/>). |
735 | buildroot (L<http://buildroot.uclibc.org/>). |
661 | |
736 | |
662 | Buildroot is primarily meant to set up a cross-compile environment (which |
737 | Buildroot is primarily meant to set up a cross-compile environment (which |
663 | is not so useful as perl doesn't quite like cross compiles), but it can also compile |
738 | is not so useful as perl doesn't quite like cross compiles), but it can also compile |
664 | a chroot environment where you can use F<staticperl>. |
739 | a chroot environment where you can use F<staticperl>. |
… | |
… | |
678 | uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201 |
753 | uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201 |
679 | snapshot) and enable NPTL, otherwise Coro needs to be configured with the |
754 | snapshot) and enable NPTL, otherwise Coro needs to be configured with the |
680 | ultra-slow pthreads backend to work around linuxthreads bugs (it also uses |
755 | ultra-slow pthreads backend to work around linuxthreads bugs (it also uses |
681 | twice the address space needed for stacks). |
756 | twice the address space needed for stacks). |
682 | |
757 | |
|
|
758 | If you use C<linuxthreads.old>, then you should also be aware that |
|
|
759 | uClibc shares C<errno> between all threads when statically linking. See |
|
|
760 | L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a |
|
|
761 | workaround (And L<https://bugs.uclibc.org/2089> for discussion). |
|
|
762 | |
683 | C<ccache> support is also recommended, especially if you want to |
763 | C<ccache> support is also recommended, especially if you want |
684 | play around with buildroot options. Enabling the C<miniperl> package |
764 | to play around with buildroot options. Enabling the C<miniperl> |
685 | will probably enable all options required for a successful perl |
765 | package will probably enable all options required for a successful |
686 | build. F<staticperl> itself additionally needs either C<wget> or C<curl>. |
766 | perl build. F<staticperl> itself additionally needs either C<wget> |
|
|
767 | (recommended, for CPAN) or C<curl>. |
687 | |
768 | |
688 | As for shells, busybox should provide all that is needed, but the default |
769 | As for shells, busybox should provide all that is needed, but the default |
689 | busybox configuration doesn't include F<comm> which is needed by perl - |
770 | busybox configuration doesn't include F<comm> which is needed by perl - |
690 | either make a custom busybox config, or compile coreutils. |
771 | either make a custom busybox config, or compile coreutils. |
691 | |
772 | |