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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.31 by root, Thu Dec 23 14:16:25 2010 UTC vs.
Revision 1.45 by root, Mon Jun 27 21:56:51 2011 UTC

…		…
9	staticperl configure # fetch and then configure perl	9	staticperl configure # fetch and then configure perl
10	staticperl build # configure and then build perl	10	staticperl build # configure and then build perl
11	staticperl install # build and then install perl	11	staticperl install # build and then install perl
12	staticperl clean # clean most intermediate files (restart at configure)	12	staticperl clean # clean most intermediate files (restart at configure)
13	staticperl distclean # delete everything installed by this script	13	staticperl distclean # delete everything installed by this script
		14	staticperl perl ... # invoke the perlinterpreter
14	staticperl cpan # invoke CPAN shell	15	staticperl cpan # invoke CPAN shell
15	staticperl instmod path... # install unpacked modules	16	staticperl instmod path... # install unpacked modules
16	staticperl instcpan modulename... # install modules from CPAN	17	staticperl instcpan modulename... # install modules from CPAN
17	staticperl mkbundle <bundle-args...> # see documentation	18	staticperl mkbundle <bundle-args...> # see documentation
18	staticperl mkperl <bundle-args...> # see documentation	19	staticperl mkperl <bundle-args...> # see documentation
…		…
20		21
21	Typical Examples:	22	Typical Examples:
22		23
23	staticperl install # fetch, configure, build and install perl	24	staticperl install # fetch, configure, build and install perl
24	staticperl cpan # run interactive cpan shell	25	staticperl cpan # run interactive cpan shell
25	staticperl mkperl -M '"Config_heavy.pl"' # build a perl that supports -V	26	staticperl mkperl -MConfig_heavy.pl # build a perl that supports -V
26	staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http	27	staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http
27	# build a perl with the above modules linked in	28	# build a perl with the above modules linked in
28	staticperl mkapp myapp --boot mainprog mymodules	29	staticperl mkapp myapp --boot mainprog mymodules
29	# build a binary "myapp" from mainprog and mymodules	30	# build a binary "myapp" from mainprog and mymodules
30		31
…		…
38	file that contains perl interpreter, libc, all the modules you need, all	39	file that contains perl interpreter, libc, all the modules you need, all
39	the libraries you need and of course your actual program.	40	the libraries you need and of course your actual program.
40		41
41	With F<uClibc> and F<upx> on x86, you can create a single 500kb binary	42	With F<uClibc> and F<upx> on x86, you can create a single 500kb binary
42	that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO,	43	that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO,
43	Coro and so on. Or any other choice of modules.	44	Coro and so on. Or any other choice of modules (and some other size :).
44		45
45	To see how this turns out, you can try out smallperl and bigperl, two	46	To see how this turns out, you can try out smallperl and bigperl, two
46	pre-built static and compressed perl binaries with many and even more	47	pre-built static and compressed perl binaries with many and even more
47	modules: just follow the links at L<http://staticperl.schmorp.de/>.	48	modules: just follow the links at L<http://staticperl.schmorp.de/>.
48		49
…		…
139	with creating binaries and bundle files.	140	with creating binaries and bundle files.
140		141
141	=head2 PHASE 1 COMMANDS: INSTALLING PERL	142	=head2 PHASE 1 COMMANDS: INSTALLING PERL
142		143
143	The most important command is F<install>, which does basically	144	The most important command is F<install>, which does basically
144	everything. The default is to download and install perl 5.12.2 and a few	145	everything. The default is to download and install perl 5.12.3 and a few
145	modules required by F<staticperl> itself, but all this can (and should) be	146	modules required by F<staticperl> itself, but all this can (and should) be
146	changed - see L<CONFIGURATION>, below.	147	changed - see L<CONFIGURATION>, below.
147		148
148	The command	149	The command
149		150
…		…
185		186
186	=item F<staticperl install>	187	=item F<staticperl install>
187		188
188	Wipes the perl installation directory (usually F<~/.staticperl/perl>) and	189	Wipes the perl installation directory (usually F<~/.staticperl/perl>) and
189	installs the perl distribution, potentially after building it first.	190	installs the perl distribution, potentially after building it first.
		191
		192	=item F<staticperl perl> [args...]
		193
		194	Invokes the compiled perl interpreter with the given args. Basically the
		195	same as starting perl directly (usually via F<~/.staticperl/bin/perl>),
		196	but beats typing the path sometimes.
		197
		198	Example: check that the Gtk2 module is installed and loadable.
		199
		200	staticperl perl -MGtk2 -e0
