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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.25 by root, Tue Dec 21 12:59:29 2010 UTC vs.
Revision 1.49 by root, Wed Jul 13 15:23:13 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
…		…
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
…		…
313		326
314	=head3 OPTION PROCESSING	327	=head3 OPTION PROCESSING
315		328
316	All options can be given as arguments on the command line (typically	329	All options can be given as arguments on the command line (typically
317	using long (e.g. C<--verbose>) or short option (e.g. C<-v>) style). Since	330	using long (e.g. C<--verbose>) or short option (e.g. C<-v>) style). Since
318	specifying a lot of modules can make the command line very cumbersome, you	331	specifying a lot of options can make the command line very long and
319	can put all long options into a "bundle specification file" (one option	332	unwieldy, you can put all long options into a "bundle specification file"
320	per line, with or without C<--> prefix) and specify this bundle file	333	(one option per line, with or without C<--> prefix) and specify this
321	instead.	334	bundle file instead.
322		335
323	For example, the command given earlier could also look like this:	336	For example, the command given earlier to link a new F<perl> could also
		337	look like this:
324		338
325	staticperl mkperl httpd.bundle	339	staticperl mkperl httpd.bundle
326		340
327	And all options could be in F<httpd.bundle>:	341	With all options stored in the F<httpd.bundle> file (one option per line,
328		342	everything after the option is an argument):
		343
329	use "Config_heavy.pl"	344	use "Config_heavy.pl"
330	use AnyEvent::Impl::Perl	345	use AnyEvent::Impl::Perl
331	use AnyEvent::HTTPD	346	use AnyEvent::HTTPD
332	use URI::http	347	use URI::http
333	add eg/httpd httpd.pm	348	add eg/httpd httpd.pm
334		349
335	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
336	order given on the command line.	351	order given on the command line.
337		352
338	=head3 PACKAGE SELECTION WORKFLOW	353	=head3 BUNDLE CREATION WORKFLOW / STATICPELR MKBUNDLE OPTIONS
339		354
340	F<staticperl mkbundle> has a number of options to control package	355	F<staticperl mkbundle> works by first assembling a list of candidate
341	selection. This section describes how they interact with each other. Also,	356	files and modules to include, then filtering them by include/exclude
342	since I am still a newbie w.r.t. these issues, maybe future versions of	357	patterns. The remaining modules (together with their direct dependencies,
343	F<staticperl> will change this, so watch out :)	358	such as link libraries and L<AutoLoader> files) are then converted into
		359	bundle files suitable for embedding. F<staticperl mkbundle> can then
		360	optionally build a new perl interpreter or a standalone application.
