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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.29 by root, Wed Dec 22 01:23:37 2010 UTC vs.
Revision 1.57 by root, Wed Dec 5 15:19:52 2012 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	staticperl - perl, libc, 100 modules, all in one 500kb file	3	staticperl - perl, libc, 100 modules, all in one standalone 500kb file
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	staticperl help # print the embedded documentation	7	staticperl help # print the embedded documentation
8	staticperl fetch # fetch and unpack perl sources	8	staticperl fetch # fetch and unpack perl sources
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 instsrc 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
19	staticperl mkapp appname <bundle-args...> # see documentation	20	staticperl mkapp appname <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
…		…
83	With F<staticperl>, the burden is mostly with the developer - only direct	84	With F<staticperl>, the burden is mostly with the developer - only direct
84	compile-time dependencies and L<AutoLoader> are handled automatically.	85	compile-time dependencies and L<AutoLoader> are handled automatically.
85	This means the modules to include often need to be tweaked manually.	86	This means the modules to include often need to be tweaked manually.
86		87
87	All this does not preclude more permissive modes to be implemented in	88	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	the future, but right now, you have to resolve hidden dependencies
89	manually.	90	manually.
90		91
91	=item * PAR works out of the box, F<staticperl> does not.	92	=item * PAR works out of the box, F<staticperl> does not.
92		93
93	Maintaining your own custom perl build can be a pain in the ass, and while	94	Maintaining your own custom perl build can be a pain in the ass, and while
…		…
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
…		…
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.
190		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
		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,
195	no magic is involved: you could just as well run it manually via	206	no magic is involved: you could just as well run it manually via
196	F<~/.staticperl/perl/bin/cpan>.	207	F<~/.staticperl/perl/bin/cpan>, except that F<staticperl> additionally
		208	sets the environment variable C<$PERL> to the path of the perl
		209	interpreter, which is handy in subshells.
197		210
198	Any additional arguments are simply passed to the F<cpan> command.	211	Any additional arguments are simply passed to the F<cpan> command.
199		212
200	=item F<staticperl instcpan> module...	213	=item F<staticperl instcpan> module...
201		214
…		…
252		265
253	# first make sure we have perl and the required modules	266	# first make sure we have perl and the required modules
254	staticperl instcpan AnyEvent::HTTPD	267	staticperl instcpan AnyEvent::HTTPD
255		268
256	# now build the perl	269	# now build the perl
257	staticperl mkperl -M'"Config_heavy.pl"' -MAnyEvent::Impl::Perl \	270	staticperl mkperl -MConfig_heavy.pl -MAnyEvent::Impl::Perl \
258	-MAnyEvent::HTTPD -MURI::http \	271	-MAnyEvent::HTTPD -MURI::http \
259	--add 'eg/httpd httpd.pm'	272	--add 'eg/httpd httpd.pm'
260		273
261	# finally, invoke it	274	# finally, invoke it
262	./perl -Mhttpd	275	./perl -Mhttpd
…		…
335	add eg/httpd httpd.pm	348	add eg/httpd httpd.pm
336		349
337	All options that specify modules or files to be added are processed in the	350	All options that specify modules or files to be added are processed in the
338	order given on the command line.	351	order given on the command line.
339		352
340	=head3 BUNDLE CREATION WORKFLOW / STATICPELR MKBUNDLE OPTIONS	353	=head3 BUNDLE CREATION WORKFLOW / STATICPERL MKBUNDLE OPTIONS
341		354
342	F<staticperl mkbundle> works by first assembling a list of candidate	355	F<staticperl mkbundle> works by first assembling a list of candidate
343	files and modules to include, then filtering them by include/exclude	356	files and modules to include, then filtering them by include/exclude
344	patterns. The remaining modules (together with their direct dependencies,	357	patterns. The remaining modules (together with their direct dependencies,
345	such as link libraries and L<AutoLoader> files) are then converted into	358	such as link libraries and L<AutoLoader> files) are then converted into
…		…
381		394
382	=over 4	395	=over 4
383		396
384	=item C<--use> F<module> \| C<-M>F<module>	397	=item C<--use> F<module> \| C<-M>F<module>
385		398
386	Include the named module and trace direct dependencies. This is done by	399	Include the named module or perl library and trace direct
387	C<require>'ing the module in a subprocess and tracing which other modules	400	dependencies. This is done by loading the module in a subprocess and
388	and files it actually loads.	401	tracing which other modules and files it actually loads.
389		402
390	Example: include AnyEvent and AnyEvent::Impl::Perl.	403	Example: include AnyEvent and AnyEvent::Impl::Perl.
391		404
392	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl	405	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
393		406
394	Sometimes you want to load old-style "perl libraries" (F<.pl> files),	407	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
395	or maybe other weirdly named files. To do that, you need to quote	408	maybe other weirdly named files. To support this, the C<--use> option
396	the name in single or double quotes (this is because F<staticperl>	409	actually tries to do what you mean, depending on the string you specify:
397	I<literally> just adds the string after the C<require> - which acts	410
398	different when confronted with quoted vs. unquoted strings). When given on	411	=over 4
399	the command line, you probably need to quote once more to avoid your shell	412
400	interpreting it. Common cases that need this are F<Config_heavy.pl> and	413	=item a possibly valid module name, e.g. F<common::sense>, F<Carp>,
401	F<utf8_heavy.pl>.	414	F<Coro::Mysql>.
		415
		416	If the string contains no quotes, no F</> and no F<.>, then C<--use>
		417	assumes that it is a normal module name. It will create a new package and
		418	evaluate a C<use module> in it, i.e. it will load the package and do a
		419	default import.
		420
		421	The import step is done because many modules trigger more dependencies
		422	when something is imported than without.
		423
		424	=item anything that contains F</> or F<.> characters,
		425	e.g. F<utf8_heavy.pl>, F<Module/private/data.pl>.
		426
		427	The string will be quoted and passed to require, as if you used C<require
		428	$module>. Nothing will be imported.
		429
		430	=item "path" or 'path', e.g. C<"utf8_heavy.pl">.
		431
		432	If you enclose the name into single or double quotes, then the quotes will
		433	be removed and the resulting string will be passed to require. This syntax
		434	is form compatibility with older versions of staticperl and should not be
		435	used anymore.
		436
		437	=back
		438
		439	Example: C<use> AnyEvent::Socket, once using C<use> (importing the
		440	symbols), and once via C<require>, not importing any symbols. The first
		441	form is preferred as many modules load some extra dependencies when asked
		442	to export symbols.
		443
		444	staticperl mkbundle -MAnyEvent::Socket # use + import
		445	staticperl mkbundle -MAnyEvent/Socket.pm # require only
