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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.26 by root, Tue Dec 21 19:14:56 2010 UTC vs.
Revision 1.35 by root, Thu Feb 10 22:44:29 2011 UTC

…		…
313		313
314	=head3 OPTION PROCESSING	314	=head3 OPTION PROCESSING
315		315
316	All options can be given as arguments on the command line (typically	316	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	317	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	318	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	319	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	320	(one option per line, with or without C<--> prefix) and specify this
321	instead.	321	bundle file instead.
322		322
323	For example, the command given earlier could also look like this:	323	For example, the command given earlier to link a new F<perl> could also
		324	look like this:
324		325
325	staticperl mkperl httpd.bundle	326	staticperl mkperl httpd.bundle
326		327
327	And all options could be in F<httpd.bundle>:	328	With all options stored in the F<httpd.bundle> file (one option per line,
328		329	everything after the option is an argument):
		330
329	use "Config_heavy.pl"	331	use "Config_heavy.pl"
330	use AnyEvent::Impl::Perl	332	use AnyEvent::Impl::Perl
331	use AnyEvent::HTTPD	333	use AnyEvent::HTTPD
332	use URI::http	334	use URI::http
333	add eg/httpd httpd.pm	335	add eg/httpd httpd.pm
334		336
335	All options that specify modules or files to be added are processed in the	337	All options that specify modules or files to be added are processed in the
336	order given on the command line.	338	order given on the command line.
337		339
338	=head3 BUNDLE CREATION WORKFLOW	340	=head3 BUNDLE CREATION WORKFLOW / STATICPELR MKBUNDLE OPTIONS
339		341
340	F<staticperl mkbundle> works by first assembling a list of candidate	342	F<staticperl mkbundle> works by first assembling a list of candidate
341	files and modules to include, then filtering them by include/exclude	343	files and modules to include, then filtering them by include/exclude
342	patterns. The remaining modules (together with their direct depdendencies,	344	patterns. The remaining modules (together with their direct dependencies,
343	such as link libraries and AutoLoader files) are then converted into	345	such as link libraries and L<AutoLoader> files) are then converted into
344	bundle files suitable for embedding. Afterwards, F<staticperl mkbundle>	346	bundle files suitable for embedding. F<staticperl mkbundle> can then
345	can optionally build a new perl interpreter or a standalone application.	347	optionally build a new perl interpreter or a standalone application.
346		348
347	=over 4	349	=over 4
348		350
349	=item Step 0: Generic argument processing.	351	=item Step 0: Generic argument processing.
350		352
351	The following options influence F<staticperl mkbundle> itself.	353	The following options influence F<staticperl mkbundle> itself.
352		354
353	=over 4	355	=over 4
354		356
355	=item --verbose \| -v	357	=item C<--verbose> \| C<-v>
356		358
357	Increases the verbosity level by one (the default is C<1>).	359	Increases the verbosity level by one (the default is C<1>).
358		360
359	=item --quiet \| -q	361	=item C<--quiet> \| C<-q>
360		362
361	Decreases the verbosity level by one.	363	Decreases the verbosity level by one.
362		364
363	=item any other argument	365	=item any other argument
364		366
365	Any other argument is interpreted as a bundle specification file, which	367	Any other argument is interpreted as a bundle specification file, which
366	supports most long options (without extra quoting), one option per line.	368	supports all options (without extra quoting), one option per line, in the
		369	format C<option> or C<option argument>. They will effectively be expanded
		370	and processed as if they were directly written on the command line, in
		371	place of the file name.
367		372
368	=back	373	=back
369		374
370	=item Step 1: gather candidate files and modules	375	=item Step 1: gather candidate files and modules
371		376
…		…
377	=over 4	382	=over 4
378		383
379	=item C<--use> F<module> \| C<-M>F<module>	384	=item C<--use> F<module> \| C<-M>F<module>
380		385
381	Include the named module and trace direct dependencies. This is done by	386	Include the named module and trace direct dependencies. This is done by
382	C<require>'ing the module in a subprocess and tracing which other modules	387	C<use>'ing the module from a fresh package in a subprocess and tracing
383	and files it actually loads.	388	which other modules and files it actually loads.
384		389
385	Example: include AnyEvent and AnyEvent::Impl::Perl.	390	Example: include AnyEvent and AnyEvent::Impl::Perl.
386		391
387	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl	392	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
388		393
389	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or	394	Sometimes you want to load old-style "perl libraries" (F<.pl> files),
390	maybe other weirdly named files. To do that, you need to quote the name in	395	or maybe other weirdly named files. To do that, you need to quote
391	single or double quotes. When given on the command line, you probably need	396	the name in single or double quotes (this is because F<staticperl>
392	to quote once more to avoid your shell interpreting it. Common cases that	397	I<literally> just adds the string after the C<require> - which acts
393	need this are F<Config_heavy.pl> and F<utf8_heavy.pl>.	398	different when confronted with quoted vs. unquoted strings). When given on
		399	the command line, you probably need to quote once more to avoid your shell
		400	interpreting it. Common cases that need this are F<Config_heavy.pl> and
		401	F<utf8_heavy.pl>.
394		402
395	Example: include the required files for F<perl -V> to work in all its	403	Example: include the required files for F<perl -V> to work in all its
396	glory (F<Config.pm> is included automatically by this).	404	glory (F<Config.pm> is included automatically by this).
397		405
398	# bourne shell	406	# bourne shell
399	staticperl mkbundle --use '"Config_heavy.pl"'	407	staticperl mkbundle --use '"Config_heavy.pl"'
400		408
401	# bundle specification file	409	# bundle specification file
402	use "Config_heavy.pl"	410	use "Config_heavy.pl"
403		411
404	The C<-M>module syntax is included as an alias that might be easier to	412	The C<-M>module syntax is included as a convenience that might be easier
405	remember than C<--use>. Or maybe it confuses people. Time will tell. Or	413	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
406	maybe not. Sigh.	415	not. Sigh.
407		416
408	=item C<--eval> "perl code" \| C<-e> "perl code"	417	=item C<--eval> "perl code" \| C<-e> "perl code"
409		418
410	Sometimes it is easier (or necessary) to specify dependencies using perl	419	Sometimes it is easier (or necessary) to specify dependencies using perl
411	code, or maybe one of the modules you use need a special use statement. In	420	code, or maybe one of the modules you use need a special use statement. In
412	that case, you can use C<--eval> to execute some perl snippet or set some	421	that case, you can use C<--eval> to execute some perl snippet or set some
413	variables or whatever you need. All files C<require>'d or C<use>'d while	422	variables or whatever you need. All files C<require>'d or C<use>'d while
414	executing the snippet are included in the final bundle.	423	executing the snippet are included in the final bundle.
415		424
416	Keep in mind that F<mkbundle> will only C<require> the modules named	425	Keep in mind that F<mkbundle> will not import any symbols from the modules
417	by the C<--use> option, so do not expect the symbols from modules you	426	named by the C<--use> option, so do not expect the symbols from modules
418	C<--use>'d earlier on the command line to be available.	427	you C<--use>'d earlier on the command line to be available.
419		428
420	Example: force L<AnyEvent> to detect a backend and therefore include it	429	Example: force L<AnyEvent> to detect a backend and therefore include it
421	in the final bundle.	430	in the final bundle.
422		431
423	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'	432	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
…		…
450	This is very useful to include "everything":	459	This is very useful to include "everything":
451		460
452	--incglob '*'	461	--incglob '*'
453		462
454	It is also useful for including perl libraries, or trees of those, such as	463	It is also useful for including perl libraries, or trees of those, such as
455	the unicode database files needed by some perl builtins, the regex engine	464	the unicode database files needed by some perl built-ins, the regex engine
456	and other modules.	465	and other modules.
457		466
458	--incglob '/unicore/**.pl'	467	--incglob '/unicore/**.pl'
459		468
460	=item C<--add> F<file> \| C<--add> "F<file> alias"	469	=item C<--add> F<file> \| C<--add> "F<file> alias"
461		470
462	Adds the given (perl) file into the bundle (and optionally call it	471	Adds the given (perl) file into the bundle (and optionally call it
463	"alias"). The F<file> is either an absolute path or a path relative to	472	"alias"). The F<file> is either an absolute path or a path relative to the
464	the current directory. If an alias is specified, then this is the name it	473	current directory. If an alias is specified, then this is the name it will
465	will use for C<@INC> searches, otherfile the F<file> will be used as the	474	use for C<@INC> searches, otherwise the path F<file> will be used as the
466	internal name.	475	internal name.
467		476
468	This switch is used to include extra files into the bundle.	477	This switch is used to include extra files into the bundle.
469		478
470	Example: embed the file F<httpd> in the current directory as F<httpd.pm>	479	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
471	when creating the bundle.	480	when creating the bundle.
472		481
473	staticperl mkperl --add "httpd httpd.pm"	482	staticperl mkperl --add "httpd httpd.pm"
		483
		484	# can be accessed via "use httpd"
		485
		486	Example: add a file F<initcode> from the current directory.
		487
		488	staticperl mkperl --add 'initcode &initcode'
		489
		490	# can be accessed via "do '&initcode'"
474		491
475	Example: add local files as extra modules in the bundle.	492	Example: add local files as extra modules in the bundle.
476		493
477	# specification file	494	# specification file
478	add file1 myfiles/file1.pm	495	add file1 myfiles/file1.pm
…		…
488		505
489	Just like C<--add>, except that it treats the file as binary and adds it	506	Just like C<--add>, except that it treats the file as binary and adds it
490	without any postprocessing (perl files might get stripped to reduce their	507	without any postprocessing (perl files might get stripped to reduce their
491	size).	508	size).
492		509
493	You should probably add a C</> prefix to avoid clashing with embedded perl	510	If you specify an alias you should probably add a C<&> prefix to avoid
494	files (whose paths do not start with C</>), and/or use a special directory	511	clashing with embedded perl files (whose paths never start with C<&>),
495	prefix, such as C</res/name>.	512	and/or use a special directory prefix, such as C<&res/name>.
496		513
497	You can later get a copy of these files by calling C<staticperl::find	514	You can later get a copy of these files by calling C<staticperl::find
498	"alias">.	515	"alias">.
499		516
500	An alternative way to embed binary files is to convert them to perl and	517	An alternative way to embed binary files is to convert them to perl and
…		…
513		530
514	=item Step 2: filter all files using C<--include> and C<--exclude> options.	531	=item Step 2: filter all files using C<--include> and C<--exclude> options.
515		532
516	After all candidate files and modules are added, they are I<filtered>	533	After all candidate files and modules are added, they are I<filtered>
517	by a combination of C<--include> and C<--exclude> patterns (there is an	534	by a combination of C<--include> and C<--exclude> patterns (there is an
518	implicit C<--include **> at the end, so if no filters are specified, all	535	implicit C<--include *> at the end, so if no filters are specified, all
519	files are included).	536	files are included).
520		537
521	All that this step does is potentially reduce the number of files that are	538	All that this step does is potentially reduce the number of files that are
522	to be included - no new files are added during this step.	539	to be included - no new files are added during this step.
523		540
…		…
548	that are added automatically. Only one (F<.packlist> files) is currently	565	that are added automatically. Only one (F<.packlist> files) is currently
549	optional and can be influenced, the others are always included:	566	optional and can be influenced, the others are always included:
550		567
551	=over 4	568	=over 4
552		569
553	=item C<--usepacklist>	570	=item C<--usepacklists>
554		571
555	Read F<.packlist> files for each distribution that happens to match a	572	Read F<.packlist> files for each distribution that happens to match a
556	module name you specified. Sounds weird, and it is, so expect semantics to	573	module name you specified. Sounds weird, and it is, so expect semantics to
557	change somehow in the future.	574	change somehow in the future.
558		575
…		…
626	Last not least, if you need accurate line numbers in error messages,	643	Last not least, if you need accurate line numbers in error messages,
627	or in the unlikely case where C<pod> is too slow, or some module gets	644	or in the unlikely case where C<pod> is too slow, or some module gets
628	mistreated, you can specify C<none> to not mangle included perl sources in	645	mistreated, you can specify C<none> to not mangle included perl sources in
629	any way.	646	any way.
630		647
631	=item --perl	648	=item C<--perl>
632		649
633	After writing out the bundle files, try to link a new perl interpreter. It	650	After writing out the bundle files, try to link a new perl interpreter. It
634	will be called F<perl> and will be left in the current working	651	will be called F<perl> and will be left in the current working
635	directory. The bundle files will be removed.	652	directory. The bundle files will be removed.
636		653
…		…
641	it will be even smaller than the standard perl interpreter as none of the	658	it will be even smaller than the standard perl interpreter as none of the
642	modules of the base distribution (such as L<Fcntl>) will be included.	659	modules of the base distribution (such as L<Fcntl>) will be included.
643		660
644	staticperl mkperl -Mcommon::sense	661	staticperl mkperl -Mcommon::sense
645		662
646	=item --app name	663	=item C<--app> F<name>
647		664
648	After writing out the bundle files, try to link a new standalone	665	After writing out the bundle files, try to link a new standalone
649	program. It will be called C<name>, and the bundle files get removed after	666	program. It will be called C<name>, and the bundle files get removed after
650	linking it.	667	linking it.
651		668
…		…
655	The difference to the (mutually exclusive) C<--perl> option is that the	672	The difference to the (mutually exclusive) C<--perl> option is that the
656	binary created by this option will not try to act as a perl interpreter -	673	binary created by this option will not try to act as a perl interpreter -
657	instead it will simply initialise the perl interpreter, clean it up and	674	instead it will simply initialise the perl interpreter, clean it up and
658	exit.	675	exit.
659		676
660	This means that, by default, it will do nothing but burna few CPU cycles	677	This means that, by default, it will do nothing but burn a few CPU cycles
661	- for it to do something useful you I<must> add some boot code, e.g. with	678	- for it to do something useful you I<must> add some boot code, e.g. with
662	the C<--boot> option.	679	the C<--boot> option.
663		680
664	Example: create a standalone perl binary called F<./myexe> that will	681	Example: create a standalone perl binary called F<./myexe> that will
665	execute F<appfile> when it is started.	682	execute F<appfile> when it is started.
666		683
667	staticperl mkbundle --app myexe --boot appfile	684	staticperl mkbundle --app myexe --boot appfile
668		685
669	=item --static	686	=item C<--static>
670		687
671	Add C<-static> to F<bundle.ldopts>, which means a fully static (if	688	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
672	supported by the OS) executable will be created. This is not immensely	689	supported by the OS) executable will be created. This is not immensely
673	useful when just creating the bundle files, but is most useful when	690	useful when just creating the bundle files, but is most useful when
674	linking a binary with the C<--perl> or C<--app> options.	691	linking a binary with the C<--perl> or C<--app> options.
…		…
681	systems based on GNU libc don't really support it in a very usable	698	systems based on GNU libc don't really support it in a very usable
682	fashion either. Try uClibc if you want to create fully statically linked	699	fashion either. Try uClibc if you want to create fully statically linked
683	executables, or try the C<--staticlib> option to link only some libraries	700	executables, or try the C<--staticlib> option to link only some libraries
684	statically.	701	statically.
685		702
686	=item --staticlib libname	703	=item C<--staticlib> libname
687		704
688	When not linking fully statically, this option allows you to link specific	705	When not linking fully statically, this option allows you to link specific
689	libraries statically. What it does is simply replace all occurances of	706	libraries statically. What it does is simply replace all occurrences of
690	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>	707	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>
691	option.	708	option.
692		709
693	This will have no effect unless the library is actually linked against,	710	This will have no effect unless the library is actually linked against,
694	specifically, C<--staticlib> will not link against the named library	711	specifically, C<--staticlib> will not link against the named library
695	unless it would be linked against anyway.	712	unless it would be linked against anyway.
696		713
697	Example: link libcrypt statically into the binary.	714	Example: link libcrypt statically into the final binary.
698		715
699	staticperl mkperl -MIO::AIO --staticlib crypt	716	staticperl mkperl -MIO::AIO --staticlib crypt
700		717
701	# ldopts might now contain:	718	# ldopts might now contain:
702	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread	719	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread
…		…
723	=item Patterns not starting with F</> will be anchored at the end of the path.	740	=item Patterns not starting with F</> will be anchored at the end of the path.
724		741
725	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the	742	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the
726	hierarchy, but not any directories of the same name.	743	hierarchy, but not any directories of the same name.
727		744
728	=item A F<*> matches any single component.	745	=item A F<*> matches anything within a single path component.
729		746
730	That is, F</unicore/*.pl> would match all F<.pl> files directly inside	747	That is, F</unicore/*.pl> would match all F<.pl> files directly inside
731	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>	748	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>
732	will not match slashes.	749	will not match slashes.
733		750
…		…
944	A header file that contains the prototypes of the few symbols "exported"	961	A header file that contains the prototypes of the few symbols "exported"
945	by bundle.c, and also exposes the perl headers to the application.	962	by bundle.c, and also exposes the perl headers to the application.
946		963
947	=over 4	964	=over 4
948		965
949	=item staticperl_init ()	966	=item staticperl_init (xs_init = 0)
950		967
951	Initialises the perl interpreter. You can use the normal perl functions	968	Initialises the perl interpreter. You can use the normal perl functions
952	after calling this function, for example, to define extra functions or	969	after calling this function, for example, to define extra functions or
953	to load a .pm file that contains some initialisation code, or the main	970	to load a .pm file that contains some initialisation code, or the main
954	program function:	971	program function:
…		…
961	}	978	}
962		979
963	static void	980	static void
964	run_myapp(void)	981	run_myapp(void)
965	{	982	{
966	staticperl_init ();	983	staticperl_init (0);
967	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");	984	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
968	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"	985	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"
969	}	986	}
970		987
		988	When your bootcode already wants to access some XS functions at
		989	compiletime, then you need to supply an C<xs_init> function pointer that
		990	is called as soon as perl is initialised enough to define XS functions,
		991	but before the preamble code is executed:
		992
		993	static void
		994	xs_init (pTHX)
		995	{
		996	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
		997	}
		998
		999	static void
		1000	run_myapp(void)
		1001	{
		1002	staticperl_init (xs_init);
		1003	}
		1004
		1005	=item staticperl_cleanup ()
		1006
		1007	In the unlikely case that you want to destroy the perl interpreter, here
		1008	is the corresponding function.
		1009
971	=item staticperl_xs_init (pTHX)	1010	=item staticperl_xs_init (pTHX)
972		1011
973	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in	1012	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in
974	which case you do not want to use C<staticperl_init> but call them on your	1013	which case you do not want to use C<staticperl_init> but call them on your
975	own.	1014	own.
976		1015
977	Then you need this function - either pass it directly as the C<xs_init>	1016	Then you need this function - either pass it directly as the C<xs_init>
978	function to C<perl_parse>, or call it from your own C<xs_init> function.	1017	function to C<perl_parse>, or call it as one of the first things from your
979		1018	own C<xs_init> function.
980	=item staticperl_cleanup ()
981
982	In the unlikely case that you want to destroy the perl interpreter, here
983	is the corresponding function.
984		1019
985	=item PerlInterpreter *staticperl	1020	=item PerlInterpreter *staticperl
986		1021
987	The perl interpreter pointer used by staticperl. Not normally so useful,	1022	The perl interpreter pointer used by staticperl. Not normally so useful,
988	but there it is.	1023	but there it is.
…		…
1024		1059
1025	Returns the list of all paths embedded in this binary.	1060	Returns the list of all paths embedded in this binary.
1026		1061
1027	=back	1062	=back
1028		1063
1029	=head1 FULLY STATIC BINARIES - BUILDROOT	1064	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
1030		1065
1031	To make truly static (Linux-) libraries, you might want to have a look at	1066	To make truly static (Linux-) libraries, you might want to have a look at
1032	buildroot (L<http://buildroot.uclibc.org/>).	1067	buildroot (L<http://buildroot.uclibc.org/>).
1033		1068
1034	Buildroot is primarily meant to set up a cross-compile environment (which	1069	Buildroot is primarily meant to set up a cross-compile environment (which
…		…
1106	handling for those files), so including them on demand by your application	1141	handling for those files), so including them on demand by your application
1107	only might pay off.	1142	only might pay off.
1108		1143
1109	To simply include the whole unicode database, use:	1144	To simply include the whole unicode database, use:
1110		1145
1111	--incglob '/unicore/*.pl'	1146	--incglob '/unicore/**.pl'
1112		1147
1113	=item AnyEvent	1148	=item AnyEvent
1114		1149
1115	AnyEvent needs a backend implementation that it will load in a delayed	1150	AnyEvent needs a backend implementation that it will load in a delayed
1116	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice	1151	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice
…		…
1121		1156
1122	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn	1157	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn
1123	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and	1158	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and
1124	C<"AnyEvent/Util/uts46data.pl">.	1159	C<"AnyEvent/Util/uts46data.pl">.
1125		1160
1126	Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include	1161	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
1127	everything.	1162	everything.
1128		1163
1129	=item Carp	1164	=item Carp
1130		1165
1131	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1166	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
…		…
1137	turn might need L<"Config_heavy.pl">. Including the latter gives you	1172	turn might need L<"Config_heavy.pl">. Including the latter gives you
1138	both.	1173	both.
1139		1174
1140	=item Term::ReadLine::Perl	1175	=item Term::ReadLine::Perl
1141		1176
1142	Also needs L<Term::ReadLine::readline>, or C<--usepacklist>.	1177	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
1143		1178
1144	=item URI	1179	=item URI
1145		1180
1146	URI implements schemes as separate modules - the generic URL scheme is	1181	URI implements schemes as separate modules - the generic URL scheme is
1147	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If	1182	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If
1148	you need to use any of these schemes, you should include these manually,	1183	you need to use any of these schemes, you should include these manually,
1149	or use C<--usepacklist>.	1184	or use C<--usepacklists>.
1150		1185
1151	=back	1186	=back
1152		1187
1153	=head2 RECIPES	1188	=head2 RECIPES
1154		1189
1155	=over 4	1190	=over 4
1156		1191
1157	=item Linking everything in	1192	=item Just link everything in
1158		1193
1159	To link just about everything installed in the perl library into a new	1194	To link just about everything installed in the perl library into a new
1160	perl, try this:	1195	perl, try this (the first time this runs it will take a long time, as a
		1196	lot of files need to be parsed):
1161		1197
1162	staticperl mkperl --strip ppi --incglob '*'	1198	staticperl mkperl -v --strip ppi --incglob '*'
1163		1199
		1200	If you don't mind the extra megabytes, this can be a very effective way of
		1201	creating bundles without having to worry about forgetting any modules.
		1202
		1203	You get even more useful variants of this method by first selecting
		1204	everything, and then excluding stuff you are reasonable sure not to need -
		1205	L<bigperl\|http://staticperl.schmorp.de/bigperl.html> uses this approach.
		1206
1164	=item Getting rid of netdb function	1207	=item Getting rid of netdb functions
1165		1208
1166	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>	1209	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>
1167	and so on) that few applications use. You can avoid compiling them in by	1210	and so on) that few applications use. You can avoid compiling them in by
1168	putting the following fragment into a C<preconfigure> hook:	1211	putting the following fragment into a C<preconfigure> hook:
1169		1212
…		…
1186	do	1229	do
1187	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"	1230	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
1188	done	1231	done
1189	}	1232	}
1190		1233
1191	This mostly gains space when linking staticaly, as the functions will	1234	This mostly gains space when linking statically, as the functions will
1192	likely not be linked in. The gain for dynamically-linked binaries is	1235	likely not be linked in. The gain for dynamically-linked binaries is
1193	smaller.	1236	smaller.
1194		1237
1195	Also, this leaves C<gethostbyname> in - not only is it actually used	1238	Also, this leaves C<gethostbyname> in - not only is it actually used
1196	often, the L<Socket> module also exposes it, so leaving it out usually	1239	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.26 by root, Tue Dec 21 19:14:56 2010 UTC vs. Revision 1.35 by root, Thu Feb 10 22:44:29 2011 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.26 by root, Tue Dec 21 19:14:56 2010 UTC vs.
Revision 1.35 by root, Thu Feb 10 22:44:29 2011 UTC