344		361
345	The idiom "in order" means "in order that they are specified on the
346	commandline". If you use a bundle specification file, then the options
347	will be processed as if they were given in place of the bundle file name.
348
349	=over 4	362	=over 4
350		363
351	=item 1. apply all C<--use>, C<--eval>, C<--add>, C<--addbin> and	364	=item Step 0: Generic argument processing.
352	C<--incglob> options, in order.
353		365
354	In addition, C<--use> and C<--eval> dependencies will be added when the	366	The following options influence F<staticperl mkbundle> itself.
355	options are processed.
356		367
357	=item 2. apply all C<--include> and C<--exclude> options, in order.
358
359	All this step does is potentially reduce the number of files already
360	selected or found in phase 1.
361
362	=item 3. find all modules (== F<.pm> files), gather their static archives
363	(F<.a>) and AutoLoader splitfiles (F<.ix> and F<.al> files), find any
364	extra libraries they need for linking (F<extralibs.ld>) and optionally
365	evaluate any F<.packlist> files.
366
367	This step is required to link against XS extensions and also adds files
368	required for L<AutoLoader> to do it's job.
369
370	=back
371
372	After this, all the files selected for bundling will be read and processed
373	(stripped), the bundle files will be written, and optionally a new F<perl>
374	or application binary will be linked.
375
376	=head3 MKBUNDLE OPTIONS
377
378	=over 4	368	=over 4
379		369
380	=item --verbose \| -v	370	=item C<--verbose> \| C<-v>
381		371
382	Increases the verbosity level by one (the default is C<1>).	372	Increases the verbosity level by one (the default is C<1>).
383		373
384	=item --quiet \| -q	374	=item C<--quiet> \| C<-q>
385		375
386	Decreases the verbosity level by one.	376	Decreases the verbosity level by one.
387		377
		378	=item any other argument
		379
		380	Any other argument is interpreted as a bundle specification file, which
		381	supports all options (without extra quoting), one option per line, in the
		382	format C<option> or C<option argument>. They will effectively be expanded
		383	and processed as if they were directly written on the command line, in
		384	place of the file name.
		385
		386	=back
		387
		388	=item Step 1: gather candidate files and modules
		389
		390	In this step, modules, perl libraries (F<.pl> files) and other files are
		391	selected for inclusion in the bundle. The relevant options are executed
		392	in order (this makes a difference mostly for C<--eval>, which can rely on
		393	earlier C<--use> options to have been executed).
		394
		395	=over 4
		396
		397	=item C<--use> F<module> \| C<-M>F<module>
		398
		399	Include the named module or perl library and trace direct
		400	dependencies. This is done by loading the module in a subprocess and
		401	tracing which other modules and files it actually loads.
		402
		403	Example: include AnyEvent and AnyEvent::Impl::Perl.
		404
		405	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
		406
		407	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
		408	maybe other weirdly named files. To support this, the C<--use> option
		409	actually tries to do what you mean, depending on the string you specify:
		410
		411	=over 4
		412
		413	=item a possibly valid module name, e.g. F<common::sense>, F<Carp>,
		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
		446
		447	Example: include the required files for F<perl -V> to work in all its
		448	glory (F<Config.pm> is included automatically by the dependency tracker).
		449
		450	# shell command
		451	staticperl mkbundle -MConfig_heavy.pl
		452
		453	# bundle specification file
		454	use Config_heavy.pl
		455
		456	The C<-M>module syntax is included as a convenience that might be easier
		457	to remember than C<--use> - it's the same switch as perl itself uses
		458	to load modules. Or maybe it confuses people. Time will tell. Or maybe
		459	not. Sigh.
		460
		461	=item C<--eval> "perl code" \| C<-e> "perl code"
		462
		463	Sometimes it is easier (or necessary) to specify dependencies using perl
		464	code, or maybe one of the modules you use need a special use statement. In
		465	that case, you can use C<--eval> to execute some perl snippet or set some
		466	variables or whatever you need. All files C<require>'d or C<use>'d while
		467	executing the snippet are included in the final bundle.
		468
		469	Keep in mind that F<mkbundle> will not import any symbols from the modules
		470	named by the C<--use> option, so do not expect the symbols from modules
		471	you C<--use>'d earlier on the command line to be available.
		472
		473	Example: force L<AnyEvent> to detect a backend and therefore include it
		474	in the final bundle.
		475
		476	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
		477
		478	# or like this
		479	staticperl mkbundle -MAnyEvent --eval 'AnyEvent::detect'
		480
		481	Example: use a separate "bootstrap" script that C<use>'s lots of modules
		482	and also include this in the final bundle, to be executed automatically
		483	when the interpreter is initialised.
		484
		485	staticperl mkbundle --eval 'do "bootstrap"' --boot bootstrap
		486
		487	=item C<--boot> F<filename>
		488
		489	Include the given file in the bundle and arrange for it to be
		490	executed (using C<require>) before the main program when the new perl
		491	is initialised. This can be used to modify C<@INC> or do similar
		492	modifications before the perl interpreter executes scripts given on the
		493	command line (or via C<-e>). This works even in an embedded interpreter -
		494	the file will be executed during interpreter initialisation in that case.
		495
		496	=item C<--incglob> pattern
		497
		498	This goes through all standard library directories and tries to match any
		499	F<.pm> and F<.pl> files against the extended glob pattern (see below). If
		500	a file matches, it is added. The pattern is matched against the full path
		501	of the file (sans the library directory prefix), e.g. F<Sys/Syslog.pm>.
		502
		503	This is very useful to include "everything":
		504
		505	--incglob '*'
		506
		507	It is also useful for including perl libraries, or trees of those, such as
		508	the unicode database files needed by some perl built-ins, the regex engine
		509	and other modules.
		510
		511	--incglob '/unicore/**.pl'
		512
		513	=item C<--add> F<file> \| C<--add> "F<file> alias"
		514
		515	Adds the given (perl) file into the bundle (and optionally call it
		516	"alias"). The F<file> is either an absolute path or a path relative to the
		517	current directory. If an alias is specified, then this is the name it will
		518	use for C<@INC> searches, otherwise the path F<file> will be used as the
		519	internal name.
		520
		521	This switch is used to include extra files into the bundle.
		522
		523	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
		524	when creating the bundle.
		525
		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'"
		535
		536	Example: add local files as extra modules in the bundle.
		537
		538	# specification file
		539	add file1 myfiles/file1.pm
		540	add file2 myfiles/file2.pm
		541	add file3 myfiles/file3.pl
		542
		543	# then later, in perl, use
		544	use myfiles::file1;
		545	require myfiles::file2;
		546	my $res = do "myfiles/file3.pl";
		547
		548	=item C<--binadd> F<file> \| C<--add> "F<file> alias"
		549
		550	Just like C<--add>, except that it treats the file as binary and adds it
		551	without any postprocessing (perl files might get stripped to reduce their
		552	size).
		553
		554	If you specify an alias you should probably add a C</> prefix to avoid
		555	clashing with embedded perl files (whose paths never start with C</>),
		556	and/or use a special directory prefix, such as C</res/name>.
		557
		558	You can later get a copy of these files by calling C<static::find
		559	"alias">.
		560
		561	An alternative way to embed binary files is to convert them to perl and
		562	use C<do> to get the contents - this method is a bit cumbersome, but works
		563	both inside and outside of a staticperl bundle, without extra ado:
		564
		565	# a "binary" file, call it "bindata.pl"
		566	<<'SOME_MARKER'
		567	binary data NOT containing SOME_MARKER
		568	SOME_MARKER
		569
		570	# load the binary
		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
		589
		590	=back
		591
		592	=item Step 2: filter all files using C<--include> and C<--exclude> options.
		593
		594	After all candidate files and modules are added, they are I<filtered>
		595	by a combination of C<--include> and C<--exclude> patterns (there is an
		596	implicit C<--include *> at the end, so if no filters are specified, all
		597	files are included).
		598
		599	All that this step does is potentially reduce the number of files that are
		600	to be included - no new files are added during this step.
		601
		602	=over 4
		603
		604	=item C<--include> pattern \| C<-i> pattern \| C<--exclude> pattern \| C<-x> pattern
		605
		606	These specify an include or exclude pattern to be applied to the candidate
		607	file list. An include makes sure that the given files will be part of the
		608	resulting file set, an exclude will exclude remaining files. The patterns
		609	are "extended glob patterns" (see below).
		610
		611	The patterns are applied "in order" - files included via earlier
		612	C<--include> specifications cannot be removed by any following
		613	C<--exclude>, and likewise, and file excluded by an earlier C<--exclude>
		614	cannot be added by any following C<--include>.
		615
		616	For example, to include everything except C<Devel> modules, but still
		617	include F<Devel::PPPort>, you could use this:
		618
		619	--incglob '' -i '/Devel/PPPort.pm' -x '/Devel/*'
		620
		621	=back
		622
		623	=item Step 3: add any extra or "hidden" dependencies.
		624
		625	F<staticperl> currently knows about three extra types of depdendencies
		626	that are added automatically. Only one (F<.packlist> files) is currently
		627	optional and can be influenced, the others are always included:
		628
		629	=over 4
		630
		631	=item C<--usepacklists>
		632
		633	Read F<.packlist> files for each distribution that happens to match a
		634	module name you specified. Sounds weird, and it is, so expect semantics to
		635	change somehow in the future.
		636
		637	The idea is that most CPAN distributions have a F<.pm> file that matches
		638	the name of the distribution (which is rather reasonable after all).
		639
		640	If this switch is enabled, then if any of the F<.pm> files that have been
		641	selected match an install distribution, then all F<.pm>, F<.pl>, F<.al>
		642	and F<.ix> files installed by this distribution are also included.
		643
		644	For example, using this switch, when the L<URI> module is specified, then
		645	all L<URI> submodules that have been installed via the CPAN distribution
		646	are included as well, so you don't have to manually specify them.
		647
		648	=item L<AutoLoader> splitfiles
		649
		650	Some modules use L<AutoLoader> - less commonly (hopefully) used functions
		651	are split into separate F<.al> files, and an index (F<.ix>) file contains
		652	the prototypes.
		653
		654	Both F<.ix> and F<.al> files will be detected automatically and added to
		655	the bundle.
		656
		657	=item link libraries (F<.a> files)
		658
		659	Modules using XS (or any other non-perl language extension compiled at
		660	installation time) will have a static archive (typically F<.a>). These
		661	will automatically be added to the linker options in F<bundle.ldopts>.
		662
		663	Should F<staticperl> find a dynamic link library (typically F<.so>) it
		664	will warn about it - obviously this shouldn't happen unless you use
		665	F<staticperl> on the wrong perl, or one (probably wrongly) configured to
		666	use dynamic loading.
		667
		668	=item extra libraries (F<extralibs.ld>)
		669
		670	Some modules need linking against external libraries - these are found in
		671	F<extralibs.ld> and added to F<bundle.ldopts>.
		672
		673	=back
		674
		675	=item Step 4: write bundle files and optionally link a program
		676
		677	At this point, the select files will be read, processed (stripped) and
		678	finally the bundle files get written to disk, and F<staticperl mkbundle>
		679	is normally finished. Optionally, it can go a step further and either link
		680	a new F<perl> binary with all selected modules and files inside, or build
		681	a standalone application.
		682
		683	Both the contents of the bundle files and any extra linking is controlled
		684	by these options:
		685
		686	=over 4
		687
