App-Staticperl
view release on metacpan or search on metacpan
done
}
This mostly gains space when linking statically, as the functions
will likely not be linked in. The gain for dynamically-linked
binaries is smaller.
Also, this leaves "gethostbyname" in - not only is it actually used
often, the Socket module also exposes it, so leaving it out usually
gains little. Why Socket exposes a C function that is in the core
already is anybody's guess.
ADDITIONAL RESOURCES
Some guy has made a repository on github
(<https://github.com/gh0stwizard/staticperl-modules>) with some modules
patched to build with staticperl.
AUTHOR
Marc Lehmann <schmorp@schmorp.de>
http://software.schmorp.de/pkg/staticperl.html
bin/staticperl view on Meta::CPAN
done
}
This mostly gains space when linking statically, as the functions will
likely not be linked in. The gain for dynamically-linked binaries is
smaller.
Also, this leaves C<gethostbyname> in - not only is it actually used
often, the L<Socket> module also exposes it, so leaving it out usually
gains little. Why Socket exposes a C function that is in the core already
is anybody's guess.
=back
=head1 ADDITIONAL RESOURCES
Some guy has made a repository on github
(L<https://github.com/gh0stwizard/staticperl-modules>) with some modules
patched to build with staticperl.
=head1 AUTHOR
staticperl.pod view on Meta::CPAN
done
}
This mostly gains space when linking statically, as the functions will
likely not be linked in. The gain for dynamically-linked binaries is
smaller.
Also, this leaves C<gethostbyname> in - not only is it actually used
often, the L<Socket> module also exposes it, so leaving it out usually
gains little. Why Socket exposes a C function that is in the core already
is anybody's guess.
=back
=head1 ADDITIONAL RESOURCES
Some guy has made a repository on github
(L<https://github.com/gh0stwizard/staticperl-modules>) with some modules
patched to build with staticperl.
=head1 AUTHOR
( run in 0.594 second using v1.01-cache-2.11-cpan-702932259ff )