402		446
403	Example: include the required files for F<perl -V> to work in all its	447	Example: include the required files for F<perl -V> to work in all its
404	glory (F<Config.pm> is included automatically by this).	448	glory (F<Config.pm> is included automatically by the dependency tracker).
405		449
406	# bourne shell	450	# shell command
407	staticperl mkbundle --use '"Config_heavy.pl"'	451	staticperl mkbundle -MConfig_heavy.pl
408		452
409	# bundle specification file	453	# bundle specification file
410	use "Config_heavy.pl"	454	use Config_heavy.pl
411		455
412	The C<-M>module syntax is included as a convenience that might be easier	456	The C<-M>module syntax is included as a convenience that might be easier
413	to remember than C<--use> - it's the same switch as perl itself uses	457	to remember than C<--use> - it's the same switch as perl itself uses
414	to load modules. Or maybe it confuses people. Time will tell. Or maybe	458	to load modules. Or maybe it confuses people. Time will tell. Or maybe
415	not. Sigh.	459	not. Sigh.
…		…
420	code, or maybe one of the modules you use need a special use statement. In	464	code, or maybe one of the modules you use need a special use statement. In
421	that case, you can use C<--eval> to execute some perl snippet or set some	465	that case, you can use C<--eval> to execute some perl snippet or set some
422	variables or whatever you need. All files C<require>'d or C<use>'d while	466	variables or whatever you need. All files C<require>'d or C<use>'d while
423	executing the snippet are included in the final bundle.	467	executing the snippet are included in the final bundle.
424		468
425	Keep in mind that F<mkbundle> will only C<require> the modules named	469	Keep in mind that F<mkbundle> will not import any symbols from the modules
426	by the C<--use> option, so do not expect the symbols from modules you	470	named by the C<--use> option, so do not expect the symbols from modules
427	C<--use>'d earlier on the command line to be available.	471	you C<--use>'d earlier on the command line to be available.
428		472
429	Example: force L<AnyEvent> to detect a backend and therefore include it	473	Example: force L<AnyEvent> to detect a backend and therefore include it
430	in the final bundle.	474	in the final bundle.
431		475
432	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'	476	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
…		…
467	--incglob '/unicore/**.pl'	511	--incglob '/unicore/**.pl'
468		512
469	=item C<--add> F<file> \| C<--add> "F<file> alias"	513	=item C<--add> F<file> \| C<--add> "F<file> alias"
470		514
471	Adds the given (perl) file into the bundle (and optionally call it	515	Adds the given (perl) file into the bundle (and optionally call it
472	"alias"). The F<file> is either an absolute path or a path relative to	516	"alias"). The F<file> is either an absolute path or a path relative to the
473	the current directory. If an alias is specified, then this is the name it	517	current directory. If an alias is specified, then this is the name it will
474	will use for C<@INC> searches, otherwise the F<file> will be used as the	518	use for C<@INC> searches, otherwise the path F<file> will be used as the
475	internal name.	519	internal name.
476		520
477	This switch is used to include extra files into the bundle.	521	This switch is used to include extra files into the bundle.
478		522
479	Example: embed the file F<httpd> in the current directory as F<httpd.pm>	523	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
480	when creating the bundle.	524	when creating the bundle.
481		525
482	staticperl mkperl --add "httpd httpd.pm"	526	staticperl mkperl --add "httpd httpd.pm"
		527
		528	# can be accessed via "use httpd"
		529
		530	Example: add a file F<initcode> from the current directory.
		531
		532	staticperl mkperl --add 'initcode &initcode'
		533
		534	# can be accessed via "do '&initcode'"
