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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.24 by root, Wed Dec 15 00:17:47 2010 UTC vs.
Revision 1.40 by root, Sun May 1 09:29:47 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
…		…
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
…		…
278	-MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI::http	289	-MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI::http
279		290
280	# run it	291	# run it
281	./app	292	./app
282		293
		294	Here are the three phase 2 commands:
		295
		296	=over 4
		297
		298	=item F<staticperl mkbundle> args...
		299
		300	The "default" bundle command - it interprets the given bundle options and
		301	writes out F<bundle.h>, F<bundle.c>, F<bundle.ccopts> and F<bundle.ldopts>
		302	files, useful for embedding.
		303
		304	=item F<staticperl mkperl> args...
		305
		306	Creates a bundle just like F<staticperl mkbundle> (in fact, it's the same
		307	as invoking F<staticperl mkbundle --perl> args...), but then compiles and
		308	links a new perl interpreter that embeds the created bundle, then deletes
		309	all intermediate files.
		310
		311	=item F<staticperl mkapp> filename args...
		312
		313	Does the same as F<staticperl mkbundle> (in fact, it's the same as
		314	invoking F<staticperl mkbundle --app> filename args...), but then compiles
		315	and links a new standalone application that simply initialises the perl
		316	interpreter.
		317
		318	The difference to F<staticperl mkperl> is that the standalone application
		319	does not act like a perl interpreter would - in fact, by default it would
		320	just do nothing and exit immediately, so you should specify some code to
		321	be executed via the F<--boot> option.
		322
		323	=back
		324
283	=head3 OPTION PROCESSING	325	=head3 OPTION PROCESSING
284		326
285	All options can be given as arguments on the command line (typically	327	All options can be given as arguments on the command line (typically
286	using long (e.g. C<--verbose>) or short option (e.g. C<-v>) style). Since	328	using long (e.g. C<--verbose>) or short option (e.g. C<-v>) style). Since
287	specifying a lot of modules can make the command line very cumbersome,	329	specifying a lot of options can make the command line very long and
288	you can put all long options into a "bundle specification file" (with or	330	unwieldy, you can put all long options into a "bundle specification file"
289	without C<--> prefix) and specify this bundle file instead.	331	(one option per line, with or without C<--> prefix) and specify this
		332	bundle file instead.
290		333
291	For example, the command given earlier could also look like this:	334	For example, the command given earlier to link a new F<perl> could also
		335	look like this:
292		336
293	staticperl mkperl httpd.bundle	337	staticperl mkperl httpd.bundle
294		338
295	And all options could be in F<httpd.bundle>:	339	With all options stored in the F<httpd.bundle> file (one option per line,
296		340	everything after the option is an argument):
		341
297	use "Config_heavy.pl"	342	use "Config_heavy.pl"
298	use AnyEvent::Impl::Perl	343	use AnyEvent::Impl::Perl
299	use AnyEvent::HTTPD	344	use AnyEvent::HTTPD
300	use URI::http	345	use URI::http
301	add eg/httpd httpd.pm	346	add eg/httpd httpd.pm
302		347
303	All options that specify modules or files to be added are processed in the	348	All options that specify modules or files to be added are processed in the
304	order given on the command line (that affects the C<--use> and C<--eval>	349	order given on the command line.
305	options at the moment).
306		350
307	=head3 PACKAGE SELECTION WORKFLOW	351	=head3 BUNDLE CREATION WORKFLOW / STATICPELR MKBUNDLE OPTIONS
308		352
309	F<staticperl mkbundle> has a number of options to control package	353	F<staticperl mkbundle> works by first assembling a list of candidate
310	selection. This section describes how they interact with each other. Also,	354	files and modules to include, then filtering them by include/exclude
311	since I am still a newbie w.r.t. these issues, maybe future versions of	355	patterns. The remaining modules (together with their direct dependencies,
312	F<staticperl> will change this, so watch out :)	356	such as link libraries and L<AutoLoader> files) are then converted into
		357	bundle files suitable for embedding. F<staticperl mkbundle> can then
		358	optionally build a new perl interpreter or a standalone application.
