[ViewVC] Diff of: cvs/App-Staticperl/staticperl.pod

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC vs.
Revision 1.43 by root, Sun Jun 26 17:26:52 2011 UTC

…		…
9	staticperl configure # fetch and then configure perl	9	staticperl configure # fetch and then configure perl
10	staticperl build # configure and then build perl	10	staticperl build # configure and then build perl
11	staticperl install # build and then install perl	11	staticperl install # build and then install perl
12	staticperl clean # clean most intermediate files (restart at configure)	12	staticperl clean # clean most intermediate files (restart at configure)
13	staticperl distclean # delete everything installed by this script	13	staticperl distclean # delete everything installed by this script
		14	staticperl perl ... # invoke the perlinterpreter
14	staticperl cpan # invoke CPAN shell	15	staticperl cpan # invoke CPAN shell
15	staticperl instmod path... # install unpacked modules	16	staticperl instmod path... # install unpacked modules
16	staticperl instcpan modulename... # install modules from CPAN	17	staticperl instcpan modulename... # install modules from CPAN
17	staticperl mkbundle <bundle-args...> # see documentation	18	staticperl mkbundle <bundle-args...> # see documentation
18	staticperl mkperl <bundle-args...> # see documentation	19	staticperl mkperl <bundle-args...> # see documentation
…		…
20		21
21	Typical Examples:	22	Typical Examples:
22		23
23	staticperl install # fetch, configure, build and install perl	24	staticperl install # fetch, configure, build and install perl
24	staticperl cpan # run interactive cpan shell	25	staticperl cpan # run interactive cpan shell
25	staticperl mkperl -M '"Config_heavy.pl"' # build a perl that supports -V	26	staticperl mkperl -MConfig_heavy.pl # build a perl that supports -V
26	staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http	27	staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http
27	# build a perl with the above modules linked in	28	# build a perl with the above modules linked in
28	staticperl mkapp myapp --boot mainprog mymodules	29	staticperl mkapp myapp --boot mainprog mymodules
29	# build a binary "myapp" from mainprog and mymodules	30	# build a binary "myapp" from mainprog and mymodules
30		31
…		…
38	file that contains perl interpreter, libc, all the modules you need, all	39	file that contains perl interpreter, libc, all the modules you need, all
39	the libraries you need and of course your actual program.	40	the libraries you need and of course your actual program.
40		41
41	With F<uClibc> and F<upx> on x86, you can create a single 500kb binary	42	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	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	Coro and so on. Or any other choice of modules (and some other size :).
44		45
45	To see how this turns out, you can try out smallperl and bigperl, two	46	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	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	modules: just follow the links at L<http://staticperl.schmorp.de/>.
48		49
…		…
139	with creating binaries and bundle files.	140	with creating binaries and bundle files.
140		141
141	=head2 PHASE 1 COMMANDS: INSTALLING PERL	142	=head2 PHASE 1 COMMANDS: INSTALLING PERL
142		143
143	The most important command is F<install>, which does basically	144	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	everything. The default is to download and install perl 5.12.3 and a few
145	modules required by F<staticperl> itself, but all this can (and should) be	146	modules required by F<staticperl> itself, but all this can (and should) be
146	changed - see L<CONFIGURATION>, below.	147	changed - see L<CONFIGURATION>, below.
147		148
148	The command	149	The command
149		150
…		…
185		186
186	=item F<staticperl install>	187	=item F<staticperl install>
187		188
188	Wipes the perl installation directory (usually F<~/.staticperl/perl>) and	189	Wipes the perl installation directory (usually F<~/.staticperl/perl>) and
189	installs the perl distribution, potentially after building it first.	190	installs the perl distribution, potentially after building it first.
		191
		192	=item F<staticperl perl> [args...]
		193
		194	Invokes the compiled perl interpreter with the given args. Basically the
		195	same as starting perl directly (usually via F<~/.staticperl/bin/perl>),
		196	but beats typing the path sometimes.
		197
		198	Example: check that the Gtk2 module is installed and loadable.
		199
		200	staticperl perl -MGtk2 -e0