190		201
191	=item F<staticperl cpan> [args...]	202	=item F<staticperl cpan> [args...]
192		203
193	Starts an interactive CPAN shell that you can use to install further	204	Starts an interactive CPAN shell that you can use to install further
194	modules. Installs the perl first if necessary, but apart from that,	205	modules. Installs the perl first if necessary, but apart from that,
…		…
252		263
253	# first make sure we have perl and the required modules	264	# first make sure we have perl and the required modules
254	staticperl instcpan AnyEvent::HTTPD	265	staticperl instcpan AnyEvent::HTTPD
255		266
256	# now build the perl	267	# now build the perl
257	staticperl mkperl -M'"Config_heavy.pl"' -MAnyEvent::Impl::Perl \	268	staticperl mkperl -MConfig_heavy.pl -MAnyEvent::Impl::Perl \
258	-MAnyEvent::HTTPD -MURI::http \	269	-MAnyEvent::HTTPD -MURI::http \
259	--add 'eg/httpd httpd.pm'	270	--add 'eg/httpd httpd.pm'
260		271
261	# finally, invoke it	272	# finally, invoke it
262	./perl -Mhttpd	273	./perl -Mhttpd
…		…
381		392
382	=over 4	393	=over 4
383		394
384	=item C<--use> F<module> \| C<-M>F<module>	395	=item C<--use> F<module> \| C<-M>F<module>
385		396
386	Include the named module and trace direct dependencies. This is done by	397	Include the named module or perl library and trace direct
387	C<require>'ing the module in a subprocess and tracing which other modules	398	dependencies. This is done by loading the module in a subprocess and
388	and files it actually loads.	399	tracing which other modules and files it actually loads.
389		400
390	Example: include AnyEvent and AnyEvent::Impl::Perl.	401	Example: include AnyEvent and AnyEvent::Impl::Perl.
391		402
392	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl	403	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
393		404
394	Sometimes you want to load old-style "perl libraries" (F<.pl> files),	405	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
395	or maybe other weirdly named files. To do that, you need to quote	406	maybe other weirdly named files. To support this, the C<--use> option
396	the name in single or double quotes (this is because F<staticperl>	407	actually tries to do what you mean, depending on the string you specify:
397	I<literally> just adds the string after the C<require> - which acts	408
398	different when confronted with quoted vs. unquoted strings). When given on	409	=over 4
399	the command line, you probably need to quote once more to avoid your shell	410
400	interpreting it. Common cases that need this are F<Config_heavy.pl> and	411	=item a possibly valid module name, e.g. F<common::sense>, F<Carp>,
401	F<utf8_heavy.pl>.	412	F<Coro::Mysql>.
		413
		414	If the string contains no quotes, no F</> and no F<.>, then C<--use>
		415	assumes that it is a normal module name. It will create a new package and
		416	evaluate a C<use module> in it, i.e. it will load the package and do a
		417	default import.
		418
		419	The import step is done because many modules trigger more dependencies
		420	when something is imported than without.
		421
		422	=item anything that contains F</> or F<.> characters,
		423	e.g. F<utf8_heavy.pl>, F<Module/private/data.pl>.
		424
		425	The string will be quoted and passed to require, as if you used C<require
		426	$module>. Nothing will be imported.
		427
		428	=item "path" or 'path', e.g. C<"utf8_heavy.pl">.
		429
		430	If you enclose the name into single or double quotes, then the quotes will
		431	be removed and the resulting string will be passed to require. This syntax
		432	is form compatibility with older versions of staticperl and should not be
		433	used anymore.
		434
		435	=back
		436
		437	Example: C<use> AnyEvent::Socket, once using C<use> (importing the
		438	symbols), and once via C<require>, not importing any symbols. The first
		439	form is preferred as many modules load some extra dependencies when asked
		440	to export symbols.
		441
		442	staticperl mkbundle -MAnyEvent::Socket # use + import
		443	staticperl mkbundle -MAnyEvent/Socket.pm # require only
