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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.19 by root, Fri Dec 10 15:25:24 2010 UTC vs.
Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC

…		…
40		40
41	With F<uClibc> and F<upx> on x86, you can create a single 500kb binary	41	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,	42	that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO,
43	Coro and so on. Or any other choice of modules.	43	Coro and so on. Or any other choice of modules.
44		44
		45	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	modules: just follow the links at L<http://staticperl.schmorp.de/>.
		48
45	The created files do not need write access to the file system (like PAR	49	The created files do not need write access to the file system (like PAR
46	does). In fact, since this script is in many ways similar to PAR::Packer,	50	does). In fact, since this script is in many ways similar to PAR::Packer,
47	here are the differences:	51	here are the differences:
48		52
49	=over 4	53	=over 4
…		…
118	often as necessary.	122	often as necessary.
119		123
120	=head1 THE F<STATICPERL> SCRIPT	124	=head1 THE F<STATICPERL> SCRIPT
121		125
122	This module installs a script called F<staticperl> into your perl	126	This module installs a script called F<staticperl> into your perl
123	binary directory. The script is fully self-contained, and can be used	127	binary directory. The script is fully self-contained, and can be
124	without perl (for example, in an uClibc chroot environment). In fact,	128	used without perl (for example, in an uClibc chroot environment). In
125	it can be extracted from the C<App::Staticperl> distribution tarball as	129	fact, it can be extracted from the C<App::Staticperl> distribution
126	F<bin/staticperl>, without any installation.	130	tarball as F<bin/staticperl>, without any installation. The
		131	newest (possibly alpha) version can also be downloaded from
		132	L<http://staticperl.schmorp.de/staticperl>.
127		133
128	F<staticperl> interprets the first argument as a command to execute,	134	F<staticperl> interprets the first argument as a command to execute,
129	optionally followed by any parameters.	135	optionally followed by any parameters.
130		136
131	There are two command categories: the "phase 1" commands which deal with	137	There are two command categories: the "phase 1" commands which deal with
…		…
141		147
142	The command	148	The command
143		149
144	staticperl install	150	staticperl install
145		151
146	Is normally all you need: It installs the perl interpreter in	152	is normally all you need: It installs the perl interpreter in
147	F<~/.staticperl/perl>. It downloads, configures, builds and installs the	153	F<~/.staticperl/perl>. It downloads, configures, builds and installs the
148	perl interpreter if required.	154	perl interpreter if required.
149		155
150	Most of the following commands simply run one or more steps of this	156	Most of the following F<staticperl> subcommands simply run one or more
151	sequence.	157	steps of this sequence.
		158
		159	If it fails, then most commonly because the compiler options I selected
		160	are not supported by your compiler - either edit the F<staticperl> script
		161	yourself or create F<~/.staticperl> shell script where your set working
		162	C<PERL_CCFLAGS> etc. variables.
152		163
153	To force recompilation or reinstallation, you need to run F<staticperl	164	To force recompilation or reinstallation, you need to run F<staticperl
154	distclean> first.	165	distclean> first.
155		166
156	=over 4	167	=over 4
		168
		169	=item F<staticperl version>
		170
		171	Prints some info about the version of the F<staticperl> script you are using.
157		172
158	=item F<staticperl fetch>	173	=item F<staticperl fetch>
159		174
160	Runs only the download and unpack phase, unless this has already happened.	175	Runs only the download and unpack phase, unless this has already happened.
161		176
…		…
199		214
200	=item F<staticperl clean>	215	=item F<staticperl clean>
201		216
202	Deletes the perl source directory (and potentially cleans up other	217	Deletes the perl source directory (and potentially cleans up other
203	intermediate files). This can be used to clean up files only needed for	218	intermediate files). This can be used to clean up files only needed for
204	building perl, without removing the installed perl interpreter, or to	219	building perl, without removing the installed perl interpreter.
205	force a re-build from scratch.
206		220
207	At the moment, it doesn't delete downloaded tarballs.	221	At the moment, it doesn't delete downloaded tarballs.
		222
		223	The exact semantics of this command will probably change.