483		535
484	Example: add local files as extra modules in the bundle.	536	Example: add local files as extra modules in the bundle.
485		537
486	# specification file	538	# specification file
487	add file1 myfiles/file1.pm	539	add file1 myfiles/file1.pm
…		…
491	# then later, in perl, use	543	# then later, in perl, use
492	use myfiles::file1;	544	use myfiles::file1;
493	require myfiles::file2;	545	require myfiles::file2;
494	my $res = do "myfiles/file3.pl";	546	my $res = do "myfiles/file3.pl";
495		547
496	=item C<--binadd> F<file> \| C<--add> "F<file> alias"	548	=item C<--binadd> F<file> \| C<--binadd> "F<file> alias"
497		549
498	Just like C<--add>, except that it treats the file as binary and adds it	550	Just like C<--add>, except that it treats the file as binary and adds it
499	without any postprocessing (perl files might get stripped to reduce their	551	without any postprocessing (perl files might get stripped to reduce their
500	size).	552	size).
501		553
502	You should probably add a C</> prefix to avoid clashing with embedded perl	554	If you specify an alias you should probably add a C</> prefix to avoid
503	files (whose paths do not start with C</>), and/or use a special directory	555	clashing with embedded perl files (whose paths never start with C</>),
504	prefix, such as C</res/name>.	556	and/or use a special directory prefix, such as C</res/name>.
505		557
506	You can later get a copy of these files by calling C<staticperl::find	558	You can later get a copy of these files by calling C<static::find
507	"alias">.	559	"alias">.
508		560
509	An alternative way to embed binary files is to convert them to perl and	561	An alternative way to embed binary files is to convert them to perl and
510	use C<do> to get the contents - this method is a bit cumbersome, but works	562	use C<do> to get the contents - this method is a bit cumbersome, but works
511	both inside and outside of a staticperl bundle:	563	both inside and outside of a staticperl bundle, without extra ado:
512		564
513	# a "binary" file, call it "bindata.pl"	565	# a "binary" file, call it "bindata.pl"
514	<<'SOME_MARKER'	566	<<'SOME_MARKER'
515	binary data NOT containing SOME_MARKER	567	binary data NOT containing SOME_MARKER
516	SOME_MARKER	568	SOME_MARKER
517		569
518	# load the binary	570	# load the binary
519	chomp (my $data = do "bindata.pl");	571	chomp (my $data = do "bindata.pl");
		572
		573	=item C<--allow-dynamic>
		574
		575	By default, when F<mkbundle> hits a dynamic perl extension (e.g. a F<.so>
		576	or F<.dll> file), it will stop with a fatal error.
		577
		578	When this option is enabled, F<mkbundle> packages the shared
		579	object into the bundle instead, with a prefix of F<!>
		580	(e.g. F<!auto/List/Util/Util.so>). What you do with that is currently up
		581	to you, F<staticperl> has no special support for this at the moment, apart
		582	from working around the lack of availability of F<PerlIO::scalar> while
		583	bootstrapping, at a speed cost.
		584
		585	One way to deal with this is to write all files starting with F<!> into
		586	some directory and then C<unshift> that path onto C<@INC>.
		587
		588	#TODO: example