402		444
403	Example: include the required files for F<perl -V> to work in all its	445	Example: include the required files for F<perl -V> to work in all its
404	glory (F<Config.pm> is included automatically by this).	446	glory (F<Config.pm> is included automatically by the dependency tracker).
405		447
406	# bourne shell	448	# shell command
407	staticperl mkbundle --use '"Config_heavy.pl"'	449	staticperl mkbundle -MConfig_heavy.pl
408		450
409	# bundle specification file	451	# bundle specification file
410	use "Config_heavy.pl"	452	use Config_heavy.pl
411		453
412	The C<-M>module syntax is included as a convenience that might be easier	454	The C<-M>module syntax is included as a convenience that might be easier
413	to remember than C<--use> - it's the same switch as perl itself uses	455	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	456	to load modules. Or maybe it confuses people. Time will tell. Or maybe
415	not. Sigh.	457	not. Sigh.
…		…
420	code, or maybe one of the modules you use need a special use statement. In	462	code, or maybe one of the modules you use need a special use statement. In
421	that case, you can use C<--eval> to execute some perl snippet or set some	463	that case, you can use C<--eval> to execute some perl snippet or set some
422	variables or whatever you need. All files C<require>'d or C<use>'d while	464	variables or whatever you need. All files C<require>'d or C<use>'d while
423	executing the snippet are included in the final bundle.	465	executing the snippet are included in the final bundle.
424		466
425	Keep in mind that F<mkbundle> will only C<require> the modules named	467	Keep in mind that F<mkbundle> will not import any symbols from the modules
426	by the C<--use> option, so do not expect the symbols from modules you	468	named by the C<--use> option, so do not expect the symbols from modules
427	C<--use>'d earlier on the command line to be available.	469	you C<--use>'d earlier on the command line to be available.
428		470
429	Example: force L<AnyEvent> to detect a backend and therefore include it	471	Example: force L<AnyEvent> to detect a backend and therefore include it
430	in the final bundle.	472	in the final bundle.
431		473
432	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'	474	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
…		…
467	--incglob '/unicore/**.pl'	509	--incglob '/unicore/**.pl'
468		510
469	=item C<--add> F<file> \| C<--add> "F<file> alias"	511	=item C<--add> F<file> \| C<--add> "F<file> alias"
470		512
471	Adds the given (perl) file into the bundle (and optionally call it	513	Adds the given (perl) file into the bundle (and optionally call it
472	"alias"). The F<file> is either an absolute path or a path relative to	514	"alias"). The F<file> is either an absolute path or a path relative to the
473	the current directory. If an alias is specified, then this is the name it	515	current directory. If an alias is specified, then this is the name it will
474	will use for C<@INC> searches, otherwise the F<file> will be used as the	516	use for C<@INC> searches, otherwise the path F<file> will be used as the
475	internal name.	517	internal name.
476		518
477	This switch is used to include extra files into the bundle.	519	This switch is used to include extra files into the bundle.
478		520
479	Example: embed the file F<httpd> in the current directory as F<httpd.pm>	521	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
480	when creating the bundle.	522	when creating the bundle.
481		523
482	staticperl mkperl --add "httpd httpd.pm"	524	staticperl mkperl --add "httpd httpd.pm"
		525
		526	# can be accessed via "use httpd"
		527
		528	Example: add a file F<initcode> from the current directory.
		529
		530	staticperl mkperl --add 'initcode &initcode'
		531
		532	# can be accessed via "do '&initcode'"