208		224
209	=item F<staticperl distclean>	225	=item F<staticperl distclean>
210		226
211	This wipes your complete F<~/.staticperl> directory. Be careful with this,	227	This wipes your complete F<~/.staticperl> directory. Be careful with this,
212	it nukes your perl download, perl sources, perl distribution and any	228	it nukes your perl download, perl sources, perl distribution and any
…		…
262	-MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI::http	278	-MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI::http
263		279
264	# run it	280	# run it
265	./app	281	./app
266		282
		283	Here are the three phase 2 commands:
		284
		285	=over 4
		286
		287	=item F<staticperl mkbundle> args...
		288
		289	The "default" bundle command - it interprets the given bundle options and
		290	writes out F<bundle.h>, F<bundle.c>, F<bundle.ccopts> and F<bundle.ldopts>
		291	files, useful for embedding.
		292
		293	=item F<staticperl mkperl> args...
		294
		295	Creates a bundle just like F<staticperl mkbundle> (in fact, it's the same
		296	as invoking F<staticperl mkbundle --perl> args...), but then compiles and
		297	links a new perl interpreter that embeds the created bundle, then deletes
		298	all intermediate files.
		299
		300	=item F<staticperl mkapp> filename args...
		301
		302	Does the same as F<staticperl mkbundle> (in fact, it's the same as
		303	invoking F<staticperl mkbundle --app> filename args...), but then compiles
		304	and links a new standalone application that simply initialises the perl
		305	interpreter.
		306
		307	The difference to F<staticperl mkperl> is that the standalone application
		308	does not act like a perl interpreter would - in fact, by default it would
		309	just do nothing and exit immediately, so you should specify some code to
		310	be executed via the F<--boot> option.
		311
		312	=back
		313
267	=head3 OPTION PROCESSING	314	=head3 OPTION PROCESSING
268		315
269	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
270	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
271	specifying a lot of modules can make the command line very cumbersome,	318	specifying a lot of options can make the command line very long and
272	you can put all long options into a "bundle specification file" (with or	319	unwieldy, you can put all long options into a "bundle specification file"
273	without C<--> prefix) and specify this bundle file instead.	320	(one option per line, with or without C<--> prefix) and specify this
		321	bundle file instead.
274		322
275	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:
276		325
277	staticperl mkperl httpd.bundle	326	staticperl mkperl httpd.bundle
278		327
279	And all options could be in F<httpd.bundle>:	328	With all options stored in the F<httpd.bundle> file (one option per line,
280		329	everything after the option is an argument):
		330
281	use "Config_heavy.pl"	331	use "Config_heavy.pl"
282	use AnyEvent::Impl::Perl	332	use AnyEvent::Impl::Perl
283	use AnyEvent::HTTPD	333	use AnyEvent::HTTPD
284	use URI::http	334	use URI::http
285	add eg/httpd httpd.pm	335	add eg/httpd httpd.pm
286		336
287	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
288	order given on the command line (that affects the C<--use> and C<--eval>	338	order given on the command line.
289	options at the moment).
290		339
291	=head3 PACKAGE SELECTION WORKFLOW	340	=head3 BUNDLE CREATION WORKFLOW / STATICPELR MKBUNDLE OPTIONS
292		341
293	F<staticperl mkbundle> has a number of options to control package	342	F<staticperl mkbundle> works by first assembling a list of candidate
294	selection. This section describes how they interact with each other. Also,	343	files and modules to include, then filtering them by include/exclude
295	since I am still a newbie w.r.t. these issues, maybe future versions of	344	patterns. The remaining modules (together with their direct dependencies,
296	F<staticperl> will change this, so watch out :)	345	such as link libraries and L<AutoLoader> files) are then converted into
		346	bundle files suitable for embedding. F<staticperl mkbundle> can then
		347	optionally build a new perl interpreter or a standalone application.