520		589
521	=back	590	=back
522		591
523	=item Step 2: filter all files using C<--include> and C<--exclude> options.	592	=item Step 2: filter all files using C<--include> and C<--exclude> options.
524		593
…		…
664	The difference to the (mutually exclusive) C<--perl> option is that the	733	The difference to the (mutually exclusive) C<--perl> option is that the
665	binary created by this option will not try to act as a perl interpreter -	734	binary created by this option will not try to act as a perl interpreter -
666	instead it will simply initialise the perl interpreter, clean it up and	735	instead it will simply initialise the perl interpreter, clean it up and
667	exit.	736	exit.
668		737
669	This means that, by default, it will do nothing but burna few CPU cycles	738	This means that, by default, it will do nothing but burn a few CPU cycles
670	- for it to do something useful you I<must> add some boot code, e.g. with	739	- for it to do something useful you I<must> add some boot code, e.g. with
671	the C<--boot> option.	740	the C<--boot> option.
672		741
673	Example: create a standalone perl binary called F<./myexe> that will	742	Example: create a standalone perl binary called F<./myexe> that will
674	execute F<appfile> when it is started.	743	execute F<appfile> when it is started.
675		744
676	staticperl mkbundle --app myexe --boot appfile	745	staticperl mkbundle --app myexe --boot appfile
		746
		747	=item C<--ignore-env>
		748
		749	Generates extra code to unset some environment variables before
		750	initialising/running perl. Perl supports a lot of environment variables
		751	that might alter execution in ways that might be undesirablre for
		752	standalone applications, and this option removes those known to cause
		753	trouble.
		754
		755	Specifically, these are removed:
		756
		757	C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause undesirable
		758	output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and
		759	C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>,
		760	C<PERLIO_DEBUG> and C<PERLIO> can affect input and output.
		761
		762	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
		763	startup code used by F<staticperl> overrides C<@INC> in all cases.
		764
		765	This option will not make your program more secure (unless you are
		766	running with elevated privileges), but it will reduce the surprise effect
		767	when a user has these environment variables set and doesn't expect your
		768	standalone program to act like a perl interpreter.
677		769
678	=item C<--static>	770	=item C<--static>
679		771
680	Add C<-static> to F<bundle.ldopts>, which means a fully static (if	772	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
681	supported by the OS) executable will be created. This is not immensely	773	supported by the OS) executable will be created. This is not immensely
…		…
809	=item C<STATICPERL>	901	=item C<STATICPERL>
810		902
811	The directory where staticperl stores all its files	903	The directory where staticperl stores all its files
812	(default: F<~/.staticperl>).	904	(default: F<~/.staticperl>).
813		905
		906	=item C<DLCACHE>
		907
		908	The path to a directory (will be created if it doesn't exist) where
		909	downloaded perl sources are being cached, to avoid downloading them
		910	again. The default is empty, which means there is no cache.
		911
		912	=item C<PERL_VERSION>
		913
		914	The perl version to install - default is currently C<5.12.3>, but C<5.8.9>
		915	is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is
		916	about as big as 5.12.3).
		917
814	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...	918	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...
815		919
816	Usually set to C<1> to make modules "less inquisitive" during their	920	Usually set to C<1> to make modules "less inquisitive" during their
817	installation, you can set any environment variable you want - some modules	921	installation. You can set (and export!) any environment variable you want
818	(such as L<Coro> or L<EV>) use environment variables for further tweaking.	922	- some modules (such as L<Coro> or L<EV>) use environment variables for
819		923	further tweaking.
820	=item C<PERL_VERSION>
821
822	The perl version to install - default is currently C<5.12.2>, but C<5.8.9>
823	is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is
824	about as big as 5.12.2).
825		924
826	=item C<PERL_PREFIX>	925	=item C<PERL_PREFIX>
827		926
828	The prefix where perl gets installed (default: F<$STATICPERL/perl>),	927	The directory where perl gets installed (default: F<$STATICPERL/perl>),
829	i.e. where the F<bin> and F<lib> subdirectories will end up.	928	i.e. where the F<bin> and F<lib> subdirectories will end up. Previous
		929	contents will be removed on installation.
830		930
831	=item C<PERL_CONFIGURE>	931	=item C<PERL_CONFIGURE>
832		932
833	Additional Configure options - these are simply passed to the perl	933	Additional Configure options - these are simply passed to the perl
834	Configure script. For example, if you wanted to enable dynamic loading,	934	Configure script. For example, if you wanted to enable dynamic loading,
…		…
850	F<~/.staticperlrc> to override them.	950	F<~/.staticperlrc> to override them.
851		951
852	Most of the variables override (or modify) the corresponding F<Configure>	952	Most of the variables override (or modify) the corresponding F<Configure>
853	variable, except C<PERL_CCFLAGS>, which gets appended.	953	variable, except C<PERL_CCFLAGS>, which gets appended.
854		954
		955	The default for C<PERL_OPTIMIZE> is C<-Os> (assuming gcc), and for
		956	C<PERL_LIBS> is C<-lm -lcrypt>, which should be good for most (but not
		957	all) systems.
		958
		959	For other compilers or more customised optimisation settings, you need to
		960	adjust these, e.g. in your F<~/.staticperlrc>.
		961
		962	With gcc on x86 and amd64, you can get more space-savings by using:
		963
		964	-Os -ffunction-sections -fdata-sections -finline-limit=8 -mpush-args
		965	-mno-inline-stringops-dynamically -mno-align-stringops
		966
		967	And on x86 and pentium3 and newer (basically everything you might ever
		968	want to run on), adding these is even better for space-savings (use
		969	-mtune=core2 or something newer for much faster code, too):
		970
		971	-fomit-frame-pointer -march=pentium3 -mtune=i386
		972