313		359
314	The idiom "in order" means "in order that they are specified on the
315	commandline". If you use a bundle specification file, then the options
316	will be processed as if they were given in place of the bundle file name.
317
318	=over 4	360	=over 4
319		361
320	=item 1. apply all C<--use>, C<--eval>, C<--add>, C<--addbin> and	362	=item Step 0: Generic argument processing.
321	C<--incglob> options, in order.
322		363
323	In addition, C<--use> and C<--eval> dependencies will be added when the	364	The following options influence F<staticperl mkbundle> itself.
324	options are processed.
325		365
326	=item 2. apply all C<--include> and C<--exclude> options, in order.
327
328	All this step does is potentially reduce the number of files already
329	selected or found in phase 1.
330
331	=item 3. find all modules (== F<.pm> files), gather their static archives
332	(F<.a>) and AutoLoader splitfiles (F<.ix> and F<.al> files), find any
333	extra libraries they need for linking (F<extralibs.ld>) and optionally
334	evaluate any F<.packlist> files.
335
336	This step is required to link against XS extensions and also adds files
337	required for L<AutoLoader> to do it's job.
338
339	=back
340
341	After this, all the files selected for bundling will be read and processed
342	(stripped), the bundle files will be written, and optionally a new F<perl>
343	or application binary will be linked.
344
345	=head3 MKBUNDLE OPTIONS
346
347	=over 4	366	=over 4
348		367
349	=item --verbose \| -v	368	=item C<--verbose> \| C<-v>
350		369
351	Increases the verbosity level by one (the default is C<1>).	370	Increases the verbosity level by one (the default is C<1>).
352		371
353	=item --quiet \| -q	372	=item C<--quiet> \| C<-q>
354		373
355	Decreases the verbosity level by one.	374	Decreases the verbosity level by one.
356		375
		376	=item any other argument
		377
		378	Any other argument is interpreted as a bundle specification file, which
		379	supports all options (without extra quoting), one option per line, in the
		380	format C<option> or C<option argument>. They will effectively be expanded
		381	and processed as if they were directly written on the command line, in
		382	place of the file name.
		383
		384	=back
		385
		386	=item Step 1: gather candidate files and modules
		387
		388	In this step, modules, perl libraries (F<.pl> files) and other files are
		389	selected for inclusion in the bundle. The relevant options are executed
		390	in order (this makes a difference mostly for C<--eval>, which can rely on
		391	earlier C<--use> options to have been executed).
		392
		393	=over 4
		394
		395	=item C<--use> F<module> \| C<-M>F<module>
		396
		397	Include the named module or perl library and trace direct
		398	dependencies. This is done by loading the module in a subprocess and
		399	tracing which other modules and files it actually loads.
		400
		401	Example: include AnyEvent and AnyEvent::Impl::Perl.
		402
		403	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
		404
		405	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
		406	maybe other weirdly named files. To support this, the C<--use> option
		407	actually tries to do what you mean, depending on the string you specify:
		408
		409	=over 4
		410
		411	=item a possibly valid module name, e.g. F<common::sense>, F<Carp>,
		412	F<Coro::Mysql>.
		413
		414	If the string contains no quotes, no F</> and no F<.>, then C<--use>
		415	assumes that it is a normal module name. It will create a new package and
		416	evaluate a C<use module> in it, i.e. it will load the package and do a
		417	default import.
		418
		419	The import step is done because many modules trigger more dependencies
		420	when something is imported than without.
		421
		422	=item anything that contains F</> or F<.> characters,
		423	e.g. F<utf8_heavy.pl>, F<Module/private/data.pl>.
		424
		425	The string will be quoted and passed to require, as if you used C<require
		426	$module>. Nothing will be imported.
		427
		428	=item "path" or 'path', e.g. C<"utf8_heavy.pl">.
		429
		430	If you enclose the name into single or double quotes, then the quotes will
		431	be removed and the resulting string will be passed to require. This syntax
		432	is form compatibility with older versions of staticperl and should not be
		433	used anymore.
		434
		435	=back
		436
		437	Example: C<use> AnyEvent::Socket, once using C<use> (importing the
		438	symbols), and once via C<require>, not importing any symbols. The first
		439	form is preferred as many modules load some extra dependencies when asked
		440	to export symbols.
		441
		442	staticperl mkbundle -MAnyEvent::Socket # use + import
		443	staticperl mkbundle -MAnyEvent/Socket.pm # require only
		444
		445	Example: include the required files for F<perl -V> to work in all its
		446	glory (F<Config.pm> is included automatically by the dependency tracker).
		447
		448	# shell command
		449	staticperl mkbundle -MConfig_heavy.pl
		450
		451	# bundle specification file
		452	use Config_heavy.pl
		453
		454	The C<-M>module syntax is included as a convenience that might be easier
		455	to remember than C<--use> - it's the same switch as perl itself uses
		456	to load modules. Or maybe it confuses people. Time will tell. Or maybe
		457	not. Sigh.
		458
		459	=item C<--eval> "perl code" \| C<-e> "perl code"
		460
		461	Sometimes it is easier (or necessary) to specify dependencies using perl
		462	code, or maybe one of the modules you use need a special use statement. In
		463	that case, you can use C<--eval> to execute some perl snippet or set some
		464	variables or whatever you need. All files C<require>'d or C<use>'d while
		465	executing the snippet are included in the final bundle.
		466
		467	Keep in mind that F<mkbundle> will not import any symbols from the modules
		468	named by the C<--use> option, so do not expect the symbols from modules
		469	you C<--use>'d earlier on the command line to be available.
		470
		471	Example: force L<AnyEvent> to detect a backend and therefore include it
		472	in the final bundle.
		473
		474	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
		475
		476	# or like this
		477	staticperl mkbundle -MAnyEvent --eval 'AnyEvent::detect'
		478
		479	Example: use a separate "bootstrap" script that C<use>'s lots of modules
		480	and also include this in the final bundle, to be executed automatically
		481	when the interpreter is initialised.
		482
		483	staticperl mkbundle --eval 'do "bootstrap"' --boot bootstrap
		484
		485	=item C<--boot> F<filename>
		486
		487	Include the given file in the bundle and arrange for it to be
		488	executed (using C<require>) before the main program when the new perl
		489	is initialised. This can be used to modify C<@INC> or do similar
		490	modifications before the perl interpreter executes scripts given on the
		491	command line (or via C<-e>). This works even in an embedded interpreter -
		492	the file will be executed during interpreter initialisation in that case.
		493
		494	=item C<--incglob> pattern
		495
		496	This goes through all standard library directories and tries to match any
		497	F<.pm> and F<.pl> files against the extended glob pattern (see below). If
		498	a file matches, it is added. The pattern is matched against the full path
		499	of the file (sans the library directory prefix), e.g. F<Sys/Syslog.pm>.
		500
		501	This is very useful to include "everything":
		502
		503	--incglob '*'
		504
		505	It is also useful for including perl libraries, or trees of those, such as
		506	the unicode database files needed by some perl built-ins, the regex engine
		507	and other modules.
		508
		509	--incglob '/unicore/**.pl'
		510
		511	=item C<--add> F<file> \| C<--add> "F<file> alias"
		512
		513	Adds the given (perl) file into the bundle (and optionally call it
		514	"alias"). The F<file> is either an absolute path or a path relative to the
		515	current directory. If an alias is specified, then this is the name it will
		516	use for C<@INC> searches, otherwise the path F<file> will be used as the
		517	internal name.
		518
		519	This switch is used to include extra files into the bundle.
		520
		521	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
		522	when creating the bundle.
		523
		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'"
		533
		534	Example: add local files as extra modules in the bundle.
		535
		536	# specification file
		537	add file1 myfiles/file1.pm
		538	add file2 myfiles/file2.pm
		539	add file3 myfiles/file3.pl
		540
		541	# then later, in perl, use
		542	use myfiles::file1;
		543	require myfiles::file2;
		544	my $res = do "myfiles/file3.pl";
		545
		546	=item C<--binadd> F<file> \| C<--add> "F<file> alias"
		547
		548	Just like C<--add>, except that it treats the file as binary and adds it
		549	without any postprocessing (perl files might get stripped to reduce their
		550	size).
		551
		552	If you specify an alias you should probably add a C<&> prefix to avoid
		553	clashing with embedded perl files (whose paths never start with C<&>),
		554	and/or use a special directory prefix, such as C<&res/name>.
		555
		556	You can later get a copy of these files by calling C<staticperl::find
		557	"alias">.
		558
		559	An alternative way to embed binary files is to convert them to perl and
		560	use C<do> to get the contents - this method is a bit cumbersome, but works
		561	both inside and outside of a staticperl bundle:
		562
		563	# a "binary" file, call it "bindata.pl"
		564	<<'SOME_MARKER'
		565	binary data NOT containing SOME_MARKER
		566	SOME_MARKER
		567
		568	# load the binary
		569	chomp (my $data = do "bindata.pl");
		570
		571	=back
		572
		573	=item Step 2: filter all files using C<--include> and C<--exclude> options.
		574
		575	After all candidate files and modules are added, they are I<filtered>
		576	by a combination of C<--include> and C<--exclude> patterns (there is an
		577	implicit C<--include *> at the end, so if no filters are specified, all
		578	files are included).
		579
		580	All that this step does is potentially reduce the number of files that are
		581	to be included - no new files are added during this step.
		582
		583	=over 4
		584
		585	=item C<--include> pattern \| C<-i> pattern \| C<--exclude> pattern \| C<-x> pattern
		586
		587	These specify an include or exclude pattern to be applied to the candidate
		588	file list. An include makes sure that the given files will be part of the
		589	resulting file set, an exclude will exclude remaining files. The patterns
		590	are "extended glob patterns" (see below).
		591
		592	The patterns are applied "in order" - files included via earlier
		593	C<--include> specifications cannot be removed by any following
		594	C<--exclude>, and likewise, and file excluded by an earlier C<--exclude>
		595	cannot be added by any following C<--include>.
		596
		597	For example, to include everything except C<Devel> modules, but still
		598	include F<Devel::PPPort>, you could use this:
		599
		600	--incglob '' -i '/Devel/PPPort.pm' -x '/Devel/*'
		601
		602	=back
		603
		604	=item Step 3: add any extra or "hidden" dependencies.
		605
		606	F<staticperl> currently knows about three extra types of depdendencies
		607	that are added automatically. Only one (F<.packlist> files) is currently
		608	optional and can be influenced, the others are always included:
		609
		610	=over 4
		611
		612	=item C<--usepacklists>
		613
		614	Read F<.packlist> files for each distribution that happens to match a
		615	module name you specified. Sounds weird, and it is, so expect semantics to
		616	change somehow in the future.
		617
		618	The idea is that most CPAN distributions have a F<.pm> file that matches
		619	the name of the distribution (which is rather reasonable after all).
		620
		621	If this switch is enabled, then if any of the F<.pm> files that have been
		622	selected match an install distribution, then all F<.pm>, F<.pl>, F<.al>
		623	and F<.ix> files installed by this distribution are also included.
		624
		625	For example, using this switch, when the L<URI> module is specified, then
		626	all L<URI> submodules that have been installed via the CPAN distribution
		627	are included as well, so you don't have to manually specify them.
		628
		629	=item L<AutoLoader> splitfiles
		630
		631	Some modules use L<AutoLoader> - less commonly (hopefully) used functions
		632	are split into separate F<.al> files, and an index (F<.ix>) file contains
		633	the prototypes.
		634
		635	Both F<.ix> and F<.al> files will be detected automatically and added to
		636	the bundle.
		637
		638	=item link libraries (F<.a> files)
		639
		640	Modules using XS (or any other non-perl language extension compiled at
		641	installation time) will have a static archive (typically F<.a>). These
		642	will automatically be added to the linker options in F<bundle.ldopts>.
		643
		644	Should F<staticperl> find a dynamic link library (typically F<.so>) it
		645	will warn about it - obviously this shouldn't happen unless you use
		646	F<staticperl> on the wrong perl, or one (probably wrongly) configured to
		647	use dynamic loading.
		648
		649	=item extra libraries (F<extralibs.ld>)
		650
		651	Some modules need linking against external libraries - these are found in
		652	F<extralibs.ld> and added to F<bundle.ldopts>.
		653
		654	=back
		655
		656	=item Step 4: write bundle files and optionally link a program
		657
		658	At this point, the select files will be read, processed (stripped) and
		659	finally the bundle files get written to disk, and F<staticperl mkbundle>
		660	is normally finished. Optionally, it can go a step further and either link
		661	a new F<perl> binary with all selected modules and files inside, or build
		662	a standalone application.
		663
		664	Both the contents of the bundle files and any extra linking is controlled
		665	by these options:
		666
		667	=over 4
		668