297		348
298	The idiom "in order" means "in order that they are specified on the
299	commandline". If you use a bundle specification file, then the options
300	will be processed as if they were given in place of the bundle file name.
301
302	=over 4	349	=over 4
303		350
304	=item 1. apply all C<--use>, C<--eval>, C<--add>, C<--addbin> and	351	=item Step 0: Generic argument processing.
305	C<--incglob> options, in order.
306		352
307	In addition, C<--use> and C<--eval> dependencies will be added when the	353	The following options influence F<staticperl mkbundle> itself.
308	options are processed.
309		354
310	=item 2. apply all C<--include> and C<--exclude> options, in order.
311
312	All this step does is potentially reduce the number of files already
313	selected or found in phase 1.
314
315	=item 3. find all modules (== F<.pm> files), gather their static archives
316	(F<.a>) and AutoLoader splitfiles (F<.ix> and F<.al> files) and find any
317	extra libraries they need for linking (F<extralibs.ld>).
318
319	This step is required to link against XS extensions and also adds files
320	required for L<AutoLoader> to do it's job.
321
322	=back
323
324	After this, all the files selected for bundling will be read and processed
325	(stripped), the bundle files will be written, and optionally a new F<perl>
326	or application binary will be linked.
327
328	=head3 MKBUNDLE OPTIONS
329
330	=over 4	355	=over 4
331		356
332	=item --verbose \| -v	357	=item C<--verbose> \| C<-v>
333		358
334	Increases the verbosity level by one (the default is C<1>).	359	Increases the verbosity level by one (the default is C<1>).
335		360
336	=item --quiet \| -q	361	=item C<--quiet> \| C<-q>
337		362
338	Decreases the verbosity level by one.	363	Decreases the verbosity level by one.
339		364
		365	=item any other argument
		366
		367	Any other argument is interpreted as a bundle specification file, which
		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.
		372
		373	=back
		374
		375	=item Step 1: gather candidate files and modules
		376
		377	In this step, modules, perl libraries (F<.pl> files) and other files are
		378	selected for inclusion in the bundle. The relevant options are executed
		379	in order (this makes a difference mostly for C<--eval>, which can rely on
		380	earlier C<--use> options to have been executed).
		381
		382	=over 4
		383
		384	=item C<--use> F<module> \| C<-M>F<module>
		385
		386	Include the named module and trace direct dependencies. This is done by
		387	C<require>'ing the module in a subprocess and tracing which other modules
		388	and files it actually loads.
		389
		390	Example: include AnyEvent and AnyEvent::Impl::Perl.
		391
		392	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
		393
		394	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
		395	maybe other weirdly named files. To do that, you need to quote the name in
		396	single or double quotes. When given on the command line, you probably need
		397	to quote once more to avoid your shell interpreting it. Common cases that
		398	need this are F<Config_heavy.pl> and F<utf8_heavy.pl>.
		399
		400	Example: include the required files for F<perl -V> to work in all its
		401	glory (F<Config.pm> is included automatically by this).
		402
		403	# bourne shell
		404	staticperl mkbundle --use '"Config_heavy.pl"'
		405
		406	# bundle specification file
		407	use "Config_heavy.pl"
		408
		409	The C<-M>module syntax is included as an alias that might be easier to
		410	remember than C<--use>. Or maybe it confuses people. Time will tell. Or
		411	maybe not. Sigh.
		412
		413	=item C<--eval> "perl code" \| C<-e> "perl code"
		414
		415	Sometimes it is easier (or necessary) to specify dependencies using perl
		416	code, or maybe one of the modules you use need a special use statement. In
		417	that case, you can use C<--eval> to execute some perl snippet or set some
		418	variables or whatever you need. All files C<require>'d or C<use>'d while
		419	executing the snippet are included in the final bundle.
		420
		421	Keep in mind that F<mkbundle> will only C<require> the modules named
		422	by the C<--use> option, so do not expect the symbols from modules you
		423	C<--use>'d earlier on the command line to be available.
		424
		425	Example: force L<AnyEvent> to detect a backend and therefore include it
		426	in the final bundle.
		427
		428	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
		429
		430	# or like this
		431	staticperl mkbundle -MAnyEvent --eval 'AnyEvent::detect'
		432
		433	Example: use a separate "bootstrap" script that C<use>'s lots of modules
		434	and also include this in the final bundle, to be executed automatically
		435	when the interpreter is initialised.
		436
		437	staticperl mkbundle --eval 'do "bootstrap"' --boot bootstrap
		438
		439	=item C<--boot> F<filename>
		440
		441	Include the given file in the bundle and arrange for it to be
		442	executed (using C<require>) before the main program when the new perl
		443	is initialised. This can be used to modify C<@INC> or do similar
		444	modifications before the perl interpreter executes scripts given on the
		445	command line (or via C<-e>). This works even in an embedded interpreter -
		446	the file will be executed during interpreter initialisation in that case.
		447
		448	=item C<--incglob> pattern
		449
		450	This goes through all standard library directories and tries to match any
		451	F<.pm> and F<.pl> files against the extended glob pattern (see below). If
		452	a file matches, it is added. The pattern is matched against the full path
		453	of the file (sans the library directory prefix), e.g. F<Sys/Syslog.pm>.
		454
		455	This is very useful to include "everything":
		456
		457	--incglob '*'
		458
		459	It is also useful for including perl libraries, or trees of those, such as
		460	the unicode database files needed by some perl builtins, the regex engine
		461	and other modules.
		462
		463	--incglob '/unicore/**.pl'
		464
		465	=item C<--add> F<file> \| C<--add> "F<file> alias"
		466
		467	Adds the given (perl) file into the bundle (and optionally call it
		468	"alias"). The F<file> is either an absolute path or a path relative to
		469	the current directory. If an alias is specified, then this is the name it
		470	will use for C<@INC> searches, otherfile the F<file> will be used as the
		471	internal name.
		472
		473	This switch is used to include extra files into the bundle.
		474
		475	Example: embed the file F<httpd> in the current directory as F<httpd.pm>
		476	when creating the bundle.
		477
		478	staticperl mkperl --add "httpd httpd.pm"
		479
		480	Example: add local files as extra modules in the bundle.
		481
		482	# specification file
		483	add file1 myfiles/file1.pm
		484	add file2 myfiles/file2.pm
		485	add file3 myfiles/file3.pl
		486
		487	# then later, in perl, use
		488	use myfiles::file1;
		489	require myfiles::file2;
		490	my $res = do "myfiles/file3.pl";
		491
		492	=item C<--binadd> F<file> \| C<--add> "F<file> alias"
		493
		494	Just like C<--add>, except that it treats the file as binary and adds it
		495	without any postprocessing (perl files might get stripped to reduce their
		496	size).
		497
		498	You should probably add a C</> prefix to avoid clashing with embedded perl
		499	files (whose paths do not start with C</>), and/or use a special directory
		500	prefix, such as C</res/name>.
		501
		502	You can later get a copy of these files by calling C<staticperl::find
		503	"alias">.
		504
		505	An alternative way to embed binary files is to convert them to perl and
		506	use C<do> to get the contents - this method is a bit cumbersome, but works
		507	both inside and outside of a staticperl bundle:
		508
		509	# a "binary" file, call it "bindata.pl"
		510	<<'SOME_MARKER'
		511	binary data NOT containing SOME_MARKER
		512	SOME_MARKER
		513
		514	# load the binary
		515	chomp (my $data = do "bindata.pl");
		516
		517	=back
		518
		519	=item Step 2: filter all files using C<--include> and C<--exclude> options.
		520
		521	After all candidate files and modules are added, they are I<filtered>
		522	by a combination of C<--include> and C<--exclude> patterns (there is an
		523	implicit C<--include **> at the end, so if no filters are specified, all
		524	files are included).
		525
		526	All that this step does is potentially reduce the number of files that are
		527	to be included - no new files are added during this step.
		528
		529	=over 4
		530
		531	=item C<--include> pattern \| C<-i> pattern \| C<--exclude> pattern \| C<-x> pattern
		532
		533	These specify an include or exclude pattern to be applied to the candidate
		534	file list. An include makes sure that the given files will be part of the
		535	resulting file set, an exclude will exclude remaining files. The patterns
		536	are "extended glob patterns" (see below).
		537
		538	The patterns are applied "in order" - files included via earlier
		539	C<--include> specifications cannot be removed by any following
		540	C<--exclude>, and likewise, and file excluded by an earlier C<--exclude>
		541	cannot be added by any following C<--include>.
		542
		543	For example, to include everything except C<Devel> modules, but still
		544	include F<Devel::PPPort>, you could use this:
		545
		546	--incglob '' -i '/Devel/PPPort.pm' -x '/Devel/*'
		547
		548	=back
		549
		550	=item Step 3: add any extra or "hidden" dependencies.
		551
		552	F<staticperl> currently knows about three extra types of depdendencies
		553	that are added automatically. Only one (F<.packlist> files) is currently
		554	optional and can be influenced, the others are always included:
		555
		556	=over 4
		557
		558	=item C<--usepacklist>
		559
		560	Read F<.packlist> files for each distribution that happens to match a
		561	module name you specified. Sounds weird, and it is, so expect semantics to
		562	change somehow in the future.
		563
		564	The idea is that most CPAN distributions have a F<.pm> file that matches
		565	the name of the distribution (which is rather reasonable after all).
		566
		567	If this switch is enabled, then if any of the F<.pm> files that have been
		568	selected match an install distribution, then all F<.pm>, F<.pl>, F<.al>
		569	and F<.ix> files installed by this distribution are also included.
		570
		571	For example, using this switch, when the L<URI> module is specified, then
		572	all L<URI> submodules that have been installed via the CPAN distribution
		573	are included as well, so you don't have to manually specify them.
		574
		575	=item L<AutoLoader> splitfiles
		576
		577	Some modules use L<AutoLoader> - less commonly (hopefully) used functions
		578	are split into separate F<.al> files, and an index (F<.ix>) file contains
		579	the prototypes.
		580
		581	Both F<.ix> and F<.al> files will be detected automatically and added to
		582	the bundle.
		583
		584	=item link libraries (F<.a> files)
		585
		586	Modules using XS (or any other non-perl language extension compiled at
		587	installation time) will have a static archive (typically F<.a>). These
		588	will automatically be added to the linker options in F<bundle.ldopts>.
		589
		590	Should F<staticperl> find a dynamic link library (typically F<.so>) it
		591	will warn about it - obviously this shouldn't happen unless you use
		592	F<staticperl> on the wrong perl, or one (probably wrongly) configured to
		593	use dynamic loading.
		594
		595	=item extra libraries (F<extralibs.ld>)
		596
		597	Some modules need linking against external libraries - these are found in
		598	F<extralibs.ld> and added to F<bundle.ldopts>.
		599
		600	=back
		601
		602	=item Step 4: write bundle files and optionally link a program
		603
		604	At this point, the select files will be read, processed (stripped) and
		605	finally the bundle files get written to disk, and F<staticperl mkbundle>
		606	is normally finished. Optionally, it can go a step further and either link
		607	a new F<perl> binary with all selected modules and files inside, or build
		608	a standalone application.
		609
		610	Both the contents of the bundle files and any extra linking is controlled
		611	by these options:
		612
		613	=over 4
		614