388	=item --strip none\|pod\|ppi	688	=item C<--strip> C<none>\|C<pod>\|C<ppi>
389		689
390	Specify the stripping method applied to reduce the file of the perl	690	Specify the stripping method applied to reduce the file of the perl
391	sources included.	691	sources included.
392		692
393	The default is C<pod>, which uses the L<Pod::Strip> module to remove all	693	The default is C<pod>, which uses the L<Pod::Strip> module to remove all
…		…
404	Last not least, if you need accurate line numbers in error messages,	704	Last not least, if you need accurate line numbers in error messages,
405	or in the unlikely case where C<pod> is too slow, or some module gets	705	or in the unlikely case where C<pod> is too slow, or some module gets
406	mistreated, you can specify C<none> to not mangle included perl sources in	706	mistreated, you can specify C<none> to not mangle included perl sources in
407	any way.	707	any way.
408		708
409	=item --perl	709	=item C<--perl>
410		710
411	After writing out the bundle files, try to link a new perl interpreter. It	711	After writing out the bundle files, try to link a new perl interpreter. It
412	will be called F<perl> and will be left in the current working	712	will be called F<perl> and will be left in the current working
413	directory. The bundle files will be removed.	713	directory. The bundle files will be removed.
414		714
415	This switch is automatically used when F<staticperl> is invoked with the	715	This switch is automatically used when F<staticperl> is invoked with the
416	C<mkperl> command (instead of C<mkbundle>):	716	C<mkperl> command instead of C<mkbundle>.
417		717
418	# build a new ./perl with only common::sense in it - very small :)	718	Example: build a new F<./perl> binary with only L<common::sense> inside -
		719	it will be even smaller than the standard perl interpreter as none of the
		720	modules of the base distribution (such as L<Fcntl>) will be included.
		721
419	staticperl mkperl -Mcommon::sense	722	staticperl mkperl -Mcommon::sense
420		723
421	=item --app name	724	=item C<--app> F<name>
422		725
423	After writing out the bundle files, try to link a new standalone	726	After writing out the bundle files, try to link a new standalone
424	program. It will be called C<name>, and the bundle files get removed after	727	program. It will be called C<name>, and the bundle files get removed after
425	linking it.	728	linking it.
		729
		730	This switch is automatically used when F<staticperl> is invoked with the
		731	C<mkapp> command instead of C<mkbundle>.
426		732
427	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
428	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 -
429	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
430	exit.	736	exit.
431		737
432	This switch is automatically used when F<staticperl> is invoked with the	738	This means that, by default, it will do nothing but burn a few CPU cycles
433	C<mkapp> command (instead of C<mkbundle>):
434
435	To let it 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
436	the C<--boot> option.	740	the C<--boot> option.
437		741
438	Example: create a standalone perl binary that will execute F<appfile> when	742	Example: create a standalone perl binary called F<./myexe> that will
439	it is started.	743	execute F<appfile> when it is started.
440		744
441	staticperl mkbundle --app myexe --boot appfile	745	staticperl mkbundle --app myexe --boot appfile
442		746
443	=item --use module \| -Mmodule	747	=item C<--ignore-env>
444		748
445	Include the named module and all direct dependencies. This is done by	749	Generates extra code to unset some environment variables before
446	C<require>'ing the module in a subprocess and tracing which other modules	750	initialising/running perl. Perl supports a lot of environment variables
447	and files it actually loads. If the module uses L<AutoLoader>, then all	751	that might alter execution in ways that might be undesirablre for
448	splitfiles will be included as well.	752	standalone applications, and this option removes those known to cause
		753	trouble.