483		533
484	Example: add local files as extra modules in the bundle.	534	Example: add local files as extra modules in the bundle.
485		535
486	# specification file	536	# specification file
487	add file1 myfiles/file1.pm	537	add file1 myfiles/file1.pm
…		…
497		547
498	Just like C<--add>, except that it treats the file as binary and adds it	548	Just like C<--add>, except that it treats the file as binary and adds it
499	without any postprocessing (perl files might get stripped to reduce their	549	without any postprocessing (perl files might get stripped to reduce their
500	size).	550	size).
501		551
502	You should probably add a C</> prefix to avoid clashing with embedded perl	552	If you specify an alias you should probably add a C<&> prefix to avoid
503	files (whose paths do not start with C</>), and/or use a special directory	553	clashing with embedded perl files (whose paths never start with C<&>),
504	prefix, such as C</res/name>.	554	and/or use a special directory prefix, such as C<&res/name>.
505		555
506	You can later get a copy of these files by calling C<staticperl::find	556	You can later get a copy of these files by calling C<staticperl::find
507	"alias">.	557	"alias">.
508		558
509	An alternative way to embed binary files is to convert them to perl and	559	An alternative way to embed binary files is to convert them to perl and
…		…
664	The difference to the (mutually exclusive) C<--perl> option is that the	714	The difference to the (mutually exclusive) C<--perl> option is that the
665	binary created by this option will not try to act as a perl interpreter -	715	binary created by this option will not try to act as a perl interpreter -
666	instead it will simply initialise the perl interpreter, clean it up and	716	instead it will simply initialise the perl interpreter, clean it up and
667	exit.	717	exit.
668		718
669	This means that, by default, it will do nothing but burna few CPU cycles	719	This means that, by default, it will do nothing but burn a few CPU cycles
670	- for it to do something useful you I<must> add some boot code, e.g. with	720	- for it to do something useful you I<must> add some boot code, e.g. with
671	the C<--boot> option.	721	the C<--boot> option.
672		722
673	Example: create a standalone perl binary called F<./myexe> that will	723	Example: create a standalone perl binary called F<./myexe> that will
674	execute F<appfile> when it is started.	724	execute F<appfile> when it is started.
675		725
676	staticperl mkbundle --app myexe --boot appfile	726	staticperl mkbundle --app myexe --boot appfile
		727
		728	=item C<--ignore-env>
		729
		730	Generates extra code to unset some environment variables before
		731	initialising/running perl. Perl supports a lot of environment variables
		732	that might alter execution in ways that might be undesirablre for
		733	standalone applications, and this option removes those known to cause
		734	trouble.
		735
		736	Specifically, these are removed:
		737
		738	C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause underaible
		739	output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and
		740	C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>,
		741	C<PERLIO_DEBUG> and C<PERLIO> can affect input and output.
		742
		743	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
		744	startup code used by F<staticperl> overrides C<@INC> in all cases.
		745
		746	This option will not make your program more secure (unless you are
		747	running with elevated privileges), but it will reduce the surprise effect
		748	when a user has these environment variables set and doesn't expect your
		749	standalone program to act like a perl interpreter.
677		750
678	=item C<--static>	751	=item C<--static>
679		752
680	Add C<-static> to F<bundle.ldopts>, which means a fully static (if	753	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
681	supported by the OS) executable will be created. This is not immensely	754	supported by the OS) executable will be created. This is not immensely
…		…
809	=item C<STATICPERL>	882	=item C<STATICPERL>
810		883
811	The directory where staticperl stores all its files	884	The directory where staticperl stores all its files
812	(default: F<~/.staticperl>).	885	(default: F<~/.staticperl>).
813		886
		887	=item C<DLCACHE>
		888
		889	The path to a directory (will be created if it doesn't exist) where
		890	downloaded perl sources are being cached, to avoid downloading them
		891	again. The default is empty, which means there is no cache.
		892
		893	=item C<PERL_VERSION>
		894
		895	The perl version to install - default is currently C<5.12.3>, but C<5.8.9>
		896	is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is
		897	about as big as 5.12.3).
		898