340	=item --strip none\|pod\|ppi	615	=item C<--strip> C<none>\|C<pod>\|C<ppi>
341		616
342	Specify the stripping method applied to reduce the file of the perl	617	Specify the stripping method applied to reduce the file of the perl
343	sources included.	618	sources included.
344		619
345	The default is C<pod>, which uses the L<Pod::Strip> module to remove all	620	The default is C<pod>, which uses the L<Pod::Strip> module to remove all
…		…
363	After writing out the bundle files, try to link a new perl interpreter. It	638	After writing out the bundle files, try to link a new perl interpreter. It
364	will be called F<perl> and will be left in the current working	639	will be called F<perl> and will be left in the current working
365	directory. The bundle files will be removed.	640	directory. The bundle files will be removed.
366		641
367	This switch is automatically used when F<staticperl> is invoked with the	642	This switch is automatically used when F<staticperl> is invoked with the
368	C<mkperl> command (instead of C<mkbundle>):	643	C<mkperl> command instead of C<mkbundle>.
369		644
370	# build a new ./perl with only common::sense in it - very small :)	645	Example: build a new F<./perl> binary with only L<common::sense> inside -
		646	it will be even smaller than the standard perl interpreter as none of the
		647	modules of the base distribution (such as L<Fcntl>) will be included.
		648