449		754
450	Example: include AnyEvent and AnyEvent::Impl::Perl.	755	Specifically, these are removed:
451		756
452	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl	757	C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause underaible
		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.
453		761
454	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or	762	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
455	maybe other weirdly named files. To do that, you need to quote the name in	763	startup code used by F<staticperl> overrides C<@INC> in all cases.
456	single or double quotes. When given on the command line, you probably need
457	to quote once more to avoid your shell interpreting it. Common cases that
458	need this are F<Config_heavy.pl> and F<utf8_heavy.pl>.
459		764
460	Example: include the required files for F<perl -V> to work in all its	765	This option will not make your program more secure (unless you are
461	glory (F<Config.pm> is included automatically by this).	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.
462		769
463	# bourne shell
464	staticperl mkbundle --use '"Config_heavy.pl"'
465
466	# bundle specification file
467	use "Config_heavy.pl"
468
469	The C<-Mmodule> syntax is included as an alias that might be easier to
470	remember than C<use>. Or maybe it confuses people. Time will tell. Or
471	maybe not. Argh.
472
473	=item --eval "perl code" \| -e "perl code"
474
475	Sometimes it is easier (or necessary) to specify dependencies using perl
476	code, or maybe one of the modules you use need a special use statement. In
477	that case, you can use C<eval> to execute some perl snippet or set some
478	variables or whatever you need. All files C<require>'d or C<use>'d in the
479	script are included in the final bundle.
480
481	Keep in mind that F<mkbundle> will only C<require> the modules named
482	by the C<--use> option, so do not expect the symbols from modules you
483	C<--use>'d earlier on the command line to be available.
484
485	Example: force L<AnyEvent> to detect a backend and therefore include it
486	in the final bundle.
487
488	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
489
490	# or like this
491	staticperl mkbundle -MAnyEvent --eval 'use AnyEvent; AnyEvent::detect'
492
493	Example: use a separate "bootstrap" script that C<use>'s lots of modules
494	and include this in the final bundle, to be executed automatically.
495
496	staticperl mkbundle --eval 'do "bootstrap"' --boot bootstrap
497
498	=item --boot filename
499
500	Include the given file in the bundle and arrange for it to be executed
501	(using a C<require>) before anything else when the new perl is
502	initialised. This can be used to modify C<@INC> or anything else before
503	the perl interpreter executes scripts given on the command line (or via
504	C<-e>). This works even in an embedded interpreter.
505
506	=item --usepacklist
507
508	Read F<.packlist> files for each distribution that happens to match a
509	module name you specified. Sounds weird, and it is, so expect semantics to
510	change somehow in the future.
511
512	The idea is that most CPAN distributions have a F<.pm> file that matches
513	the name of the distribution (which is rather reasonable after all).
514
515	If this switch is enabled, then if any of the F<.pm> files that have been
516	selected match an install distribution, then all F<.pm>, F<.pl>, F<.al>
517	and F<.ix> files installed by this distribution are also included.
518
519	For example, using this switch, when the L<URI> module is specified, then
520	all L<URI> submodules that have been installed via the CPAN distribution
521	are included as well, so you don't have to manually specify them.
522
523	=item --incglob pattern
524
525	This goes through all library directories and tries to match any F<.pm>
526	and F<.pl> files against the extended glob pattern (see below). If a file
527	matches, it is added. This switch will automatically detect L<AutoLoader>
528	files and the required link libraries for XS modules, but it will I<not>
529	scan the file for dependencies (at the moment).
530
531	This is mainly useful to include "everything":
532
533	--incglob '*'
534
535	Or to include perl libraries, or trees of those, such as the unicode
536	database files needed by many other modules:
537
538	--incglob '/unicore/**.pl'
539
540	=item --add file \| --add "file alias"
541
542	Adds the given (perl) file into the bundle (and optionally call it
543	"alias"). This is useful to include any custom files into the bundle.
544
545	Example: embed the file F<httpd> as F<httpd.pm> when creating the bundle.
546
547	staticperl mkperl --add "httpd httpd.pm"
548
549	It is also a great way to add any custom modules:
550
551	# specification file
552	add file1 myfiles/file1
553	add file2 myfiles/file2
554	add file3 myfiles/file3
555
556	=item --binadd file \| --add "file alias"
557
558	Just like C<--add>, except that it treats the file as binary and adds it
559	without any processing.
560
561	You should probably add a C</> prefix to avoid clashing with embedded
562	perl files (whose paths do not start with C</>), and/or use a special
563	directory, such as C</res/name>.
564
565	You can later get a copy of these files by calling C<staticperl::find
566	"alias">.
567
568	=item --include pattern \| -i pattern \| --exclude pattern \| -x pattern
569
570	These two options define an include/exclude filter that is used after all
571	files selected by the other options have been found. Each include/exclude
572	is applied to all files found so far - an include makes sure that the
573	given files will be part of the resulting file set, an exclude will
574	exclude files. The patterns are "extended glob patterns" (see below).
575
576	For example, to include everything, except C<Devel> modules, but still
577	include F<Devel::PPPort>, you could use this:
578
579	--incglob '' -i '/Devel/PPPort.pm' -x '/Devel/*'
580
581	=item --static	770	=item C<--static>
582		771
583	When C<--perl> is also given, link statically instead of dynamically. The	772	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
		773	supported by the OS) executable will be created. This is not immensely
		774	useful when just creating the bundle files, but is most useful when
		775	linking a binary with the C<--perl> or C<--app> options.
		776