190		201
191	=item F<staticperl cpan> [args...]	202	=item F<staticperl cpan> [args...]
192		203
193	Starts an interactive CPAN shell that you can use to install further	204	Starts an interactive CPAN shell that you can use to install further
194	modules. Installs the perl first if necessary, but apart from that,	205	modules. Installs the perl first if necessary, but apart from that,
…		…
252		263
253	# first make sure we have perl and the required modules	264	# first make sure we have perl and the required modules
254	staticperl instcpan AnyEvent::HTTPD	265	staticperl instcpan AnyEvent::HTTPD
255		266
256	# now build the perl	267	# now build the perl
257	staticperl mkperl -M'"Config_heavy.pl"' -MAnyEvent::Impl::Perl \	268	staticperl mkperl -MConfig_heavy.pl -MAnyEvent::Impl::Perl \
258	-MAnyEvent::HTTPD -MURI::http \	269	-MAnyEvent::HTTPD -MURI::http \
259	--add 'eg/httpd httpd.pm'	270	--add 'eg/httpd httpd.pm'
260		271
261	# finally, invoke it	272	# finally, invoke it
262	./perl -Mhttpd	273	./perl -Mhttpd
…		…
381		392
382	=over 4	393	=over 4
383		394
384	=item C<--use> F<module> \| C<-M>F<module>	395	=item C<--use> F<module> \| C<-M>F<module>
385		396
386	Include the named module and trace direct dependencies. This is done by	397	Include the named module or perl library and trace direct
387	C<require>'ing the module in a subprocess and tracing which other modules	398	dependencies. This is done by loading the module in a subprocess and
388	and files it actually loads.	399	tracing which other modules and files it actually loads.
389		400
390	Example: include AnyEvent and AnyEvent::Impl::Perl.	401	Example: include AnyEvent and AnyEvent::Impl::Perl.
391		402
392	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl	403	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
393		404
394	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or	405	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
395	maybe other weirdly named files. To do that, you need to quote the name in	406	maybe other weirdly named files. To support this, the C<--use> option
396	single or double quotes. When given on the command line, you probably need	407	actually tries to do what you mean, depending on the string you specify:
397	to quote once more to avoid your shell interpreting it. Common cases that	408
398	need this are F<Config_heavy.pl> and F<utf8_heavy.pl>.	409	=over 4
		410
		411	=item a possibly valid module name, e.g. F<common::sense>, F<Carp>,
		412	F<Coro::Mysql>.
		413
		414	If the string contains no quotes, no F</> and no F<.>, then C<--use>
		415	assumes that it is a normal module name. It will create a new package and
		416	evaluate a C<use module> in it, i.e. it will load the package and do a
		417	default import.
		418
		419	The import step is done because many modules trigger more dependencies
		420	when something is imported than without.
		421
		422	=item anything that contains F</> or F<.> characters,
		423	e.g. F<utf8_heavy.pl>, F<Module/private/data.pl>.
		424
		425	The string will be quoted and passed to require, as if you used C<require
		426	$module>. Nothing will be imported.
		427
		428	=item "path" or 'path', e.g. C<"utf8_heavy.pl">.
		429
		430	If you enclose the name into single or double quotes, then the quotes will
		431	be removed and the resulting string will be passed to require. This syntax
		432	is form compatibility with older versions of staticperl and should not be
		433	used anymore.
		434
		435	=back
		436
		437	Example: C<use> AnyEvent::Socket, once using C<use> (importing the
		438	symbols), and once via C<require>, not importing any symbols. The first
		439	form is preferred as many modules load some extra dependencies when asked
		440	to export symbols.
		441
		442	staticperl mkbundle -MAnyEvent::Socket # use + import
		443	staticperl mkbundle -MAnyEvent/Socket.pm # require only
399		444
400	Example: include the required files for F<perl -V> to work in all its	445	Example: include the required files for F<perl -V> to work in all its
401	glory (F<Config.pm> is included automatically by this).	446	glory (F<Config.pm> is included automatically by the dependency tracker).
402		447
403	# bourne shell	448	# shell command
404	staticperl mkbundle --use '"Config_heavy.pl"'	449	staticperl mkbundle -MConfig_heavy.pl
405		450
406	# bundle specification file	451	# bundle specification file
407	use "Config_heavy.pl"	452	use Config_heavy.pl
408		453
409	The C<-M>module syntax is included as an alias that might be easier to	454	The C<-M>module syntax is included as a convenience that might be easier
410	remember than C<--use>. Or maybe it confuses people. Time will tell. Or	455	to remember than C<--use> - it's the same switch as perl itself uses
		456	to load modules. Or maybe it confuses people. Time will tell. Or maybe