357	=item --strip none\|pod\|ppi	669	=item C<--strip> C<none>\|C<pod>\|C<ppi>
358		670
359	Specify the stripping method applied to reduce the file of the perl	671	Specify the stripping method applied to reduce the file of the perl
360	sources included.	672	sources included.
361		673
362	The default is C<pod>, which uses the L<Pod::Strip> module to remove all	674	The default is C<pod>, which uses the L<Pod::Strip> module to remove all
…		…
373	Last not least, if you need accurate line numbers in error messages,	685	Last not least, if you need accurate line numbers in error messages,
374	or in the unlikely case where C<pod> is too slow, or some module gets	686	or in the unlikely case where C<pod> is too slow, or some module gets
375	mistreated, you can specify C<none> to not mangle included perl sources in	687	mistreated, you can specify C<none> to not mangle included perl sources in
376	any way.	688	any way.
377		689
378	=item --perl	690	=item C<--perl>
379		691
380	After writing out the bundle files, try to link a new perl interpreter. It	692	After writing out the bundle files, try to link a new perl interpreter. It
381	will be called F<perl> and will be left in the current working	693	will be called F<perl> and will be left in the current working
382	directory. The bundle files will be removed.	694	directory. The bundle files will be removed.
383		695
384	This switch is automatically used when F<staticperl> is invoked with the	696	This switch is automatically used when F<staticperl> is invoked with the
385	C<mkperl> command (instead of C<mkbundle>):	697	C<mkperl> command instead of C<mkbundle>.
386		698
387	# build a new ./perl with only common::sense in it - very small :)	699	Example: build a new F<./perl> binary with only L<common::sense> inside -
		700	it will be even smaller than the standard perl interpreter as none of the
		701	modules of the base distribution (such as L<Fcntl>) will be included.
		702