814	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...	899	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...
815		900
816	Usually set to C<1> to make modules "less inquisitive" during their	901	Usually set to C<1> to make modules "less inquisitive" during their
817	installation, you can set any environment variable you want - some modules	902	installation. You can set (and export!) any environment variable you want
818	(such as L<Coro> or L<EV>) use environment variables for further tweaking.	903	- some modules (such as L<Coro> or L<EV>) use environment variables for
819		904	further tweaking.
820	=item C<PERL_VERSION>
821
822	The perl version to install - default is currently C<5.12.2>, but C<5.8.9>
823	is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is
824	about as big as 5.12.2).
825		905
826	=item C<PERL_PREFIX>	906	=item C<PERL_PREFIX>
827		907
828	The prefix where perl gets installed (default: F<$STATICPERL/perl>),	908	The prefix where perl gets installed (default: F<$STATICPERL/perl>),
829	i.e. where the F<bin> and F<lib> subdirectories will end up.	909	i.e. where the F<bin> and F<lib> subdirectories will end up.
…		…
850	F<~/.staticperlrc> to override them.	930	F<~/.staticperlrc> to override them.
851		931
852	Most of the variables override (or modify) the corresponding F<Configure>	932	Most of the variables override (or modify) the corresponding F<Configure>
853	variable, except C<PERL_CCFLAGS>, which gets appended.	933	variable, except C<PERL_CCFLAGS>, which gets appended.
854		934
		935	You should have a look near the beginning of the F<staticperl> script -
		936	staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options
		937	suitable for newer gcc versions. For other compilers or older versions you
		938	need to adjust these, for example, in your F<~/.staticperlrc>.
		939
855	=back	940	=back
856		941
857	=head4 Variables you probably I<do not want> to override	942	=head4 Variables you probably I<do not want> to override
858		943
859	=over 4	944	=over 4
…		…
877	=head3 OVERRIDABLE HOOKS	962	=head3 OVERRIDABLE HOOKS
878		963
879	In addition to environment variables, it is possible to provide some	964	In addition to environment variables, it is possible to provide some
880	shell functions that are called at specific times. To provide your own	965	shell functions that are called at specific times. To provide your own
881	commands, just define the corresponding function.	966	commands, just define the corresponding function.
		967
		968	The actual order in which hooks are invoked during a full install
		969	from scratch is C<preconfigure>, C<patchconfig>, C<postconfigure>,
		970	C<postbuild>, C<postinstall>.
882		971
883	Example: install extra modules from CPAN and from some directories	972	Example: install extra modules from CPAN and from some directories
884	at F<staticperl install> time.	973	at F<staticperl install> time.
885		974
886	postinstall() {	975	postinstall() {
…		…
893		982
894	=over 4	983	=over 4
895		984
896	=item preconfigure	985	=item preconfigure
897		986
898	Called just before running F<./Configur> in the perl source	987	Called just before running F<./Configure> in the perl source
899	directory. Current working directory is the perl source directory.	988	directory. Current working directory is the perl source directory.
900		989
901	This can be used to set any C<PERL_xxx> variables, which might be costly	990	This can be used to set any C<PERL_xxx> variables, which might be costly
902	to compute.	991	to compute.
903		992
		993	=item patchconfig
		994
		995	Called after running F<./Configure> in the perl source directory to create
		996	F<./config.sh>, but before running F<./Configure -S> to actually apply the
		997	config. Current working directory is the perl source directory.
		998
		999	Can be used to tailor/patch F<config.sh> or do any other modifications.
		1000
904	=item postconfigure	1001	=item postconfigure
905		1002
906	Called after configuring, but before building perl. Current working	1003	Called after configuring, but before building perl. Current working
907	directory is the perl source directory.	1004	directory is the perl source directory.
908
909	Could be used to tailor/patch config.sh (followed by F<sh Configure -S>)
910	or do any other modifications.
911		1005
912	=item postbuild	1006	=item postbuild
913		1007
914	Called after building, but before installing perl. Current working	1008	Called after building, but before installing perl. Current working
915	directory is the perl source directory.	1009	directory is the perl source directory.
…		…
953	A header file that contains the prototypes of the few symbols "exported"	1047	A header file that contains the prototypes of the few symbols "exported"
954	by bundle.c, and also exposes the perl headers to the application.	1048	by bundle.c, and also exposes the perl headers to the application.
955		1049
956	=over 4	1050	=over 4
957		1051
958	=item staticperl_init ()	1052	=item staticperl_init (xs_init = 0)
959		1053
960	Initialises the perl interpreter. You can use the normal perl functions	1054	Initialises the perl interpreter. You can use the normal perl functions
961	after calling this function, for example, to define extra functions or	1055	after calling this function, for example, to define extra functions or
962	to load a .pm file that contains some initialisation code, or the main	1056	to load a .pm file that contains some initialisation code, or the main
963	program function:	1057	program function:
…		…
970	}	1064	}
971		1065
972	static void	1066	static void
973	run_myapp(void)	1067	run_myapp(void)
974	{	1068	{
975	staticperl_init ();	1069	staticperl_init (0);
976	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");	1070	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
977	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"	1071	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"
978	}	1072	}
979		1073
		1074	When your bootcode already wants to access some XS functions at
		1075	compiletime, then you need to supply an C<xs_init> function pointer that
		1076	is called as soon as perl is initialised enough to define XS functions,
		1077	but before the preamble code is executed:
		1078
		1079	static void
		1080	xs_init (pTHX)
		1081	{
		1082	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
		1083	}
		1084
		1085	static void
		1086	run_myapp(void)
		1087	{
		1088	staticperl_init (xs_init);
		1089	}
		1090
		1091	=item staticperl_cleanup ()
		1092
		1093	In the unlikely case that you want to destroy the perl interpreter, here
		1094	is the corresponding function.
		1095