371	staticperl mkperl -Mcommon::sense	649	staticperl mkperl -Mcommon::sense
372		650
373	=item --app name	651	=item --app name
374		652
375	After writing out the bundle files, try to link a new standalone	653	After writing out the bundle files, try to link a new standalone
376	program. It will be called C<name>, and the bundle files get removed after	654	program. It will be called C<name>, and the bundle files get removed after
377	linking it.	655	linking it.
		656
		657	This switch is automatically used when F<staticperl> is invoked with the
		658	C<mkapp> command instead of C<mkbundle>.
378		659
379	The difference to the (mutually exclusive) C<--perl> option is that the	660	The difference to the (mutually exclusive) C<--perl> option is that the
380	binary created by this option will not try to act as a perl interpreter -	661	binary created by this option will not try to act as a perl interpreter -
381	instead it will simply initialise the perl interpreter, clean it up and	662	instead it will simply initialise the perl interpreter, clean it up and
382	exit.	663	exit.
383		664
384	This switch is automatically used when F<staticperl> is invoked with the	665	This means that, by default, it will do nothing but burna few CPU cycles
385	C<mkapp> command (instead of C<mkbundle>):
386
387	To let it do something useful you I<must> add some boot code, e.g. with	666	- for it to do something useful you I<must> add some boot code, e.g. with
388	the C<--boot> option.	667	the C<--boot> option.
389		668
390	Example: create a standalone perl binary that will execute F<appfile> when	669	Example: create a standalone perl binary called F<./myexe> that will
391	it is started.	670	execute F<appfile> when it is started.
392		671
393	staticperl mkbundle --app myexe --boot appfile	672	staticperl mkbundle --app myexe --boot appfile
394		673
395	=item --use module \| -Mmodule
396
397	Include the named module and all direct dependencies. This is done by
398	C<require>'ing the module in a subprocess and tracing which other modules
399	and files it actually loads. If the module uses L<AutoLoader>, then all
400	splitfiles will be included as well.
401
402	Example: include AnyEvent and AnyEvent::Impl::Perl.
403
404	staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl
405
406	Sometimes you want to load old-style "perl libraries" (F<.pl> files), or
407	maybe other weirdly named files. To do that, you need to quote the name in
408	single or double quotes. When given on the command line, you probably need
409	to quote once more to avoid your shell interpreting it. Common cases that
410	need this are F<Config_heavy.pl> and F<utf8_heavy.pl>.
411
412	Example: include the required files for F<perl -V> to work in all its
413	glory (F<Config.pm> is included automatically by this).
414
415	# bourne shell
416	staticperl mkbundle --use '"Config_heavy.pl"'
417
418	# bundle specification file
419	use "Config_heavy.pl"
420
421	The C<-Mmodule> syntax is included as an alias that might be easier to
422	remember than C<use>. Or maybe it confuses people. Time will tell. Or
423	maybe not. Argh.
424
425	=item --eval "perl code" \| -e "perl code"
426
427	Sometimes it is easier (or necessary) to specify dependencies using perl
428	code, or maybe one of the modules you use need a special use statement. In
429	that case, you can use C<eval> to execute some perl snippet or set some
430	variables or whatever you need. All files C<require>'d or C<use>'d in the
431	script are included in the final bundle.
432
433	Keep in mind that F<mkbundle> will only C<require> the modules named
434	by the C<--use> option, so do not expect the symbols from modules you
435	C<--use>'d earlier on the command line to be available.
436
437	Example: force L<AnyEvent> to detect a backend and therefore include it
438	in the final bundle.
439
440	staticperl mkbundle --eval 'use AnyEvent; AnyEvent::detect'
441
442	# or like this
443	staticperl mkbundle -MAnyEvent --eval 'use AnyEvent; AnyEvent::detect'
444
445	Example: use a separate "bootstrap" script that C<use>'s lots of modules
446	and include this in the final bundle, to be executed automatically.
447
448	staticperl mkbundle --eval 'do "bootstrap"' --boot bootstrap
449
450	=item --boot filename
451
452	Include the given file in the bundle and arrange for it to be executed
453	(using a C<require>) before anything else when the new perl is
454	initialised. This can be used to modify C<@INC> or anything else before
455	the perl interpreter executes scripts given on the command line (or via
456	C<-e>). This works even in an embedded interpreter.
457
458	=item --incglob pattern
459
460	This goes through all library directories and tries to match any F<.pm>
461	and F<.pl> files against the extended glob pattern (see below). If a file
462	matches, it is added. This switch will automatically detect L<AutoLoader>
463	files and the required link libraries for XS modules, but it will I<not>
464	scan the file for dependencies (at the moment).
465
466	This is mainly useful to include "everything":
467
468	--incglob '*'
469
470	Or to include perl libraries, or trees of those, such as the unicode
471	database files needed by many other modules:
472
473	--incglob '/unicore/**.pl'
474
475	=item --add file \| --add "file alias"
476
477	Adds the given (perl) file into the bundle (and optionally call it
478	"alias"). This is useful to include any custom files into the bundle.
479
480	Example: embed the file F<httpd> as F<httpd.pm> when creating the bundle.
481
482	staticperl mkperl --add "httpd httpd.pm"
483
484	It is also a great way to add any custom modules:
485
486	# specification file
487	add file1 myfiles/file1
488	add file2 myfiles/file2
489	add file3 myfiles/file3
490
491	=item --binadd file \| --add "file alias"
492
493	Just like C<--add>, except that it treats the file as binary and adds it
494	without any processing.
495
496	You should probably add a C</> prefix to avoid clashing with embedded
497	perl files (whose paths do not start with C</>), and/or use a special
498	directory, such as C</res/name>.
499
500	You can later get a copy of these files by calling C<staticperl::find
501	"alias">.
502
503	=item --include pattern \| -i pattern \| --exclude pattern \| -x pattern
504
505	These two options define an include/exclude filter that is used after all
506	files selected by the other options have been found. Each include/exclude
507	is applied to all files found so far - an include makes sure that the
508	given files will be part of the resulting file set, an exclude will
509	exclude files. The patterns are "extended glob patterns" (see below).
510
511	For example, to include everything, except C<Devel> modules, but still
512	include F<Devel::PPPort>, you could use this:
513
514	--incglob '' -i '/Devel/PPPort.pm' -x '/Devel/*'
515
516	=item --static	674	=item --static
517		675
518	When C<--perl> is also given, link statically instead of dynamically. The	676	Add C<-static> to F<bundle.ldopts>, which means a fully static (if
		677	supported by the OS) executable will be created. This is not immensely
		678	useful when just creating the bundle files, but is most useful when
		679	linking a binary with the C<--perl> or C<--app> options.
		680