411	maybe not. Sigh.	457	not. Sigh.
412		458
413	=item C<--eval> "perl code" \| C<-e> "perl code"	459	=item C<--eval> "perl code" \| C<-e> "perl code"
414		460
415	Sometimes it is easier (or necessary) to specify dependencies using perl	461	Sometimes it is easier (or necessary) to specify dependencies using perl
416	code, or maybe one of the modules you use need a special use statement. In	462	code, or maybe one of the modules you use need a special use statement. In
417	that case, you can use C<--eval> to execute some perl snippet or set some	463	that case, you can use C<--eval> to execute some perl snippet or set some
418	variables or whatever you need. All files C<require>'d or C<use>'d while	464	variables or whatever you need. All files C<require>'d or C<use>'d while
419	executing the snippet are included in the final bundle.	465	executing the snippet are included in the final bundle.
420		466
421	Keep in mind that F<mkbundle> will only C<require> the modules named	467	Keep in mind that F<mkbundle> will not import any symbols from the modules
422	by the C<--use> option, so do not expect the symbols from modules you	468	named by the C<--use> option, so do not expect the symbols from modules
423	C<--use>'d earlier on the command line to be available.	469	you C<--use>'d earlier on the command line to be available.
424		470
425	Example: force L<AnyEvent> to detect a backend and therefore include it	471	Example: force L<AnyEvent> to detect a backend and therefore include it
426	in the final bundle.	472	in the final bundle.
427		473
428	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'	474	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
…		…
455	This is very useful to include "everything":	501	This is very useful to include "everything":
456		502
457	--incglob '*'	503	--incglob '*'
458		504
459	It is also useful for including perl libraries, or trees of those, such as	505	It is also useful for including perl libraries, or trees of those, such as
460	the unicode database files needed by some perl builtins, the regex engine	506	the unicode database files needed by some perl built-ins, the regex engine
461	and other modules.	507	and other modules.
462		508
463	--incglob '/unicore/**.pl'	509	--incglob '/unicore/**.pl'
464		510
465	=item C<--add> F<file> \| C<--add> "F<file> alias"	511	=item C<--add> F<file> \| C<--add> "F<file> alias"
466		512
467	Adds the given (perl) file into the bundle (and optionally call it	513	Adds the given (perl) file into the bundle (and optionally call it
468	"alias"). The F<file> is either an absolute path or a path relative to	514	"alias"). The F<file> is either an absolute path or a path relative to the
469	the current directory. If an alias is specified, then this is the name it	515	current directory. If an alias is specified, then this is the name it will
470	will use for C<@INC> searches, otherfile the F<file> will be used as the	516	use for C<@INC> searches, otherwise the path F<file> will be used as the
471	internal name.	517	internal name.
472		518
473	This switch is used to include extra files into the bundle.	519	This switch is used to include extra files into the bundle.
474		520
475	Example: embed the file F<httpd> in the current directory as F<httpd.pm>	521	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
476	when creating the bundle.	522	when creating the bundle.
477		523
478	staticperl mkperl --add "httpd httpd.pm"	524	staticperl mkperl --add "httpd httpd.pm"
		525
		526	# can be accessed via "use httpd"
		527
		528	Example: add a file F<initcode> from the current directory.
		529
		530	staticperl mkperl --add 'initcode &initcode'
		531
		532	# can be accessed via "do '&initcode'"