980	=item staticperl_xs_init (pTHX)	1096	=item staticperl_xs_init (pTHX)
981		1097
982	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in	1098	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in
983	which case you do not want to use C<staticperl_init> but call them on your	1099	which case you do not want to use C<staticperl_init> but call them on your
984	own.	1100	own.
985		1101
986	Then you need this function - either pass it directly as the C<xs_init>	1102	Then you need this function - either pass it directly as the C<xs_init>
987	function to C<perl_parse>, or call it from your own C<xs_init> function.	1103	function to C<perl_parse>, or call it as one of the first things from your
988		1104	own C<xs_init> function.
989	=item staticperl_cleanup ()
990
991	In the unlikely case that you want to destroy the perl interpreter, here
992	is the corresponding function.
993		1105
994	=item PerlInterpreter *staticperl	1106	=item PerlInterpreter *staticperl
995		1107
996	The perl interpreter pointer used by staticperl. Not normally so useful,	1108	The perl interpreter pointer used by staticperl. Not normally so useful,
997	but there it is.	1109	but there it is.
…		…
1050	good experiences with GCC 4.4.x but not GCC 4.5.	1162	good experiences with GCC 4.4.x but not GCC 4.5.
1051		1163
1052	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections	1164	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections
1053	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>	1165	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>
1054	doesn't decrease codesize much, but it makes the file much more	1166	doesn't decrease codesize much, but it makes the file much more
1055	compressible.	1167	compressible (and the execution a lot slower...).
1056		1168
1057	If you don't need Coro or threads, you can go with "linuxthreads.old" (or	1169	If you don't need Coro or threads, you can go with "linuxthreads.old" (or
1058	no thread support). For Coro, it is highly recommended to switch to a	1170	no thread support). For Coro, it is highly recommended to switch to a
1059	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201	1171	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201
1060	snapshot) and enable NPTL, otherwise Coro needs to be configured with the	1172	snapshot) and enable NPTL, otherwise Coro needs to be configured with the
…		…
1062	twice the address space needed for stacks).	1174	twice the address space needed for stacks).
1063		1175
1064	If you use C<linuxthreads.old>, then you should also be aware that	1176	If you use C<linuxthreads.old>, then you should also be aware that
1065	uClibc shares C<errno> between all threads when statically linking. See	1177	uClibc shares C<errno> between all threads when statically linking. See
1066	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a	1178	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a
1067	workaround (And L<https://bugs.uclibc.org/2089> for discussion).	1179	workaround (and L<https://bugs.uclibc.org/2089> for discussion).
1068		1180
1069	C<ccache> support is also recommended, especially if you want	1181	C<ccache> support is also recommended, especially if you want
1070	to play around with buildroot options. Enabling the C<miniperl>	1182	to play around with buildroot options. Enabling the C<miniperl>
1071	package will probably enable all options required for a successful	1183	package will probably enable all options required for a successful
1072	perl build. F<staticperl> itself additionally needs either C<wget>	1184	perl build. F<staticperl> itself additionally needs either C<wget>
…		…
1080	it from working properly in a chroot - either use dash (and link it to	1192	it from working properly in a chroot - either use dash (and link it to
1081	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's	1193	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's
1082	built-in ash shell.	1194	built-in ash shell.
1083		1195
1084	Finally, you need F</dev/null> inside the chroot for many scripts to work	1196	Finally, you need F</dev/null> inside the chroot for many scripts to work
1085	- F<cp /dev/null output/target/dev> or bind-mounting your F</dev> will	1197	- either F<cp /dev/null output/target/dev> or bind-mounting your F</dev>
1086	both provide this.	1198	will provide this.
1087		1199
1088	After you have compiled and set up your buildroot target, you can copy	1200	After you have compiled and set up your buildroot target, you can copy
1089	F<staticperl> from the C<App::Staticperl> distribution or from your	1201	F<staticperl> from the C<App::Staticperl> distribution or from your
1090	perl f<bin> directory (if you installed it) into the F<output/target>	1202	perl F<bin> directory (if you installed it) into the F<output/target>
1091	filesystem, chroot inside and run it.	1203	filesystem, chroot inside and run it.
1092		1204
1093	=head1 RECIPES / SPECIFIC MODULES	1205	=head1 RECIPES / SPECIFIC MODULES
1094		1206
1095	This section contains some common(?) recipes and information about	1207	This section contains some common(?) recipes and information about
…		…
1104		1216
1105	Some functionality in the utf8 module, such as swash handling (used	1217	Some functionality in the utf8 module, such as swash handling (used
1106	for unicode character ranges in regexes) is implemented in the	1218	for unicode character ranges in regexes) is implemented in the
1107	C<"utf8_heavy.pl"> library:	1219	C<"utf8_heavy.pl"> library:
1108		1220
1109	-M'"utf8_heavy.pl"'	1221	-Mutf8_heavy.pl
1110		1222
1111	Many Unicode properties in turn are defined in separate modules,	1223	Many Unicode properties in turn are defined in separate modules,
1112	such as C<"unicore/Heavy.pl"> and more specific data tables such as	1224	such as C<"unicore/Heavy.pl"> and more specific data tables such as
1113	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables	1225	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables
1114	are big (7MB uncompressed, although F<staticperl> contains special	1226	are big (7MB uncompressed, although F<staticperl> contains special
…		…
1133	C<"AnyEvent/Util/uts46data.pl">.	1245	C<"AnyEvent/Util/uts46data.pl">.
1134		1246
1135	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include	1247	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
1136	everything.	1248	everything.
1137		1249
		1250	=item Cairo
		1251
		1252	See Glib, same problem, same solution.
		1253
1138	=item Carp	1254	=item Carp
1139		1255
1140	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1256	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
1141	perl 5.12.2 (maybe earlier), this dependency no longer exists.	1257	perl 5.12.2 (maybe earlier), this dependency no longer exists.
1142		1258
1143	=item Config	1259	=item Config
1144		1260
1145	The F<perl -V> switch (as well as many modules) needs L<Config>, which in	1261	The F<perl -V> switch (as well as many modules) needs L<Config>, which in
1146	turn might need L<"Config_heavy.pl">. Including the latter gives you	1262	turn might need L<"Config_heavy.pl">. Including the latter gives you
1147	both.	1263	both.
		1264
		1265	=item Glib
		1266
		1267	Glib literally requires Glib to be installed already to build - it tries
		1268	to fake this by running Glib out of the build directory before being
		1269	built. F<staticperl> tries to work around this by forcing C<MAN1PODS> and
		1270	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
		1271
		1272	=item Gtk2
		1273
		1274	See Pango, same problems, same solution.
		1275
		1276	=item Pango
		1277
		1278	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
		1279	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>
		1280	tries to patch L<ExtUtils::MM_Unix> to route around Pango.
1148		1281
1149	=item Term::ReadLine::Perl	1282	=item Term::ReadLine::Perl
1150		1283
1151	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.	1284	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
1152		1285

Diff Legend

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

Comparing App-Staticperl/staticperl.pod (file contents): Revision 1.31 by root, Thu Dec 23 14:16:25 2010 UTC vs. Revision 1.45 by root, Mon Jun 27 21:56:51 2011 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.31 by root, Thu Dec 23 14:16:25 2010 UTC vs.
Revision 1.45 by root, Mon Jun 27 21:56:51 2011 UTC