855	=back	973	=back
856		974
857	=head4 Variables you probably I<do not want> to override	975	=head4 Variables you probably I<do not want> to override
858		976
859	=over 4	977	=over 4
…		…
877	=head3 OVERRIDABLE HOOKS	995	=head3 OVERRIDABLE HOOKS
878		996
879	In addition to environment variables, it is possible to provide some	997	In addition to environment variables, it is possible to provide some
880	shell functions that are called at specific times. To provide your own	998	shell functions that are called at specific times. To provide your own
881	commands, just define the corresponding function.	999	commands, just define the corresponding function.
		1000
		1001	The actual order in which hooks are invoked during a full install
		1002	from scratch is C<preconfigure>, C<patchconfig>, C<postconfigure>,
		1003	C<postbuild>, C<postinstall>.
882		1004
883	Example: install extra modules from CPAN and from some directories	1005	Example: install extra modules from CPAN and from some directories
884	at F<staticperl install> time.	1006	at F<staticperl install> time.
885		1007
886	postinstall() {	1008	postinstall() {
…		…
893		1015
894	=over 4	1016	=over 4
895		1017
896	=item preconfigure	1018	=item preconfigure
897		1019
898	Called just before running F<./Configur> in the perl source	1020	Called just before running F<./Configure> in the perl source
899	directory. Current working directory is the perl source directory.	1021	directory. Current working directory is the perl source directory.
900		1022
901	This can be used to set any C<PERL_xxx> variables, which might be costly	1023	This can be used to set any C<PERL_xxx> variables, which might be costly
902	to compute.	1024	to compute.
903		1025
		1026	=item patchconfig
		1027
		1028	Called after running F<./Configure> in the perl source directory to create
		1029	F<./config.sh>, but before running F<./Configure -S> to actually apply the
		1030	config. Current working directory is the perl source directory.
		1031
		1032	Can be used to tailor/patch F<config.sh> or do any other modifications.
		1033
904	=item postconfigure	1034	=item postconfigure
905		1035
906	Called after configuring, but before building perl. Current working	1036	Called after configuring, but before building perl. Current working
907	directory is the perl source directory.	1037	directory is the perl source directory.
908
909	Could be used to tailor/patch config.sh (followed by F<sh Configure -S>)
910	or do any other modifications.
911		1038
912	=item postbuild	1039	=item postbuild
913		1040
914	Called after building, but before installing perl. Current working	1041	Called after building, but before installing perl. Current working
915	directory is the perl source directory.	1042	directory is the perl source directory.
…		…
953	A header file that contains the prototypes of the few symbols "exported"	1080	A header file that contains the prototypes of the few symbols "exported"
954	by bundle.c, and also exposes the perl headers to the application.	1081	by bundle.c, and also exposes the perl headers to the application.
955		1082
956	=over 4	1083	=over 4
957		1084
958	=item staticperl_init ()	1085	=item staticperl_init (xs_init = 0)
959		1086
960	Initialises the perl interpreter. You can use the normal perl functions	1087	Initialises the perl interpreter. You can use the normal perl functions
961	after calling this function, for example, to define extra functions or	1088	after calling this function, for example, to define extra functions or
962	to load a .pm file that contains some initialisation code, or the main	1089	to load a .pm file that contains some initialisation code, or the main
963	program function:	1090	program function:
…		…
970	}	1097	}
971		1098
972	static void	1099	static void
973	run_myapp(void)	1100	run_myapp(void)
974	{	1101	{
975	staticperl_init ();	1102	staticperl_init (0);
976	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");	1103	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
977	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"	1104	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"
978	}	1105	}
979		1106
		1107	When your bootcode already wants to access some XS functions at
		1108	compiletime, then you need to supply an C<xs_init> function pointer that
		1109	is called as soon as perl is initialised enough to define XS functions,
		1110	but before the preamble code is executed:
		1111
		1112	static void
		1113	xs_init (pTHX)
		1114	{
		1115	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
		1116	}
		1117
		1118	static void
		1119	run_myapp(void)
		1120	{
		1121	staticperl_init (xs_init);
		1122	}
		1123
		1124	=item staticperl_cleanup ()
		1125
		1126	In the unlikely case that you want to destroy the perl interpreter, here
		1127	is the corresponding function.
		1128