479		533
480	Example: add local files as extra modules in the bundle.	534	Example: add local files as extra modules in the bundle.
481		535
482	# specification file	536	# specification file
483	add file1 myfiles/file1.pm	537	add file1 myfiles/file1.pm
…		…
493		547
494	Just like C<--add>, except that it treats the file as binary and adds it	548	Just like C<--add>, except that it treats the file as binary and adds it
495	without any postprocessing (perl files might get stripped to reduce their	549	without any postprocessing (perl files might get stripped to reduce their
496	size).	550	size).
497		551
498	You should probably add a C</> prefix to avoid clashing with embedded perl	552	If you specify an alias you should probably add a C<&> prefix to avoid
499	files (whose paths do not start with C</>), and/or use a special directory	553	clashing with embedded perl files (whose paths never start with C<&>),
500	prefix, such as C</res/name>.	554	and/or use a special directory prefix, such as C<&res/name>.
501		555
502	You can later get a copy of these files by calling C<staticperl::find	556	You can later get a copy of these files by calling C<staticperl::find
503	"alias">.	557	"alias">.
504		558
505	An alternative way to embed binary files is to convert them to perl and	559	An alternative way to embed binary files is to convert them to perl and
…		…
518		572
519	=item Step 2: filter all files using C<--include> and C<--exclude> options.	573	=item Step 2: filter all files using C<--include> and C<--exclude> options.
520		574
521	After all candidate files and modules are added, they are I<filtered>	575	After all candidate files and modules are added, they are I<filtered>
522	by a combination of C<--include> and C<--exclude> patterns (there is an	576	by a combination of C<--include> and C<--exclude> patterns (there is an
523	implicit C<--include **> at the end, so if no filters are specified, all	577	implicit C<--include *> at the end, so if no filters are specified, all
524	files are included).	578	files are included).
525		579
526	All that this step does is potentially reduce the number of files that are	580	All that this step does is potentially reduce the number of files that are
527	to be included - no new files are added during this step.	581	to be included - no new files are added during this step.
528		582
…		…
553	that are added automatically. Only one (F<.packlist> files) is currently	607	that are added automatically. Only one (F<.packlist> files) is currently
554	optional and can be influenced, the others are always included:	608	optional and can be influenced, the others are always included:
555		609
556	=over 4	610	=over 4
557		611
558	=item C<--usepacklist>	612	=item C<--usepacklists>
559		613
560	Read F<.packlist> files for each distribution that happens to match a	614	Read F<.packlist> files for each distribution that happens to match a
561	module name you specified. Sounds weird, and it is, so expect semantics to	615	module name you specified. Sounds weird, and it is, so expect semantics to
562	change somehow in the future.	616	change somehow in the future.
563		617
…		…
631	Last not least, if you need accurate line numbers in error messages,	685	Last not least, if you need accurate line numbers in error messages,
632	or in the unlikely case where C<pod> is too slow, or some module gets	686	or in the unlikely case where C<pod> is too slow, or some module gets
633	mistreated, you can specify C<none> to not mangle included perl sources in	687	mistreated, you can specify C<none> to not mangle included perl sources in
634	any way.	688	any way.
635		689
636	=item --perl	690	=item C<--perl>
637		691
638	After writing out the bundle files, try to link a new perl interpreter. It	692	After writing out the bundle files, try to link a new perl interpreter. It
639	will be called F<perl> and will be left in the current working	693	will be called F<perl> and will be left in the current working
640	directory. The bundle files will be removed.	694	directory. The bundle files will be removed.
641		695
…		…
646	it will be even smaller than the standard perl interpreter as none of the	700	it will be even smaller than the standard perl interpreter as none of the
647	modules of the base distribution (such as L<Fcntl>) will be included.	701	modules of the base distribution (such as L<Fcntl>) will be included.
648		702
649	staticperl mkperl -Mcommon::sense	703	staticperl mkperl -Mcommon::sense
650		704
651	=item --app name	705	=item C<--app> F<name>
652		706
653	After writing out the bundle files, try to link a new standalone	707	After writing out the bundle files, try to link a new standalone
654	program. It will be called C<name>, and the bundle files get removed after	708	program. It will be called C<name>, and the bundle files get removed after
655	linking it.	709	linking it.
656		710
…		…
660	The difference to the (mutually exclusive) C<--perl> option is that the	714	The difference to the (mutually exclusive) C<--perl> option is that the
661	binary created by this option will not try to act as a perl interpreter -	715	binary created by this option will not try to act as a perl interpreter -
662	instead it will simply initialise the perl interpreter, clean it up and	716	instead it will simply initialise the perl interpreter, clean it up and
663	exit.	717	exit.
664		718
665	This means that, by default, it will do nothing but burna few CPU cycles	719	This means that, by default, it will do nothing but burn a few CPU cycles
666	- for it to do something useful you I<must> add some boot code, e.g. with	720	- for it to do something useful you I<must> add some boot code, e.g. with
667	the C<--boot> option.	721	the C<--boot> option.
668		722
669	Example: create a standalone perl binary called F<./myexe> that will	723	Example: create a standalone perl binary called F<./myexe> that will
670	execute F<appfile> when it is started.	724	execute F<appfile> when it is started.
671		725
672	staticperl mkbundle --app myexe --boot appfile	726	staticperl mkbundle --app myexe --boot appfile
673		727
		728	=item C<--ignore-env>
		729
		730	Generates extra code to unset some environment variables before
		731	initialising/running perl. Perl supports a lot of environment variables
		732	that might alter execution in ways that might be undesirablre for
		733	standalone applications, and this option removes those known to cause
		734	trouble.
		735
		736	Specifically, these are removed:
		737
		738	C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause underaible
		739	output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and
		740	C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>,
		741	C<PERLIO_DEBUG> and C<PERLIO> can affect input and output.
		742
		743	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
		744	startup code used by F<staticperl> overrides C<@INC> in all cases.
		745
		746	This option will not make your program more secure (unless you are
		747	running with elevated privileges), but it will reduce the surprise effect
		748	when a user has these environment variables set and doesn't expect your
		749	standalone program to act like a perl interpreter.
		750