519	default is to link the new perl interpreter fully dynamic (that means all	681	The default is to link the new binary dynamically (that means all perl
520	perl modules are linked statically, but all external libraries are still	682	modules are linked statically, but all external libraries are still
521	referenced dynamically).	683	referenced dynamically).
522		684
523	Keep in mind that Solaris doesn't support static linking at all, and	685	Keep in mind that Solaris doesn't support static linking at all, and
524	systems based on GNU libc don't really support it in a usable fashion	686	systems based on GNU libc don't really support it in a very usable
525	either. Try uClibc if you want to create fully statically linked	687	fashion either. Try uClibc if you want to create fully statically linked
526	executables, or try the C<--staticlibs> option to link only some libraries	688	executables, or try the C<--staticlib> option to link only some libraries
527	statically.	689	statically.
528		690
529	=item --staticlib libname	691	=item --staticlib libname
530		692
531	When not linking fully statically, this option allows you to link specific	693	When not linking fully statically, this option allows you to link specific
…		…
539		701
540	Example: link libcrypt statically into the binary.	702	Example: link libcrypt statically into the binary.
541		703
542	staticperl mkperl -MIO::AIO --staticlib crypt	704	staticperl mkperl -MIO::AIO --staticlib crypt
543		705
544	# ldopts might nwo contain:	706	# ldopts might now contain:
545	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread	707	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread
546		708
547	=item any other argument	709	=back
548
549	Any other argument is interpreted as a bundle specification file, which
550	supports most long options (without extra quoting), one option per line.
551		710
552	=back	711	=back
553		712
554	=head3 EXTENDED GLOB PATTERNS	713	=head3 EXTENDED GLOB PATTERNS
555		714
…		…
589		748
590	=back	749	=back
591		750
592	=head2 F<STATICPERL> CONFIGURATION AND HOOKS	751	=head2 F<STATICPERL> CONFIGURATION AND HOOKS
593		752
594	During (each) startup, F<staticperl> tries to source the following shell	753	During (each) startup, F<staticperl> tries to source some shell files to
		754	allow you to fine-tune/override configuration settings.
		755
		756	In them you can override shell variables, or define shell functions
		757	("hooks") to be called at specific phases during installation. For
		758	example, you could define a C<postinstall> hook to install additional
		759	modules from CPAN each time you start from scratch.
		760
		761	If the env variable C<$STATICPERLRC> is set, then F<staticperl> will try
		762	to source the file named with it only. Otherwise, it tries the following