980	=item staticperl_xs_init (pTHX)	1129	=item staticperl_xs_init (pTHX)
981		1130
982	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in	1131	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in
983	which case you do not want to use C<staticperl_init> but call them on your	1132	which case you do not want to use C<staticperl_init> but call them on your
984	own.	1133	own.
985		1134
986	Then you need this function - either pass it directly as the C<xs_init>	1135	Then you need this function - either pass it directly as the C<xs_init>
987	function to C<perl_parse>, or call it from your own C<xs_init> function.	1136	function to C<perl_parse>, or call it as one of the first things from your
988		1137	own C<xs_init> function.
989	=item staticperl_cleanup ()
990
991	In the unlikely case that you want to destroy the perl interpreter, here
992	is the corresponding function.
993		1138
994	=item PerlInterpreter *staticperl	1139	=item PerlInterpreter *staticperl
995		1140
996	The perl interpreter pointer used by staticperl. Not normally so useful,	1141	The perl interpreter pointer used by staticperl. Not normally so useful,
997	but there it is.	1142	but there it is.
…		…
1010		1155
1011	=back	1156	=back
1012		1157
1013	=head1 RUNTIME FUNCTIONALITY	1158	=head1 RUNTIME FUNCTIONALITY
1014		1159
1015	Binaries created with C<mkbundle>/C<mkperl> contain extra functions, which	1160	Binaries created with C<mkbundle>/C<mkperl> contain extra functionality,
1016	are required to access the bundled perl sources, but might be useful for	1161	mostly related to the extra files bundled in the binary (the virtual
1017	other purposes.	1162	filesystem). All of this data is statically compiled into the binary, and
		1163	accessing means copying it from a read-only section of your binary. Data
		1164	pages in this way is usually freed by the operating system, as it isn't
		1165	use more the onace.
		1166
		1167	=head2 VIRTUAL FILESYSTEM
		1168
		1169	Every bundle has a virtual filesystem. The only information stored in it
		1170	is the path and contents of each file that was bundled.
		1171
		1172	=head3 LAYOUT
		1173
		1174	Any path starting with an ampersand (F<&>) or exclamation mark (F<!>) are
		1175	reserved by F<staticperl>. They must only be used as described in this
		1176	section.
		1177
		1178	=over 4
		1179
		1180	=item !
		1181
		1182	All files that typically cannot be loaded from memory (such as dynamic
		1183	objects or shared libraries), but have to reside in the filesystem, are
		1184	prefixed with F<!>. Typically these files get written out to some
		1185	(semi-)temporary directory shortly after program startup, or before being
		1186	used.
		1187
		1188	=item !boot
		1189
		1190	The bootstrap file, if specified during bundling.
		1191
		1192	=item !auto/
		1193
		1194	Shared objects or dlls corresponding to dynamically-linked perl extensions
		1195	are stored with an F<!auto/> prefix.
		1196
		1197	=item !lib/
		1198
		1199	External shared libraries are stored in this directory.
		1200
		1201	=item any letter
		1202
		1203	Any path starting with a letter is a perl library file. For example,
		1204	F<Coro/AIO.pm> corresponds to the file loaded by C<use Coro::AIO>, and
		1205	F<Coro/jit.pl> corresponds to C<require "Coro/jit.pl">.
		1206
		1207	Obviously, module names shouldn't start with any other characters than
		1208	letters :)
		1209
		1210	=back
		1211
		1212	=head3 FUNCTIONS
		1213
		1214	=over 4
		1215
		1216	=item $file = static::find $path
		1217
		1218	Returns the data associated with the given C<$path>
		1219	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>).
		1220
		1221	Returns C<undef> if the file isn't embedded.
		1222
		1223	=item @paths = static::list
		1224
		1225	Returns the list of all paths embedded in this binary.
		1226
		1227	=back
		1228
		1229	=head2 EXTRA FEATURES