674	=item --static	751	=item C<--static>
675		752
676	Add C<-static> to F<bundle.ldopts>, which means a fully static (if	753	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
677	supported by the OS) executable will be created. This is not immensely	754	supported by the OS) executable will be created. This is not immensely
678	useful when just creating the bundle files, but is most useful when	755	useful when just creating the bundle files, but is most useful when
679	linking a binary with the C<--perl> or C<--app> options.	756	linking a binary with the C<--perl> or C<--app> options.
…		…
686	systems based on GNU libc don't really support it in a very usable	763	systems based on GNU libc don't really support it in a very usable
687	fashion either. Try uClibc if you want to create fully statically linked	764	fashion either. Try uClibc if you want to create fully statically linked
688	executables, or try the C<--staticlib> option to link only some libraries	765	executables, or try the C<--staticlib> option to link only some libraries
689	statically.	766	statically.
690		767
691	=item --staticlib libname	768	=item C<--staticlib> libname
692		769
693	When not linking fully statically, this option allows you to link specific	770	When not linking fully statically, this option allows you to link specific
694	libraries statically. What it does is simply replace all occurances of	771	libraries statically. What it does is simply replace all occurrences of
695	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>	772	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>
696	option.	773	option.
697		774
698	This will have no effect unless the library is actually linked against,	775	This will have no effect unless the library is actually linked against,
699	specifically, C<--staticlib> will not link against the named library	776	specifically, C<--staticlib> will not link against the named library
700	unless it would be linked against anyway.	777	unless it would be linked against anyway.
701		778
702	Example: link libcrypt statically into the binary.	779	Example: link libcrypt statically into the final binary.
703		780
704	staticperl mkperl -MIO::AIO --staticlib crypt	781	staticperl mkperl -MIO::AIO --staticlib crypt
705		782
706	# ldopts might now contain:	783	# ldopts might now contain:
707	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread	784	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread
…		…
728	=item Patterns not starting with F</> will be anchored at the end of the path.	805	=item Patterns not starting with F</> will be anchored at the end of the path.
729		806
730	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the	807	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the
731	hierarchy, but not any directories of the same name.	808	hierarchy, but not any directories of the same name.
732		809
733	=item A F<*> matches any single component.	810	=item A F<*> matches anything within a single path component.
734		811
735	That is, F</unicore/*.pl> would match all F<.pl> files directly inside	812	That is, F</unicore/*.pl> would match all F<.pl> files directly inside
736	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>	813	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>
737	will not match slashes.	814	will not match slashes.
738		815
…		…
805	=item C<STATICPERL>	882	=item C<STATICPERL>
806		883
807	The directory where staticperl stores all its files	884	The directory where staticperl stores all its files
808	(default: F<~/.staticperl>).	885	(default: F<~/.staticperl>).
809		886
		887	=item C<DLCACHE>
		888
		889	The path to a directory (will be created if it doesn't exist) where
		890	downloaded perl sources are being cached, to avoid downloading them
		891	again. The default is empty, which means there is no cache.
		892
		893	=item C<PERL_VERSION>
		894
		895	The perl version to install - default is currently C<5.12.3>, but C<5.8.9>
		896	is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is
		897	about as big as 5.12.3).
		898
810	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...	899	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...
811		900
812	Usually set to C<1> to make modules "less inquisitive" during their	901	Usually set to C<1> to make modules "less inquisitive" during their
813	installation, you can set any environment variable you want - some modules	902	installation, you can set any environment variable you want - some modules
814	(such as L<Coro> or L<EV>) use environment variables for further tweaking.	903	(such as L<Coro> or L<EV>) use environment variables for further tweaking.
815
816	=item C<PERL_VERSION>
817
818	The perl version to install - default is currently C<5.12.2>, but C<5.8.9>
819	is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is
820	about as big as 5.12.2).
821		904
822	=item C<PERL_PREFIX>	905	=item C<PERL_PREFIX>
823		906
824	The prefix where perl gets installed (default: F<$STATICPERL/perl>),	907	The prefix where perl gets installed (default: F<$STATICPERL/perl>),
825	i.e. where the F<bin> and F<lib> subdirectories will end up.	908	i.e. where the F<bin> and F<lib> subdirectories will end up.
…		…
846	F<~/.staticperlrc> to override them.	929	F<~/.staticperlrc> to override them.
847		930
848	Most of the variables override (or modify) the corresponding F<Configure>	931	Most of the variables override (or modify) the corresponding F<Configure>
849	variable, except C<PERL_CCFLAGS>, which gets appended.	932	variable, except C<PERL_CCFLAGS>, which gets appended.
850		933
		934	You should have a look near the beginning of the F<staticperl> script -
		935	staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options
		936	suitable for newer gcc versions. For other compilers or older versions you
		937	need to adjust these, for example, in your F<~/.staticperlrc>.
		938
851	=back	939	=back
852		940
853	=head4 Variables you probably I<do not want> to override	941	=head4 Variables you probably I<do not want> to override
854		942
855	=over 4	943	=over 4
…		…
873	=head3 OVERRIDABLE HOOKS	961	=head3 OVERRIDABLE HOOKS
874		962
875	In addition to environment variables, it is possible to provide some	963	In addition to environment variables, it is possible to provide some
876	shell functions that are called at specific times. To provide your own	964	shell functions that are called at specific times. To provide your own
877	commands, just define the corresponding function.	965	commands, just define the corresponding function.
		966
		967	The actual order in which hooks are invoked during a full install
		968	from scratch is C<preconfigure>, C<patchconfig>, C<postconfigure>,
		969	C<postbuild>, C<postinstall>.
878		970
879	Example: install extra modules from CPAN and from some directories	971	Example: install extra modules from CPAN and from some directories
880	at F<staticperl install> time.	972	at F<staticperl install> time.
881		973
882	postinstall() {	974	postinstall() {
…		…
889		981
890	=over 4	982	=over 4
891		983
892	=item preconfigure	984	=item preconfigure
893		985
894	Called just before running F<./Configur> in the perl source	986	Called just before running F<./Configure> in the perl source
895	directory. Current working directory is the perl source directory.	987	directory. Current working directory is the perl source directory.
896		988
897	This can be used to set any C<PERL_xxx> variables, which might be costly	989	This can be used to set any C<PERL_xxx> variables, which might be costly
898	to compute.	990	to compute.
899		991
		992	=item patchconfig
		993
		994	Called after running F<./Configure> in the perl source directory to create
		995	F<./config.sh>, but before running F<./Configure -S> to actually apply the
		996	config. Current working directory is the perl source directory.
		997
		998	Can be used to tailor/patch F<config.sh> or do any other modifications.
		999
900	=item postconfigure	1000	=item postconfigure
901		1001
902	Called after configuring, but before building perl. Current working	1002	Called after configuring, but before building perl. Current working
903	directory is the perl source directory.	1003	directory is the perl source directory.
904
905	Could be used to tailor/patch config.sh (followed by F<sh Configure -S>)
906	or do any other modifications.
907		1004
908	=item postbuild	1005	=item postbuild
909		1006
910	Called after building, but before installing perl. Current working	1007	Called after building, but before installing perl. Current working
911	directory is the perl source directory.	1008	directory is the perl source directory.
…		…
949	A header file that contains the prototypes of the few symbols "exported"	1046	A header file that contains the prototypes of the few symbols "exported"
950	by bundle.c, and also exposes the perl headers to the application.	1047	by bundle.c, and also exposes the perl headers to the application.
951		1048
952	=over 4	1049	=over 4
953		1050
954	=item staticperl_init ()	1051	=item staticperl_init (xs_init = 0)
955		1052
956	Initialises the perl interpreter. You can use the normal perl functions	1053	Initialises the perl interpreter. You can use the normal perl functions
957	after calling this function, for example, to define extra functions or	1054	after calling this function, for example, to define extra functions or
958	to load a .pm file that contains some initialisation code, or the main	1055	to load a .pm file that contains some initialisation code, or the main
959	program function:	1056	program function:
…		…
966	}	1063	}
967		1064
968	static void	1065	static void
969	run_myapp(void)	1066	run_myapp(void)
970	{	1067	{
971	staticperl_init ();	1068	staticperl_init (0);
972	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");	1069	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
973	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"	1070	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"
974	}	1071	}
975		1072
		1073	When your bootcode already wants to access some XS functions at
		1074	compiletime, then you need to supply an C<xs_init> function pointer that
		1075	is called as soon as perl is initialised enough to define XS functions,
		1076	but before the preamble code is executed:
		1077
		1078	static void
		1079	xs_init (pTHX)
		1080	{
		1081	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
		1082	}
		1083
		1084	static void
		1085	run_myapp(void)
		1086	{
		1087	staticperl_init (xs_init);
		1088	}
		1089
		1090	=item staticperl_cleanup ()
		1091
		1092	In the unlikely case that you want to destroy the perl interpreter, here
		1093	is the corresponding function.
		1094
976	=item staticperl_xs_init (pTHX)	1095	=item staticperl_xs_init (pTHX)
977		1096
978	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in	1097	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in
979	which case you do not want to use C<staticperl_init> but call them on your	1098	which case you do not want to use C<staticperl_init> but call them on your
980	own.	1099	own.
981		1100
982	Then you need this function - either pass it directly as the C<xs_init>	1101	Then you need this function - either pass it directly as the C<xs_init>
983	function to C<perl_parse>, or call it from your own C<xs_init> function.	1102	function to C<perl_parse>, or call it as one of the first things from your
984		1103	own C<xs_init> function.
985	=item staticperl_cleanup ()
986
987	In the unlikely case that you want to destroy the perl interpreter, here
988	is the corresponding function.
989		1104
990	=item PerlInterpreter *staticperl	1105	=item PerlInterpreter *staticperl
991		1106
992	The perl interpreter pointer used by staticperl. Not normally so useful,	1107	The perl interpreter pointer used by staticperl. Not normally so useful,
993	but there it is.	1108	but there it is.
…		…
1029		1144
1030	Returns the list of all paths embedded in this binary.	1145	Returns the list of all paths embedded in this binary.
1031		1146
1032	=back	1147	=back
1033		1148
1034	=head1 FULLY STATIC BINARIES - BUILDROOT	1149	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
1035		1150
1036	To make truly static (Linux-) libraries, you might want to have a look at	1151	To make truly static (Linux-) libraries, you might want to have a look at
1037	buildroot (L<http://buildroot.uclibc.org/>).	1152	buildroot (L<http://buildroot.uclibc.org/>).
1038		1153
1039	Buildroot is primarily meant to set up a cross-compile environment (which	1154	Buildroot is primarily meant to set up a cross-compile environment (which
…		…
1046	good experiences with GCC 4.4.x but not GCC 4.5.	1161	good experiences with GCC 4.4.x but not GCC 4.5.
1047		1162
1048	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections	1163	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections
1049	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>	1164	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>
1050	doesn't decrease codesize much, but it makes the file much more	1165	doesn't decrease codesize much, but it makes the file much more
1051	compressible.	1166	compressible (and the execution a lot slower...).
1052		1167
1053	If you don't need Coro or threads, you can go with "linuxthreads.old" (or	1168	If you don't need Coro or threads, you can go with "linuxthreads.old" (or
1054	no thread support). For Coro, it is highly recommended to switch to a	1169	no thread support). For Coro, it is highly recommended to switch to a
1055	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201	1170	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201
1056	snapshot) and enable NPTL, otherwise Coro needs to be configured with the	1171	snapshot) and enable NPTL, otherwise Coro needs to be configured with the
…		…
1058	twice the address space needed for stacks).	1173	twice the address space needed for stacks).
1059		1174
1060	If you use C<linuxthreads.old>, then you should also be aware that	1175	If you use C<linuxthreads.old>, then you should also be aware that
1061	uClibc shares C<errno> between all threads when statically linking. See	1176	uClibc shares C<errno> between all threads when statically linking. See
1062	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a	1177	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a
1063	workaround (And L<https://bugs.uclibc.org/2089> for discussion).	1178	workaround (and L<https://bugs.uclibc.org/2089> for discussion).
1064		1179
1065	C<ccache> support is also recommended, especially if you want	1180	C<ccache> support is also recommended, especially if you want
1066	to play around with buildroot options. Enabling the C<miniperl>	1181	to play around with buildroot options. Enabling the C<miniperl>
1067	package will probably enable all options required for a successful	1182	package will probably enable all options required for a successful
1068	perl build. F<staticperl> itself additionally needs either C<wget>	1183	perl build. F<staticperl> itself additionally needs either C<wget>
…		…
1076	it from working properly in a chroot - either use dash (and link it to	1191	it from working properly in a chroot - either use dash (and link it to
1077	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's	1192	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's
1078	built-in ash shell.	1193	built-in ash shell.
1079		1194
1080	Finally, you need F</dev/null> inside the chroot for many scripts to work	1195	Finally, you need F</dev/null> inside the chroot for many scripts to work
1081	- F<cp /dev/null output/target/dev> or bind-mounting your F</dev> will	1196	- either F<cp /dev/null output/target/dev> or bind-mounting your F</dev>
1082	both provide this.	1197	will provide this.
1083		1198
1084	After you have compiled and set up your buildroot target, you can copy	1199	After you have compiled and set up your buildroot target, you can copy
1085	F<staticperl> from the C<App::Staticperl> distribution or from your	1200	F<staticperl> from the C<App::Staticperl> distribution or from your
1086	perl f<bin> directory (if you installed it) into the F<output/target>	1201	perl F<bin> directory (if you installed it) into the F<output/target>
1087	filesystem, chroot inside and run it.	1202	filesystem, chroot inside and run it.
1088		1203
1089	=head1 RECIPES / SPECIFIC MODULES	1204	=head1 RECIPES / SPECIFIC MODULES
1090		1205
1091	This section contains some common(?) recipes and information about	1206	This section contains some common(?) recipes and information about
…		…
1100		1215
1101	Some functionality in the utf8 module, such as swash handling (used	1216	Some functionality in the utf8 module, such as swash handling (used
1102	for unicode character ranges in regexes) is implemented in the	1217	for unicode character ranges in regexes) is implemented in the
1103	C<"utf8_heavy.pl"> library:	1218	C<"utf8_heavy.pl"> library:
1104		1219
1105	-M'"utf8_heavy.pl"'	1220	-Mutf8_heavy.pl
1106		1221
1107	Many Unicode properties in turn are defined in separate modules,	1222	Many Unicode properties in turn are defined in separate modules,
1108	such as C<"unicore/Heavy.pl"> and more specific data tables such as	1223	such as C<"unicore/Heavy.pl"> and more specific data tables such as
1109	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables	1224	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables
1110	are big (7MB uncompressed, although F<staticperl> contains special	1225	are big (7MB uncompressed, although F<staticperl> contains special
1111	handling for those files), so including them on demand by your application	1226	handling for those files), so including them on demand by your application
1112	only might pay off.	1227	only might pay off.
1113		1228
1114	To simply include the whole unicode database, use:	1229	To simply include the whole unicode database, use:
1115		1230
1116	--incglob '/unicore/*.pl'	1231	--incglob '/unicore/**.pl'
1117		1232
1118	=item AnyEvent	1233	=item AnyEvent
1119		1234
1120	AnyEvent needs a backend implementation that it will load in a delayed	1235	AnyEvent needs a backend implementation that it will load in a delayed
1121	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice	1236	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice
…		…
1126		1241
1127	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn	1242	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn
1128	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and	1243	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and
1129	C<"AnyEvent/Util/uts46data.pl">.	1244	C<"AnyEvent/Util/uts46data.pl">.
1130		1245
1131	Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include	1246	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
1132	everything.	1247	everything.
		1248
		1249	=item Cairo
		1250
		1251	See Glib, same problem, same solution.
1133		1252
1134	=item Carp	1253	=item Carp
1135		1254
1136	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1255	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
1137	perl 5.12.2 (maybe earlier), this dependency no longer exists.	1256	perl 5.12.2 (maybe earlier), this dependency no longer exists.
…		…
1140		1259
1141	The F<perl -V> switch (as well as many modules) needs L<Config>, which in	1260	The F<perl -V> switch (as well as many modules) needs L<Config>, which in
1142	turn might need L<"Config_heavy.pl">. Including the latter gives you	1261	turn might need L<"Config_heavy.pl">. Including the latter gives you
1143	both.	1262	both.
1144		1263
		1264	=item Glib
		1265
		1266	Glib literally requires Glib to be installed already to build - it tries
		1267	to fake this by running Glib out of the build directory before being
		1268	built. F<staticperl> tries to work around this by forcing C<MAN1PODS> and
		1269	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
		1270
		1271	=item Gtk2
		1272
		1273	See Pango, same problems, same solution.
		1274
		1275	=item Pango
		1276
		1277	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
		1278	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>
		1279	tries to patch L<ExtUtils::MM_Unix> to route around Pango.
		1280
1145	=item Term::ReadLine::Perl	1281	=item Term::ReadLine::Perl
1146		1282
1147	Also needs L<Term::ReadLine::readline>, or C<--usepacklist>.	1283	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
1148		1284
1149	=item URI	1285	=item URI
1150		1286
1151	URI implements schemes as separate modules - the generic URL scheme is	1287	URI implements schemes as separate modules - the generic URL scheme is
1152	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If	1288	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If
1153	you need to use any of these schemes, you should include these manually,	1289	you need to use any of these schemes, you should include these manually,
1154	or use C<--usepacklist>.	1290	or use C<--usepacklists>.
1155		1291
1156	=back	1292	=back
1157		1293
1158	=head2 RECIPES	1294	=head2 RECIPES
1159		1295
1160	=over 4	1296	=over 4
1161		1297
1162	=item Linking everything in	1298	=item Just link everything in
1163		1299
1164	To link just about everything installed in the perl library into a new	1300	To link just about everything installed in the perl library into a new
1165	perl, try this:	1301	perl, try this (the first time this runs it will take a long time, as a
		1302	lot of files need to be parsed):
1166		1303
1167	staticperl mkperl --strip ppi --incglob '*'	1304	staticperl mkperl -v --strip ppi --incglob '*'
1168		1305
		1306	If you don't mind the extra megabytes, this can be a very effective way of
		1307	creating bundles without having to worry about forgetting any modules.
		1308
		1309	You get even more useful variants of this method by first selecting
		1310	everything, and then excluding stuff you are reasonable sure not to need -
		1311	L<bigperl\|http://staticperl.schmorp.de/bigperl.html> uses this approach.
		1312
1169	=item Getting rid of netdb function	1313	=item Getting rid of netdb functions
1170		1314
1171	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>	1315	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>
1172	and so on) that few applications use. You can avoid compiling them in by	1316	and so on) that few applications use. You can avoid compiling them in by
1173	putting the following fragment into a C<preconfigure> hook:	1317	putting the following fragment into a C<preconfigure> hook:
1174		1318
…		…
1191	do	1335	do
1192	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"	1336	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
1193	done	1337	done
1194	}	1338	}
1195		1339
1196	This mostly gains space when linking staticaly, as the functions will	1340	This mostly gains space when linking statically, as the functions will
1197	likely not be linked in. The gain for dynamically-linked binaries is	1341	likely not be linked in. The gain for dynamically-linked binaries is
1198	smaller.	1342	smaller.
1199		1343
1200	Also, this leaves C<gethostbyname> in - not only is it actually used	1344	Also, this leaves C<gethostbyname> in - not only is it actually used
1201	often, the L<Socket> module also exposes it, so leaving it out usually	1345	often, the L<Socket> module also exposes it, so leaving it out usually

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing App-Staticperl/staticperl.pod (file contents): Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC vs. Revision 1.43 by root, Sun Jun 26 17:26:52 2011 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC vs.
Revision 1.43 by root, Sun Jun 26 17:26:52 2011 UTC