388	staticperl mkperl -Mcommon::sense	703	staticperl mkperl -Mcommon::sense
389		704
390	=item --app name	705	=item C<--app> F<name>
391		706
392	After writing out the bundle files, try to link a new standalone	707	After writing out the bundle files, try to link a new standalone
393	program. It will be called C<name>, and the bundle files get removed after	708	program. It will be called C<name>, and the bundle files get removed after
394	linking it.	709	linking it.
		710
		711	This switch is automatically used when F<staticperl> is invoked with the
		712	C<mkapp> command instead of C<mkbundle>.
395		713
396	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
397	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 -
398	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
399	exit.	717	exit.
400		718
401	This switch is automatically used when F<staticperl> is invoked with the	719	This means that, by default, it will do nothing but burn a few CPU cycles
402	C<mkapp> command (instead of C<mkbundle>):
403
404	To let it 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
405	the C<--boot> option.	721	the C<--boot> option.
406		722
407	Example: create a standalone perl binary that will execute F<appfile> when	723	Example: create a standalone perl binary called F<./myexe> that will
408	it is started.	724	execute F<appfile> when it is started.
409		725
410	staticperl mkbundle --app myexe --boot appfile	726	staticperl mkbundle --app myexe --boot appfile
411		727
412	=item --use module \| -Mmodule	728	=item C<--ignore-env>
413		729
414	Include the named module and all direct dependencies. This is done by	730	Generates extra code to unset some environment variables before
415	C<require>'ing the module in a subprocess and tracing which other modules	731	initialising/running perl. Perl supports a lot of environment variables
416	and files it actually loads. If the module uses L<AutoLoader>, then all	732	that might alter execution in ways that might be undesirablre for
417	splitfiles will be included as well.	733	standalone applications, and this option removes those known to cause
		734	trouble.