595	files in order:	763	shell files in order:
596		764
597	/etc/staticperlrc	765	/etc/staticperlrc
598	~/.staticperlrc	766	~/.staticperlrc
599	$STATICPERL/rc	767	$STATICPERL/rc
600
601	They can be used to override shell variables, or define functions to be
602	called at specific phases.
603		768
604	Note that the last file is erased during F<staticperl distclean>, so	769	Note that the last file is erased during F<staticperl distclean>, so
605	generally should not be used.	770	generally should not be used.
606		771
607	=head3 CONFIGURATION VARIABLES	772	=head3 CONFIGURATION VARIABLES
…		…
669		834
670	More commonly, you would either activate 64 bit integer support	835	More commonly, you would either activate 64 bit integer support
671	(C<-Duse64bitint>), or disable large files support (-Uuselargefiles), to	836	(C<-Duse64bitint>), or disable large files support (-Uuselargefiles), to
672	reduce filesize further.	837	reduce filesize further.
673		838
674	=item C<PERL_CPPFLAGS>, C<PERL_OPTIMIZE>, C<PERL_LDFLAGS>, C<PERL_LIBS>	839	=item C<PERL_CC>, C<PERL_CCFLAGS>, C<PERL_OPTIMIZE>, C<PERL_LDFLAGS>, C<PERL_LIBS>
675		840
676	These flags are passed to perl's F<Configure> script, and are generally	841	These flags are passed to perl's F<Configure> script, and are generally
677	optimised for small size (at the cost of performance). Since they also	842	optimised for small size (at the cost of performance). Since they also
678	contain subtle workarounds around various build issues, changing these	843	contain subtle workarounds around various build issues, changing these
679	usually requires understanding their default values - best look at the top	844	usually requires understanding their default values - best look at
680	of the F<staticperl> script for more info on these.	845	the top of the F<staticperl> script for more info on these, and use a
		846	F<~/.staticperlrc> to override them.
		847
		848	Most of the variables override (or modify) the corresponding F<Configure>
		849	variable, except C<PERL_CCFLAGS>, which gets appended.