584	default is to link the new perl interpreter fully dynamic (that means all	777	The default is to link the new binary dynamically (that means all perl
585	perl modules are linked statically, but all external libraries are still	778	modules are linked statically, but all external libraries are still
586	referenced dynamically).	779	referenced dynamically).
587		780
588	Keep in mind that Solaris doesn't support static linking at all, and	781	Keep in mind that Solaris doesn't support static linking at all, and
589	systems based on GNU libc don't really support it in a usable fashion	782	systems based on GNU libc don't really support it in a very usable
590	either. Try uClibc if you want to create fully statically linked	783	fashion either. Try uClibc if you want to create fully statically linked
591	executables, or try the C<--staticlibs> option to link only some libraries	784	executables, or try the C<--staticlib> option to link only some libraries
592	statically.	785	statically.
593		786
594	=item --staticlib libname	787	=item C<--staticlib> libname
595		788
596	When not linking fully statically, this option allows you to link specific	789	When not linking fully statically, this option allows you to link specific
597	libraries statically. What it does is simply replace all occurances of	790	libraries statically. What it does is simply replace all occurrences of
598	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>	791	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>
599	option.	792	option.
600		793
601	This will have no effect unless the library is actually linked against,	794	This will have no effect unless the library is actually linked against,
602	specifically, C<--staticlib> will not link against the named library	795	specifically, C<--staticlib> will not link against the named library
603	unless it would be linked against anyway.	796	unless it would be linked against anyway.
604		797
605	Example: link libcrypt statically into the binary.	798	Example: link libcrypt statically into the final binary.
606		799
607	staticperl mkperl -MIO::AIO --staticlib crypt	800	staticperl mkperl -MIO::AIO --staticlib crypt
608		801
609	# ldopts might nwo contain:	802	# ldopts might now contain:
610	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread	803	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread
611		804
612	=item any other argument	805	=back
613
614	Any other argument is interpreted as a bundle specification file, which
615	supports most long options (without extra quoting), one option per line.
616		806
617	=back	807	=back
618		808
619	=head3 EXTENDED GLOB PATTERNS	809	=head3 EXTENDED GLOB PATTERNS
620		810
…		…
634	=item Patterns not starting with F</> will be anchored at the end of the path.	824	=item Patterns not starting with F</> will be anchored at the end of the path.
635		825
636	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the	826	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the
637	hierarchy, but not any directories of the same name.	827	hierarchy, but not any directories of the same name.
638		828
639	=item A F<*> matches any single component.	829	=item A F<*> matches anything within a single path component.
640		830
641	That is, F</unicore/*.pl> would match all F<.pl> files directly inside	831	That is, F</unicore/*.pl> would match all F<.pl> files directly inside
642	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>	832	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>
643	will not match slashes.	833	will not match slashes.
644		834
…		…
711	=item C<STATICPERL>	901	=item C<STATICPERL>
712		902
713	The directory where staticperl stores all its files	903	The directory where staticperl stores all its files
714	(default: F<~/.staticperl>).	904	(default: F<~/.staticperl>).
715		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
716	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...	918	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...
717		919
718	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
719	installation, you can set any environment variable you want - some modules	921	installation. You can set (and export!) any environment variable you want
720	(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
721		923	further tweaking.
722	=item C<PERL_VERSION>
723
724	The perl version to install - default is currently C<5.12.2>, but C<5.8.9>
725	is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is
726	about as big as 5.12.2).
727		924
728	=item C<PERL_PREFIX>	925	=item C<PERL_PREFIX>
729		926
730	The prefix where perl gets installed (default: F<$STATICPERL/perl>),	927	The prefix where perl gets installed (default: F<$STATICPERL/perl>),
731	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.
…		…
752	F<~/.staticperlrc> to override them.	949	F<~/.staticperlrc> to override them.
753		950
754	Most of the variables override (or modify) the corresponding F<Configure>	951	Most of the variables override (or modify) the corresponding F<Configure>
755	variable, except C<PERL_CCFLAGS>, which gets appended.	952	variable, except C<PERL_CCFLAGS>, which gets appended.
756		953
		954	You should have a look near the beginning of the F<staticperl> script -
		955	staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options
		956	suitable for newer gcc versions. For other compilers or older versions you
		957	need to adjust these, for example, in your F<~/.staticperlrc>.
		958
757	=back	959	=back
758		960
759	=head4 Variables you probably I<do not want> to override	961	=head4 Variables you probably I<do not want> to override
760		962
761	=over 4	963	=over 4
…		…
779	=head3 OVERRIDABLE HOOKS	981	=head3 OVERRIDABLE HOOKS
780		982
781	In addition to environment variables, it is possible to provide some	983	In addition to environment variables, it is possible to provide some
782	shell functions that are called at specific times. To provide your own	984	shell functions that are called at specific times. To provide your own
783	commands, just define the corresponding function.	985	commands, just define the corresponding function.
		986
		987	The actual order in which hooks are invoked during a full install
		988	from scratch is C<preconfigure>, C<patchconfig>, C<postconfigure>,
		989	C<postbuild>, C<postinstall>.
784		990
785	Example: install extra modules from CPAN and from some directories	991	Example: install extra modules from CPAN and from some directories
786	at F<staticperl install> time.	992	at F<staticperl install> time.
787		993
788	postinstall() {	994	postinstall() {
…		…
795		1001
796	=over 4	1002	=over 4
797		1003
798	=item preconfigure	1004	=item preconfigure
799		1005
800	Called just before running F<./Configur> in the perl source	1006	Called just before running F<./Configure> in the perl source
801	directory. Current working directory is the perl source directory.	1007	directory. Current working directory is the perl source directory.
802		1008
803	This can be used to set any C<PERL_xxx> variables, which might be costly	1009	This can be used to set any C<PERL_xxx> variables, which might be costly
804	to compute.	1010	to compute.
805		1011
		1012	=item patchconfig
		1013
		1014	Called after running F<./Configure> in the perl source directory to create
		1015	F<./config.sh>, but before running F<./Configure -S> to actually apply the
		1016	config. Current working directory is the perl source directory.
		1017
		1018	Can be used to tailor/patch F<config.sh> or do any other modifications.
		1019
806	=item postconfigure	1020	=item postconfigure
807		1021
808	Called after configuring, but before building perl. Current working	1022	Called after configuring, but before building perl. Current working
809	directory is the perl source directory.	1023	directory is the perl source directory.
810
811	Could be used to tailor/patch config.sh (followed by F<sh Configure -S>)
812	or do any other modifications.
813		1024
814	=item postbuild	1025	=item postbuild
815		1026
816	Called after building, but before installing perl. Current working	1027	Called after building, but before installing perl. Current working
817	directory is the perl source directory.	1028	directory is the perl source directory.
…		…
855	A header file that contains the prototypes of the few symbols "exported"	1066	A header file that contains the prototypes of the few symbols "exported"
856	by bundle.c, and also exposes the perl headers to the application.	1067	by bundle.c, and also exposes the perl headers to the application.
857		1068
858	=over 4	1069	=over 4
859		1070
860	=item staticperl_init ()	1071	=item staticperl_init (xs_init = 0)
861		1072
862	Initialises the perl interpreter. You can use the normal perl functions	1073	Initialises the perl interpreter. You can use the normal perl functions
863	after calling this function, for example, to define extra functions or	1074	after calling this function, for example, to define extra functions or
864	to load a .pm file that contains some initialisation code, or the main	1075	to load a .pm file that contains some initialisation code, or the main
865	program function:	1076	program function:
…		…
872	}	1083	}
873		1084
874	static void	1085	static void
875	run_myapp(void)	1086	run_myapp(void)
876	{	1087	{
877	staticperl_init ();	1088	staticperl_init (0);
878	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");	1089	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
879	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"	1090	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"
880	}	1091	}
881		1092
		1093	When your bootcode already wants to access some XS functions at
		1094	compiletime, then you need to supply an C<xs_init> function pointer that
		1095	is called as soon as perl is initialised enough to define XS functions,
		1096	but before the preamble code is executed:
		1097
		1098	static void
		1099	xs_init (pTHX)
		1100	{
		1101	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
		1102	}
		1103
		1104	static void
		1105	run_myapp(void)
		1106	{
		1107	staticperl_init (xs_init);
		1108	}
		1109
		1110	=item staticperl_cleanup ()
		1111
		1112	In the unlikely case that you want to destroy the perl interpreter, here
		1113	is the corresponding function.
		1114
882	=item staticperl_xs_init (pTHX)	1115	=item staticperl_xs_init (pTHX)
883		1116
884	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in	1117	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in
885	which case you do not want to use C<staticperl_init> but call them on your	1118	which case you do not want to use C<staticperl_init> but call them on your
886	own.	1119	own.
887		1120
888	Then you need this function - either pass it directly as the C<xs_init>	1121	Then you need this function - either pass it directly as the C<xs_init>
889	function to C<perl_parse>, or call it from your own C<xs_init> function.	1122	function to C<perl_parse>, or call it as one of the first things from your
890		1123	own C<xs_init> function.
891	=item staticperl_cleanup ()
892
893	In the unlikely case that you want to destroy the perl interpreter, here
894	is the corresponding function.
895		1124
896	=item PerlInterpreter *staticperl	1125	=item PerlInterpreter *staticperl
897		1126
898	The perl interpreter pointer used by staticperl. Not normally so useful,	1127	The perl interpreter pointer used by staticperl. Not normally so useful,
899	but there it is.	1128	but there it is.
…		…
912		1141
913	=back	1142	=back
914		1143
915	=head1 RUNTIME FUNCTIONALITY	1144	=head1 RUNTIME FUNCTIONALITY
916		1145
917	Binaries created with C<mkbundle>/C<mkperl> contain extra functions, which	1146	Binaries created with C<mkbundle>/C<mkperl> contain extra functionality,
918	are required to access the bundled perl sources, but might be useful for	1147	mostly related to the extra files bundled in the binary (the virtual
919	other purposes.	1148	filesystem). All of this data is statically compiled into the binary, and
		1149	accessing means copying it from a read-only section of your binary. Data
		1150	pages in this way is usually freed by the operating system, as it isn't
		1151	use more the onace.
		1152
		1153	=head2 VIRTUAL FILESYSTEM
		1154
		1155	Every bundle has a virtual filesystem. The only information stored in it
		1156	is the path and contents of each file that was bundled.
		1157
		1158	=head3 LAYOUT
		1159
		1160	Any path starting with an ampersand (F<&>) or exclamation mark (F<!>) are
		1161	reserved by F<staticperl>. They must only be used as described in this
		1162	section.
		1163
		1164	=over 4
		1165
		1166	=item !
		1167
		1168	All files that typically cannot be loaded from memory (such as dynamic
		1169	objects or shared libraries), but have to reside in the filesystem, are
		1170	prefixed with F<!>. Typically these files get written out to some
		1171	(semi-)temporary directory shortly after program startup, or before being
		1172	used.
		1173
		1174	=item !boot
		1175
		1176	The bootstrap file, if specified during bundling.
		1177
		1178	=item !auto/
		1179
		1180	Shared objects or dlls corresponding to dynamically-linked perl extensions
		1181	are stored with an F<!auto/> prefix.
		1182
		1183	=item !lib/
		1184
		1185	External shared libraries are stored in this directory.
		1186
		1187	=item any letter
		1188
		1189	Any path starting with a letter is a perl library file. For example,
		1190	F<Coro/AIO.pm> corresponds to the file loaded by C<use Coro::AIO>, and
		1191	F<Coro/jit.pl> corresponds to C<require "Coro/jit.pl">.
		1192
		1193	Obviously, module names shouldn't start with any other characters than
		1194	letters :)
		1195
		1196	=back
		1197
		1198	=head3 FUNCTIONS
		1199
		1200	=over 4
		1201
		1202	=item $file = static::find $path
		1203
		1204	Returns the data associated with the given C<$path>
		1205	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>).
		1206
		1207	Returns C<undef> if the file isn't embedded.
		1208
		1209	=item @paths = static::list
		1210
		1211	Returns the list of all paths embedded in this binary.
		1212
		1213	=back
		1214
		1215	=head2 EXTRA FEATURES
920		1216
921	In addition, for the embedded loading of perl files to work, F<staticperl>	1217	In addition, for the embedded loading of perl files to work, F<staticperl>
922	overrides the C<@INC> array.	1218	overrides the C<@INC> array.
923		1219
924	=over 4
925
926	=item $file = staticperl::find $path
927
928	Returns the data associated with the given C<$path>
929	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>), which is basically
930	the UNIX path relative to the perl library directory.
931
932	Returns C<undef> if the file isn't embedded.
933
934	=item @paths = staticperl::list
935
936	Returns the list of all paths embedded in this binary.
937
938	=back
939
940	=head1 FULLY STATIC BINARIES - BUILDROOT	1220	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
941		1221
942	To make truly static (Linux-) libraries, you might want to have a look at	1222	To make truly static (Linux-) libraries, you might want to have a look at
943	buildroot (L<http://buildroot.uclibc.org/>).	1223	buildroot (L<http://buildroot.uclibc.org/>).
944		1224
945	Buildroot is primarily meant to set up a cross-compile environment (which	1225	Buildroot is primarily meant to set up a cross-compile environment (which
…		…
952	good experiences with GCC 4.4.x but not GCC 4.5.	1232	good experiences with GCC 4.4.x but not GCC 4.5.
953		1233
954	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections	1234	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections
955	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>	1235	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>
956	doesn't decrease codesize much, but it makes the file much more	1236	doesn't decrease codesize much, but it makes the file much more
957	compressible.	1237	compressible (and the execution a lot slower...).
958		1238
959	If you don't need Coro or threads, you can go with "linuxthreads.old" (or	1239	If you don't need Coro or threads, you can go with "linuxthreads.old" (or
960	no thread support). For Coro, it is highly recommended to switch to a	1240	no thread support). For Coro, it is highly recommended to switch to a
961	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201	1241	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201
962	snapshot) and enable NPTL, otherwise Coro needs to be configured with the	1242	snapshot) and enable NPTL, otherwise Coro needs to be configured with the
…		…
964	twice the address space needed for stacks).	1244	twice the address space needed for stacks).
965		1245
966	If you use C<linuxthreads.old>, then you should also be aware that	1246	If you use C<linuxthreads.old>, then you should also be aware that
967	uClibc shares C<errno> between all threads when statically linking. See	1247	uClibc shares C<errno> between all threads when statically linking. See
968	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a	1248	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a
969	workaround (And L<https://bugs.uclibc.org/2089> for discussion).	1249	workaround (and L<https://bugs.uclibc.org/2089> for discussion).
970		1250
971	C<ccache> support is also recommended, especially if you want	1251	C<ccache> support is also recommended, especially if you want
972	to play around with buildroot options. Enabling the C<miniperl>	1252	to play around with buildroot options. Enabling the C<miniperl>
973	package will probably enable all options required for a successful	1253	package will probably enable all options required for a successful
974	perl build. F<staticperl> itself additionally needs either C<wget>	1254	perl build. F<staticperl> itself additionally needs either C<wget>
…		…
982	it from working properly in a chroot - either use dash (and link it to	1262	it from working properly in a chroot - either use dash (and link it to
983	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's	1263	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's
984	built-in ash shell.	1264	built-in ash shell.
985		1265
986	Finally, you need F</dev/null> inside the chroot for many scripts to work	1266	Finally, you need F</dev/null> inside the chroot for many scripts to work
987	- F<cp /dev/null output/target/dev> or bind-mounting your F</dev> will	1267	- either F<cp /dev/null output/target/dev> or bind-mounting your F</dev>
988	both provide this.	1268	will provide this.
989		1269
990	After you have compiled and set up your buildroot target, you can copy	1270	After you have compiled and set up your buildroot target, you can copy
991	F<staticperl> from the C<App::Staticperl> distribution or from your	1271	F<staticperl> from the C<App::Staticperl> distribution or from your
992	perl f<bin> directory (if you installed it) into the F<output/target>	1272	perl F<bin> directory (if you installed it) into the F<output/target>
993	filesystem, chroot inside and run it.	1273	filesystem, chroot inside and run it.
994		1274
995	=head1 RECIPES / SPECIFIC MODULES	1275	=head1 RECIPES / SPECIFIC MODULES
996		1276
997	This section contains some common(?) recipes and information about	1277	This section contains some common(?) recipes and information about
…		…
1006		1286
1007	Some functionality in the utf8 module, such as swash handling (used	1287	Some functionality in the utf8 module, such as swash handling (used
1008	for unicode character ranges in regexes) is implemented in the	1288	for unicode character ranges in regexes) is implemented in the
1009	C<"utf8_heavy.pl"> library:	1289	C<"utf8_heavy.pl"> library:
1010		1290
1011	-M'"utf8_heavy.pl"'	1291	-Mutf8_heavy.pl
1012		1292
1013	Many Unicode properties in turn are defined in separate modules,	1293	Many Unicode properties in turn are defined in separate modules,
1014	such as C<"unicore/Heavy.pl"> and more specific data tables such as	1294	such as C<"unicore/Heavy.pl"> and more specific data tables such as
1015	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables	1295	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables
1016	are big (7MB uncompressed, although F<staticperl> contains special	1296	are big (7MB uncompressed, although F<staticperl> contains special
1017	handling for those files), so including them on demand by your application	1297	handling for those files), so including them on demand by your application
1018	only might pay off.	1298	only might pay off.
1019		1299
1020	To simply include the whole unicode database, use:	1300	To simply include the whole unicode database, use:
1021		1301
1022	--incglob '/unicore/*.pl'	1302	--incglob '/unicore/**.pl'
1023		1303
1024	=item AnyEvent	1304	=item AnyEvent
1025		1305
1026	AnyEvent needs a backend implementation that it will load in a delayed	1306	AnyEvent needs a backend implementation that it will load in a delayed
1027	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice	1307	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice
…		…
1032		1312
1033	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn	1313	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn
1034	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and	1314	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and
1035	C<"AnyEvent/Util/uts46data.pl">.	1315	C<"AnyEvent/Util/uts46data.pl">.
1036		1316
1037	Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include	1317	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
1038	everything.	1318	everything.
		1319
		1320	=item Cairo
		1321
		1322	See Glib, same problem, same solution.
1039		1323
1040	=item Carp	1324	=item Carp
1041		1325
1042	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1326	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
1043	perl 5.12.2 (maybe earlier), this dependency no longer exists.	1327	perl 5.12.2 (maybe earlier), this dependency no longer exists.
…		…
1046		1330
1047	The F<perl -V> switch (as well as many modules) needs L<Config>, which in	1331	The F<perl -V> switch (as well as many modules) needs L<Config>, which in
1048	turn might need L<"Config_heavy.pl">. Including the latter gives you	1332	turn might need L<"Config_heavy.pl">. Including the latter gives you
1049	both.	1333	both.
1050		1334
		1335	=item Glib
		1336
		1337	Glib literally requires Glib to be installed already to build - it tries
		1338	to fake this by running Glib out of the build directory before being
		1339	built. F<staticperl> tries to work around this by forcing C<MAN1PODS> and
		1340	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
		1341
		1342	=item Gtk2
		1343
		1344	See Pango, same problems, same solution.
		1345
		1346	=item Pango
		1347
		1348	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
		1349	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>
		1350	tries to patch L<ExtUtils::MM_Unix> to route around Pango.
		1351
1051	=item Term::ReadLine::Perl	1352	=item Term::ReadLine::Perl
1052		1353
1053	Also needs L<Term::ReadLine::readline>, or C<--usepacklist>.	1354	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
1054		1355
1055	=item URI	1356	=item URI
1056		1357
1057	URI implements schemes as separate modules - the generic URL scheme is	1358	URI implements schemes as separate modules - the generic URL scheme is
1058	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If	1359	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If
1059	you need to use any of these schemes, you should include these manually,	1360	you need to use any of these schemes, you should include these manually,
1060	or use C<--usepacklist>.	1361	or use C<--usepacklists>.
1061		1362
1062	=back	1363	=back
1063		1364
1064	=head2 RECIPES	1365	=head2 RECIPES
1065		1366
1066	=over 4	1367	=over 4
1067		1368
1068	=item Linking everything in	1369	=item Just link everything in
1069		1370
1070	To link just about everything installed in the perl library into a new	1371	To link just about everything installed in the perl library into a new
1071	perl, try this:	1372	perl, try this (the first time this runs it will take a long time, as a
		1373	lot of files need to be parsed):
1072		1374
1073	staticperl mkperl --strip ppi --incglob '*'	1375	staticperl mkperl -v --strip ppi --incglob '*'
1074		1376
		1377	If you don't mind the extra megabytes, this can be a very effective way of
		1378	creating bundles without having to worry about forgetting any modules.
		1379
		1380	You get even more useful variants of this method by first selecting
		1381	everything, and then excluding stuff you are reasonable sure not to need -
		1382	L<bigperl\|http://staticperl.schmorp.de/bigperl.html> uses this approach.
		1383
1075	=item Getting rid of netdb function	1384	=item Getting rid of netdb functions
1076		1385
1077	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>	1386	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>
1078	and so on) that few applications use. You can avoid compiling them in by	1387	and so on) that few applications use. You can avoid compiling them in by
1079	putting the following fragment into a C<preconfigure> hook:	1388	putting the following fragment into a C<preconfigure> hook:
1080		1389
…		…
1097	do	1406	do
1098	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"	1407	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
1099	done	1408	done
1100	}	1409	}
1101		1410
1102	This mostly gains space when linking staticaly, as the functions will	1411	This mostly gains space when linking statically, as the functions will
1103	likely not be linked in. The gain for dynamically-linked binaries is	1412	likely not be linked in. The gain for dynamically-linked binaries is
1104	smaller.	1413	smaller.
1105		1414
1106	Also, this leaves C<gethostbyname> in - not only is it actually used	1415	Also, this leaves C<gethostbyname> in - not only is it actually used
1107	often, the L<Socket> module also exposes it, so leaving it out usually	1416	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.25 by root, Tue Dec 21 12:59:29 2010 UTC vs. Revision 1.49 by root, Wed Jul 13 15:23:13 2011 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.25 by root, Tue Dec 21 12:59:29 2010 UTC vs.
Revision 1.49 by root, Wed Jul 13 15:23:13 2011 UTC