418		735
419	Example: include AnyEvent and AnyEvent::Impl::Perl.	736	Specifically, these are removed:
420		737
421	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl	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.
422		742
423	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or	743	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
424	maybe other weirdly named files. To do that, you need to quote the name in	744	startup code used by F<staticperl> overrides C<@INC> in all cases.
425	single or double quotes. When given on the command line, you probably need
426	to quote once more to avoid your shell interpreting it. Common cases that
427	need this are F<Config_heavy.pl> and F<utf8_heavy.pl>.
428		745
429	Example: include the required files for F<perl -V> to work in all its	746	This option will not make your program more secure (unless you are
430	glory (F<Config.pm> is included automatically by this).	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.
431		750
432	# bourne shell
433	staticperl mkbundle --use '"Config_heavy.pl"'
434
435	# bundle specification file
436	use "Config_heavy.pl"
437
438	The C<-Mmodule> syntax is included as an alias that might be easier to
439	remember than C<use>. Or maybe it confuses people. Time will tell. Or
440	maybe not. Argh.
441
442	=item --eval "perl code" \| -e "perl code"
443
444	Sometimes it is easier (or necessary) to specify dependencies using perl
445	code, or maybe one of the modules you use need a special use statement. In
446	that case, you can use C<eval> to execute some perl snippet or set some
447	variables or whatever you need. All files C<require>'d or C<use>'d in the
448	script are included in the final bundle.
449
450	Keep in mind that F<mkbundle> will only C<require> the modules named
451	by the C<--use> option, so do not expect the symbols from modules you
452	C<--use>'d earlier on the command line to be available.
453
454	Example: force L<AnyEvent> to detect a backend and therefore include it
455	in the final bundle.
456
457	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
458
459	# or like this
460	staticperl mkbundle -MAnyEvent --eval 'use AnyEvent; AnyEvent::detect'
461
462	Example: use a separate "bootstrap" script that C<use>'s lots of modules
463	and include this in the final bundle, to be executed automatically.
464
465	staticperl mkbundle --eval 'do "bootstrap"' --boot bootstrap
466
467	=item --boot filename
468
469	Include the given file in the bundle and arrange for it to be executed
470	(using a C<require>) before anything else when the new perl is
471	initialised. This can be used to modify C<@INC> or anything else before
472	the perl interpreter executes scripts given on the command line (or via
473	C<-e>). This works even in an embedded interpreter.
474
475	=item --usepacklist
476
477	Read F<.packlist> files for each distribution that happens to match a
478	module name you specified. Sounds weird, and it is, so expect semantics to
479	change somehow in the future.
480
481	The idea is that most CPAN distributions have a F<.pm> file that matches
482	the name of the distribution (which is rather reasonable after all).
483
484	If this switch is enabled, then if any of the F<.pm> files that have been
485	selected match an install distribution, then all F<.pm>, F<.pl>, F<.al>
486	and F<.ix> files installed by this distribution are also included.
487
488	For example, using this switch, when the L<URI> module is specified, then
489	all L<URI> submodules that have been installed via the CPAN distribution
490	are included as well, so you don't have to manually specify them.
491
492	=item --incglob pattern
493
494	This goes through all library directories and tries to match any F<.pm>
495	and F<.pl> files against the extended glob pattern (see below). If a file
496	matches, it is added. This switch will automatically detect L<AutoLoader>
497	files and the required link libraries for XS modules, but it will I<not>
498	scan the file for dependencies (at the moment).
499
500	This is mainly useful to include "everything":
501
502	--incglob '*'
503
504	Or to include perl libraries, or trees of those, such as the unicode
505	database files needed by many other modules:
506
507	--incglob '/unicore/**.pl'
508
509	=item --add file \| --add "file alias"
510
511	Adds the given (perl) file into the bundle (and optionally call it
512	"alias"). This is useful to include any custom files into the bundle.
513
514	Example: embed the file F<httpd> as F<httpd.pm> when creating the bundle.
515
516	staticperl mkperl --add "httpd httpd.pm"
517
518	It is also a great way to add any custom modules:
519
520	# specification file
521	add file1 myfiles/file1
522	add file2 myfiles/file2
523	add file3 myfiles/file3
524
525	=item --binadd file \| --add "file alias"
526
527	Just like C<--add>, except that it treats the file as binary and adds it
528	without any processing.
529
530	You should probably add a C</> prefix to avoid clashing with embedded
531	perl files (whose paths do not start with C</>), and/or use a special
532	directory, such as C</res/name>.
533
534	You can later get a copy of these files by calling C<staticperl::find
535	"alias">.
536
537	=item --include pattern \| -i pattern \| --exclude pattern \| -x pattern
538
539	These two options define an include/exclude filter that is used after all
540	files selected by the other options have been found. Each include/exclude
541	is applied to all files found so far - an include makes sure that the
542	given files will be part of the resulting file set, an exclude will
543	exclude files. The patterns are "extended glob patterns" (see below).
544
545	For example, to include everything, except C<Devel> modules, but still
546	include F<Devel::PPPort>, you could use this:
547
548	--incglob '' -i '/Devel/PPPort.pm' -x '/Devel/*'
549
550	=item --static	751	=item C<--static>
551		752
552	When C<--perl> is also given, link statically instead of dynamically. The	753	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
		754	supported by the OS) executable will be created. This is not immensely
		755	useful when just creating the bundle files, but is most useful when
		756	linking a binary with the C<--perl> or C<--app> options.
		757