681		850
682	=back	851	=back
683		852
684	=head4 Variables you probably I<do not want> to override	853	=head4 Variables you probably I<do not want> to override
685		854
686	=over 4	855	=over 4
		856
		857	=item C<MAKE>
		858
		859	The make command to use - default is C<make>.
687		860
688	=item C<MKBUNDLE>	861	=item C<MKBUNDLE>
689		862
690	Where F<staticperl> writes the C<mkbundle> command to	863	Where F<staticperl> writes the C<mkbundle> command to
691	(default: F<$STATICPERL/mkbundle>).	864	(default: F<$STATICPERL/mkbundle>).
…		…
953		1126
954	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn	1127	If you want to handle IRIs or IDNs (L<AnyEvent::Util> punycode and idn
955	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and	1128	functions), you also need to include C<"AnyEvent/Util/idna.pl"> and
956	C<"AnyEvent/Util/uts46data.pl">.	1129	C<"AnyEvent/Util/uts46data.pl">.
957		1130
		1131	Or you can use C<--usepacklist> and specify C<-MAnyEvent> to include
		1132	everything.
		1133
958	=item Carp	1134	=item Carp
959		1135
960	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of	1136	Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of
961	perl 5.12.2 (maybe earlier), this dependency no longer exists.	1137	perl 5.12.2 (maybe earlier), this dependency no longer exists.
962		1138
…		…
966	turn might need L<"Config_heavy.pl">. Including the latter gives you	1142	turn might need L<"Config_heavy.pl">. Including the latter gives you
967	both.	1143	both.
968		1144
969	=item Term::ReadLine::Perl	1145	=item Term::ReadLine::Perl
970		1146
971	Also needs L<Term::ReadLine::readline>.	1147	Also needs L<Term::ReadLine::readline>, or C<--usepacklist>.
972		1148
973	=item URI	1149	=item URI
974		1150
975	URI implements schemes as separate modules - the generic URL scheme is	1151	URI implements schemes as separate modules - the generic URL scheme is
976	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If	1152	implemented in L<URI::_generic>, HTTP is implemented in L<URI::http>. If
977	you need to use any of these schemes, you should include these manually.	1153	you need to use any of these schemes, you should include these manually,
		1154	or use C<--usepacklist>.
978		1155
979	=back	1156	=back
980		1157
981	=head2 RECIPES	1158	=head2 RECIPES
982		1159
…		…
1015	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"	1192	PERL_CONFIGURE="$PERL_CONFIGURE -U$sym"
1016	done	1193	done
1017	}	1194	}
1018		1195
1019	This mostly gains space when linking staticaly, as the functions will	1196	This mostly gains space when linking staticaly, as the functions will
1020	liekly not be linked in. The gain for dynamically-linked binaries is	1197	likely not be linked in. The gain for dynamically-linked binaries is
1021	smaller.	1198	smaller.
1022		1199
1023	Also, this leaves C<gethostbyname> in - not only is it actually used	1200	Also, this leaves C<gethostbyname> in - not only is it actually used
1024	often, the L<Socket> module also exposes it, so leaving it out usually	1201	often, the L<Socket> module also exposes it, so leaving it out usually
1025	gains little. Why Socket exposes a C function that is in the core already	1202	gains little. Why Socket exposes a C function that is in the core already

Diff Legend

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

Comparing App-Staticperl/staticperl.pod (file contents): Revision 1.19 by root, Fri Dec 10 15:25:24 2010 UTC vs. Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.19 by root, Fri Dec 10 15:25:24 2010 UTC vs.
Revision 1.27 by root, Tue Dec 21 19:32:34 2010 UTC