1018		1230
1019	In addition, for the embedded loading of perl files to work, F<staticperl>	1231	In addition, for the embedded loading of perl files to work, F<staticperl>
1020	overrides the C<@INC> array.	1232	overrides the C<@INC> array.
1021
1022	=over 4
1023
1024	=item $file = staticperl::find $path
1025
1026	Returns the data associated with the given C<$path>
1027	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>), which is basically
1028	the UNIX path relative to the perl library directory.
1029
1030	Returns C<undef> if the file isn't embedded.
1031
1032	=item @paths = staticperl::list
1033
1034	Returns the list of all paths embedded in this binary.
1035
1036	=back
1037		1233
1038	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT	1234	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
1039		1235
1040	To make truly static (Linux-) libraries, you might want to have a look at	1236	To make truly static (Linux-) libraries, you might want to have a look at
1041	buildroot (L<http://buildroot.uclibc.org/>).	1237	buildroot (L<http://buildroot.uclibc.org/>).
…		…
1050	good experiences with GCC 4.4.x but not GCC 4.5.	1246	good experiences with GCC 4.4.x but not GCC 4.5.
1051		1247
1052	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections	1248	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections
1053	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>	1249	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>
1054	doesn't decrease codesize much, but it makes the file much more	1250	doesn't decrease codesize much, but it makes the file much more
1055	compressible.	1251	compressible (and the execution a lot slower...).
1056		1252
1057	If you don't need Coro or threads, you can go with "linuxthreads.old" (or	1253	If you don't need Coro or threads, you can go with "linuxthreads.old" (or
1058	no thread support). For Coro, it is highly recommended to switch to a	1254	no thread support). For Coro, it is highly recommended to switch to a
1059	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201	1255	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201
1060	snapshot) and enable NPTL, otherwise Coro needs to be configured with the	1256	snapshot) and enable NPTL, otherwise Coro needs to be configured with the
…		…
1062	twice the address space needed for stacks).	1258	twice the address space needed for stacks).
1063		1259
1064	If you use C<linuxthreads.old>, then you should also be aware that	1260	If you use C<linuxthreads.old>, then you should also be aware that
1065	uClibc shares C<errno> between all threads when statically linking. See	1261	uClibc shares C<errno> between all threads when statically linking. See
1066	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a	1262	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a
1067	workaround (And L<https://bugs.uclibc.org/2089> for discussion).	1263	workaround (and L<https://bugs.uclibc.org/2089> for discussion).
1068		1264
1069	C<ccache> support is also recommended, especially if you want	1265	C<ccache> support is also recommended, especially if you want
1070	to play around with buildroot options. Enabling the C<miniperl>	1266	to play around with buildroot options. Enabling the C<miniperl>
1071	package will probably enable all options required for a successful	1267	package will probably enable all options required for a successful
1072	perl build. F<staticperl> itself additionally needs either C<wget>	1268	perl build. F<staticperl> itself additionally needs either C<wget>
…		…
1080	it from working properly in a chroot - either use dash (and link it to	1276	it from working properly in a chroot - either use dash (and link it to
1081	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's	1277	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's
1082	built-in ash shell.	1278	built-in ash shell.
1083		1279
1084	Finally, you need F</dev/null> inside the chroot for many scripts to work	1280	Finally, you need F</dev/null> inside the chroot for many scripts to work
1085	- F<cp /dev/null output/target/dev> or bind-mounting your F</dev> will	1281	- either F<cp /dev/null output/target/dev> or bind-mounting your F</dev>
1086	both provide this.	1282	will provide this.
1087		1283
1088	After you have compiled and set up your buildroot target, you can copy	1284	After you have compiled and set up your buildroot target, you can copy
1089	F<staticperl> from the C<App::Staticperl> distribution or from your	1285	F<staticperl> from the C<App::Staticperl> distribution or from your
1090	perl f<bin> directory (if you installed it) into the F<output/target>	1286	perl F<bin> directory (if you installed it) into the F<output/target>
1091	filesystem, chroot inside and run it.	1287	filesystem, chroot inside and run it.
1092		1288
1093	=head1 RECIPES / SPECIFIC MODULES	1289	=head1 RECIPES / SPECIFIC MODULES
1094		1290
1095	This section contains some common(?) recipes and information about	1291	This section contains some common(?) recipes and information about
…		…
1104		1300
1105	Some functionality in the utf8 module, such as swash handling (used	1301	Some functionality in the utf8 module, such as swash handling (used
1106	for unicode character ranges in regexes) is implemented in the	1302	for unicode character ranges in regexes) is implemented in the
1107	C<"utf8_heavy.pl"> library:	1303	C<"utf8_heavy.pl"> library:
1108		1304
1109	-M'"utf8_heavy.pl"'	1305	-Mutf8_heavy.pl
1110		1306
1111	Many Unicode properties in turn are defined in separate modules,	1307	Many Unicode properties in turn are defined in separate modules,
1112	such as C<"unicore/Heavy.pl"> and more specific data tables such as	1308	such as C<"unicore/Heavy.pl"> and more specific data tables such as
1113	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables	1309	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables
1114	are big (7MB uncompressed, although F<staticperl> contains special	1310	are big (7MB uncompressed, although F<staticperl> contains special
1115	handling for those files), so including them on demand by your application	1311	handling for those files), so including them on demand by your application
1116	only might pay off.	1312	only might pay off.
1117		1313
1118	To simply include the whole unicode database, use:	1314	To simply include the whole unicode database, use:
1119		1315
1120	--incglob '/unicore/*.pl'	1316	--incglob '/unicore/**.pl'
1121		1317
1122	=item AnyEvent	1318	=item AnyEvent
1123		1319
1124	AnyEvent needs a backend implementation that it will load in a delayed	1320	AnyEvent needs a backend implementation that it will load in a delayed
1125	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice	1321	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice
…		…
1133	C<"AnyEvent/Util/uts46data.pl">.	1329	C<"AnyEvent/Util/uts46data.pl">.
1134		1330
1135	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include	1331	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
1136	everything.	1332	everything.
1137		1333
		1334	=item Cairo
		1335
		1336	See Glib, same problem, same solution.
		1337
1138	=item Carp	1338	=item Carp
1139		1339
1140	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1340	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
1141	perl 5.12.2 (maybe earlier), this dependency no longer exists.	1341	perl 5.12.2 (maybe earlier), this dependency no longer exists.
1142		1342
1143	=item Config	1343	=item Config
1144		1344
1145	The F<perl -V> switch (as well as many modules) needs L<Config>, which in	1345	The F<perl -V> switch (as well as many modules) needs L<Config>, which in
1146	turn might need L<"Config_heavy.pl">. Including the latter gives you	1346	turn might need L<"Config_heavy.pl">. Including the latter gives you
1147	both.	1347	both.
		1348
		1349	=item Glib
		1350
		1351	Glib literally requires Glib to be installed already to build - it tries
		1352	to fake this by running Glib out of the build directory before being
		1353	built. F<staticperl> tries to work around this by forcing C<MAN1PODS> and
		1354	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
		1355
		1356	=item Gtk2
		1357
		1358	See Pango, same problems, same solution.
		1359
		1360	=item Net::SSLeay
		1361
		1362	This module hasn't been significantly updated since OpenSSL is called
		1363	OpenSSL, and fails to properly link against dependent libraries, most
		1364	commonly, it forgets to specify -ldl when linking.
		1365
		1366	On GNU/Linux systems this usually goes undetected, as perl usually links
		1367	against -ldl itself and OpenSSL just happens to pick it up that way, by
		1368	chance.
		1369
		1370	For static builds, you either have to configure -ldl manually, or you
		1371	cna use the following snippet in your C<postinstall> hook which patches
		1372	Net::SSLeay after installation, which happens to work most of the time:
		1373
		1374	postinstall() {
		1375	# first install it
		1376	instcpan Net::SSLeay
		1377	# then add -ldl for future linking
		1378	chmod u+w "$PERL_PREFIX"/lib/auto/Net/SSLeay/extralibs.ld
		1379	echo " -ldl" >>"$PERL_PREFIX"/lib/auto/Net/SSLeay/extralibs.ld
		1380	}
		1381
		1382	=item Pango
		1383
		1384	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
		1385	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>
		1386	tries to patch L<ExtUtils::MM_Unix> to route around Pango.
1148		1387
1149	=item Term::ReadLine::Perl	1388	=item Term::ReadLine::Perl
1150		1389
1151	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.	1390	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
1152		1391
…		…
1203	do	1442	do
1204	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"	1443	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
1205	done	1444	done
1206	}	1445	}
1207		1446
1208	This mostly gains space when linking staticaly, as the functions will	1447	This mostly gains space when linking statically, as the functions will
1209	likely not be linked in. The gain for dynamically-linked binaries is	1448	likely not be linked in. The gain for dynamically-linked binaries is
1210	smaller.	1449	smaller.
1211		1450
1212	Also, this leaves C<gethostbyname> in - not only is it actually used	1451	Also, this leaves C<gethostbyname> in - not only is it actually used
1213	often, the L<Socket> module also exposes it, so leaving it out usually	1452	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.29 by root, Wed Dec 22 01:23:37 2010 UTC vs. Revision 1.57 by root, Wed Dec 5 15:19:52 2012 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.29 by root, Wed Dec 22 01:23:37 2010 UTC vs.
Revision 1.57 by root, Wed Dec 5 15:19:52 2012 UTC