553	default is to link the new perl interpreter fully dynamic (that means all	758	The default is to link the new binary dynamically (that means all perl
554	perl modules are linked statically, but all external libraries are still	759	modules are linked statically, but all external libraries are still
555	referenced dynamically).	760	referenced dynamically).
556		761
557	Keep in mind that Solaris doesn't support static linking at all, and	762	Keep in mind that Solaris doesn't support static linking at all, and
558	systems based on GNU libc don't really support it in a usable fashion	763	systems based on GNU libc don't really support it in a very usable
559	either. Try uClibc if you want to create fully statically linked	764	fashion either. Try uClibc if you want to create fully statically linked
560	executables, or try the C<--staticlibs> option to link only some libraries	765	executables, or try the C<--staticlib> option to link only some libraries
561	statically.	766	statically.
562		767
563	=item --staticlib libname	768	=item C<--staticlib> libname
564		769
565	When not linking fully statically, this option allows you to link specific	770	When not linking fully statically, this option allows you to link specific
566	libraries statically. What it does is simply replace all occurances of	771	libraries statically. What it does is simply replace all occurrences of
567	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>	772	C<-llibname> with the GCC-specific C<-Wl,-Bstatic -llibname -Wl,-Bdynamic>
568	option.	773	option.
569		774
570	This will have no effect unless the library is actually linked against,	775	This will have no effect unless the library is actually linked against,
571	specifically, C<--staticlib> will not link against the named library	776	specifically, C<--staticlib> will not link against the named library
572	unless it would be linked against anyway.	777	unless it would be linked against anyway.
573		778
574	Example: link libcrypt statically into the binary.	779	Example: link libcrypt statically into the final binary.
575		780
576	staticperl mkperl -MIO::AIO --staticlib crypt	781	staticperl mkperl -MIO::AIO --staticlib crypt
577		782
578	# ldopts might nwo contain:	783	# ldopts might now contain:
579	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread	784	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread
580		785
581	=item any other argument	786	=back
582
583	Any other argument is interpreted as a bundle specification file, which
584	supports most long options (without extra quoting), one option per line.
585		787
586	=back	788	=back
587		789
588	=head3 EXTENDED GLOB PATTERNS	790	=head3 EXTENDED GLOB PATTERNS
589		791
…		…
603	=item Patterns not starting with F</> will be anchored at the end of the path.	805	=item Patterns not starting with F</> will be anchored at the end of the path.
604		806
605	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the	807	That is, F<idna.pl> will match any file called F<idna.pl> anywhere in the
606	hierarchy, but not any directories of the same name.	808	hierarchy, but not any directories of the same name.
607		809
608	=item A F<*> matches any single component.	810	=item A F<*> matches anything within a single path component.
609		811
610	That is, F</unicore/*.pl> would match all F<.pl> files directly inside	812	That is, F</unicore/*.pl> would match all F<.pl> files directly inside
611	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>	813	C</unicore>, not any deeper level F<.pl> files. Or in other words, F<*>
612	will not match slashes.	814	will not match slashes.
613		815
…		…
688	installation, you can set any environment variable you want - some modules	890	installation, you can set any environment variable you want - some modules
689	(such as L<Coro> or L<EV>) use environment variables for further tweaking.	891	(such as L<Coro> or L<EV>) use environment variables for further tweaking.
690		892
691	=item C<PERL_VERSION>	893	=item C<PERL_VERSION>
692		894
693	The perl version to install - default is currently C<5.12.2>, but C<5.8.9>	895	The perl version to install - default is currently C<5.12.3>, but C<5.8.9>
694	is also a good choice (5.8.9 is much smaller than 5.12.2, while 5.10.1 is	896	is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is
695	about as big as 5.12.2).	897	about as big as 5.12.3).
696		898
697	=item C<PERL_PREFIX>	899	=item C<PERL_PREFIX>
698		900
699	The prefix where perl gets installed (default: F<$STATICPERL/perl>),	901	The prefix where perl gets installed (default: F<$STATICPERL/perl>),
700	i.e. where the F<bin> and F<lib> subdirectories will end up.	902	i.e. where the F<bin> and F<lib> subdirectories will end up.
…		…
721	F<~/.staticperlrc> to override them.	923	F<~/.staticperlrc> to override them.
722		924
723	Most of the variables override (or modify) the corresponding F<Configure>	925	Most of the variables override (or modify) the corresponding F<Configure>
724	variable, except C<PERL_CCFLAGS>, which gets appended.	926	variable, except C<PERL_CCFLAGS>, which gets appended.
725		927
		928	You should have a look near the beginning of the F<staticperl> script -
		929	staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options
		930	suitable for newer gcc versions. For other compilers or older versions you
		931	need to adjust these, for example, in your F<~/.staticperlrc>.
		932
726	=back	933	=back
727		934
728	=head4 Variables you probably I<do not want> to override	935	=head4 Variables you probably I<do not want> to override
729		936
730	=over 4	937	=over 4
…		…
748	=head3 OVERRIDABLE HOOKS	955	=head3 OVERRIDABLE HOOKS
749		956
750	In addition to environment variables, it is possible to provide some	957	In addition to environment variables, it is possible to provide some
751	shell functions that are called at specific times. To provide your own	958	shell functions that are called at specific times. To provide your own
752	commands, just define the corresponding function.	959	commands, just define the corresponding function.
		960
		961	The actual order in which hooks are invoked during a full install
		962	from scratch is C<preconfigure>, C<patchconfig>, C<postconfigure>,
		963	C<postbuild>, C<postinstall>.
753		964
754	Example: install extra modules from CPAN and from some directories	965	Example: install extra modules from CPAN and from some directories
755	at F<staticperl install> time.	966	at F<staticperl install> time.
756		967
757	postinstall() {	968	postinstall() {
…		…
764		975
765	=over 4	976	=over 4
766		977
767	=item preconfigure	978	=item preconfigure
768		979
769	Called just before running F<./Configur> in the perl source	980	Called just before running F<./Configure> in the perl source
770	directory. Current working directory is the perl source directory.	981	directory. Current working directory is the perl source directory.
771		982
772	This can be used to set any C<PERL_xxx> variables, which might be costly	983	This can be used to set any C<PERL_xxx> variables, which might be costly
773	to compute.	984	to compute.
774		985
		986	=item patchconfig
		987
		988	Called after running F<./Configure> in the perl source directory to create
		989	F<./config.sh>, but before running F<./Configure -S> to actually apply the
		990	config. Current working directory is the perl source directory.
		991
		992	Can be used to tailor/patch F<config.sh> or do any other modifications.
		993
775	=item postconfigure	994	=item postconfigure
776		995
777	Called after configuring, but before building perl. Current working	996	Called after configuring, but before building perl. Current working
778	directory is the perl source directory.	997	directory is the perl source directory.
779
780	Could be used to tailor/patch config.sh (followed by F<sh Configure -S>)
781	or do any other modifications.
782		998
783	=item postbuild	999	=item postbuild
784		1000
785	Called after building, but before installing perl. Current working	1001	Called after building, but before installing perl. Current working
786	directory is the perl source directory.	1002	directory is the perl source directory.
…		…
824	A header file that contains the prototypes of the few symbols "exported"	1040	A header file that contains the prototypes of the few symbols "exported"
825	by bundle.c, and also exposes the perl headers to the application.	1041	by bundle.c, and also exposes the perl headers to the application.
826		1042
827	=over 4	1043	=over 4
828		1044
829	=item staticperl_init ()	1045	=item staticperl_init (xs_init = 0)
830		1046
831	Initialises the perl interpreter. You can use the normal perl functions	1047	Initialises the perl interpreter. You can use the normal perl functions
832	after calling this function, for example, to define extra functions or	1048	after calling this function, for example, to define extra functions or
833	to load a .pm file that contains some initialisation code, or the main	1049	to load a .pm file that contains some initialisation code, or the main
834	program function:	1050	program function:
…		…
841	}	1057	}
842		1058
843	static void	1059	static void
844	run_myapp(void)	1060	run_myapp(void)
845	{	1061	{
846	staticperl_init ();	1062	staticperl_init (0);
847	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");	1063	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
848	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"	1064	eval_pv ("require myapp::main", 1); // executes "myapp/main.pm"
849	}	1065	}
850		1066
		1067	When your bootcode already wants to access some XS functions at
		1068	compiletime, then you need to supply an C<xs_init> function pointer that
		1069	is called as soon as perl is initialised enough to define XS functions,
		1070	but before the preamble code is executed:
		1071
		1072	static void
		1073	xs_init (pTHX)
		1074	{
		1075	newXSproto ("myapp::xsfunction", xsfunction, __FILE__, "$$;$");
		1076	}
		1077
		1078	static void
		1079	run_myapp(void)
		1080	{
		1081	staticperl_init (xs_init);
		1082	}
		1083
		1084	=item staticperl_cleanup ()
		1085
		1086	In the unlikely case that you want to destroy the perl interpreter, here
		1087	is the corresponding function.
		1088
851	=item staticperl_xs_init (pTHX)	1089	=item staticperl_xs_init (pTHX)
852		1090
853	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in	1091	Sometimes you need direct control over C<perl_parse> and C<perl_run>, in
854	which case you do not want to use C<staticperl_init> but call them on your	1092	which case you do not want to use C<staticperl_init> but call them on your
855	own.	1093	own.
856		1094
857	Then you need this function - either pass it directly as the C<xs_init>	1095	Then you need this function - either pass it directly as the C<xs_init>
858	function to C<perl_parse>, or call it from your own C<xs_init> function.	1096	function to C<perl_parse>, or call it as one of the first things from your
859		1097	own C<xs_init> function.
860	=item staticperl_cleanup ()
861
862	In the unlikely case that you want to destroy the perl interpreter, here
863	is the corresponding function.
864		1098
865	=item PerlInterpreter *staticperl	1099	=item PerlInterpreter *staticperl
866		1100
867	The perl interpreter pointer used by staticperl. Not normally so useful,	1101	The perl interpreter pointer used by staticperl. Not normally so useful,
868	but there it is.	1102	but there it is.
…		…
904		1138
905	Returns the list of all paths embedded in this binary.	1139	Returns the list of all paths embedded in this binary.
906		1140
907	=back	1141	=back
908		1142
909	=head1 FULLY STATIC BINARIES - BUILDROOT	1143	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
910		1144
911	To make truly static (Linux-) libraries, you might want to have a look at	1145	To make truly static (Linux-) libraries, you might want to have a look at
912	buildroot (L<http://buildroot.uclibc.org/>).	1146	buildroot (L<http://buildroot.uclibc.org/>).
913		1147
914	Buildroot is primarily meant to set up a cross-compile environment (which	1148	Buildroot is primarily meant to set up a cross-compile environment (which
…		…
975		1209
976	Some functionality in the utf8 module, such as swash handling (used	1210	Some functionality in the utf8 module, such as swash handling (used
977	for unicode character ranges in regexes) is implemented in the	1211	for unicode character ranges in regexes) is implemented in the
978	C<"utf8_heavy.pl"> library:	1212	C<"utf8_heavy.pl"> library:
979		1213
980	-M'"utf8_heavy.pl"'	1214	-Mutf8_heavy.pl
981		1215
982	Many Unicode properties in turn are defined in separate modules,	1216	Many Unicode properties in turn are defined in separate modules,
983	such as C<"unicore/Heavy.pl"> and more specific data tables such as	1217	such as C<"unicore/Heavy.pl"> and more specific data tables such as
984	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables	1218	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables
985	are big (7MB uncompressed, although F<staticperl> contains special	1219	are big (7MB uncompressed, although F<staticperl> contains special
986	handling for those files), so including them on demand by your application	1220	handling for those files), so including them on demand by your application
987	only might pay off.	1221	only might pay off.
988		1222
989	To simply include the whole unicode database, use:	1223	To simply include the whole unicode database, use:
990		1224
991	--incglob '/unicore/*.pl'	1225	--incglob '/unicore/**.pl'
992		1226
993	=item AnyEvent	1227	=item AnyEvent
994		1228
995	AnyEvent needs a backend implementation that it will load in a delayed	1229	AnyEvent needs a backend implementation that it will load in a delayed
996	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice	1230	fashion. The L<AnyEvent::Impl::Perl> backend is the default choice
…		…
1001		1235
1002	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn	1236	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn
1003	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and	1237	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and
1004	C<"AnyEvent/Util/uts46data.pl">.	1238	C<"AnyEvent/Util/uts46data.pl">.
1005		1239
1006	Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include	1240	Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include
1007	everything.	1241	everything.
		1242
		1243	=item Cairo
		1244
		1245	See Glib, same problem, same solution.
1008		1246
1009	=item Carp	1247	=item Carp
1010		1248
1011	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1249	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
1012	perl 5.12.2 (maybe earlier), this dependency no longer exists.	1250	perl 5.12.2 (maybe earlier), this dependency no longer exists.
…		…
1015		1253
1016	The F<perl -V> switch (as well as many modules) needs L<Config>, which in	1254	The F<perl -V> switch (as well as many modules) needs L<Config>, which in
1017	turn might need L<"Config_heavy.pl">. Including the latter gives you	1255	turn might need L<"Config_heavy.pl">. Including the latter gives you
1018	both.	1256	both.
1019		1257
		1258	=item Glib
		1259
		1260	Glib literally requires Glib to be installed already to build - it tries
		1261	to fake this by running Glib out of the build directory before being
		1262	built. F<staticperl> tries to work around this by forcing C<MAN1PODS> and
		1263	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
		1264
		1265	=item Gtk2
		1266
		1267	See Pango, same problems, same solution.
		1268
		1269	=item Pango
		1270
		1271	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
		1272	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>
		1273	tries to patch L<ExtUtils::MM_Unix> to route around Pango.
		1274
1020	=item Term::ReadLine::Perl	1275	=item Term::ReadLine::Perl
1021		1276
1022	Also needs L<Term::ReadLine::readline>, or C<--usepacklist>.	1277	Also needs L<Term::ReadLine::readline>, or C<--usepacklists>.
1023		1278
1024	=item URI	1279	=item URI
1025		1280
1026	URI implements schemes as separate modules - the generic URL scheme is	1281	URI implements schemes as separate modules - the generic URL scheme is
1027	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If	1282	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If
1028	you need to use any of these schemes, you should include these manually,	1283	you need to use any of these schemes, you should include these manually,
1029	or use C<--usepacklist>.	1284	or use C<--usepacklists>.
1030		1285
1031	=back	1286	=back
1032		1287
1033	=head2 RECIPES	1288	=head2 RECIPES
1034		1289
1035	=over 4	1290	=over 4
1036		1291
1037	=item Linking everything in	1292	=item Just link everything in
1038		1293
1039	To link just about everything installed in the perl library into a new	1294	To link just about everything installed in the perl library into a new
1040	perl, try this:	1295	perl, try this (the first time this runs it will take a long time, as a
		1296	lot of files need to be parsed):
1041		1297
1042	staticperl mkperl --strip ppi --incglob '*'	1298	staticperl mkperl -v --strip ppi --incglob '*'
1043		1299
		1300	If you don't mind the extra megabytes, this can be a very effective way of
		1301	creating bundles without having to worry about forgetting any modules.
		1302
		1303	You get even more useful variants of this method by first selecting
		1304	everything, and then excluding stuff you are reasonable sure not to need -
		1305	L<bigperl\|http://staticperl.schmorp.de/bigperl.html> uses this approach.
		1306
1044	=item Getting rid of netdb function	1307	=item Getting rid of netdb functions
1045		1308
1046	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>	1309	The perl core has lots of netdb functions (C<getnetbyname>, C<getgrent>
1047	and so on) that few applications use. You can avoid compiling them in by	1310	and so on) that few applications use. You can avoid compiling them in by
1048	putting the following fragment into a C<preconfigure> hook:	1311	putting the following fragment into a C<preconfigure> hook:
1049		1312
…		…
1066	do	1329	do
1067	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"	1330	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
1068	done	1331	done
1069	}	1332	}
1070		1333
1071	This mostly gains space when linking staticaly, as the functions will	1334	This mostly gains space when linking statically, as the functions will
1072	likely not be linked in. The gain for dynamically-linked binaries is	1335	likely not be linked in. The gain for dynamically-linked binaries is
1073	smaller.	1336	smaller.
1074		1337
1075	Also, this leaves C<gethostbyname> in - not only is it actually used	1338	Also, this leaves C<gethostbyname> in - not only is it actually used
1076	often, the L<Socket> module also exposes it, so leaving it out usually	1339	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.24 by root, Wed Dec 15 00:17:47 2010 UTC vs. Revision 1.40 by root, Sun May 1 09:29:47 2011 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.24 by root, Wed Dec 15 00:17:47 2010 UTC vs.
Revision 1.40 by root, Sun May 1 09:29:47 2011 UTC