Bundle dynamic executables with their library dependencies so they can be run anywhere, just like a static executable.
StaticX currently works only with Linux 64-bit dynamic executables.
The following external tools need to be installed to run StaticX:
ldd
- Part of GNU C Libraryreadelf
- Part of binutilsobjcopy
- Part of binutilspatchelf
- Packages available for Debian 8+, Fedora 14+, others
- install with
pip install patchelf-wrapper
The following additional tools must be installed to build StaticX from source:
scons
musl-libc
(optional)
StaticX is avaiable on PyPI. The wheels are built on Travis CI and include a bootloader built with musl-libc.
You can install using Pip.
StaticX is compatible with Python Python 3.5+ (pip3
):
sudo pip3 install staticx
If you have musl libc installed, you can use it to build the staticx
bootloader, resulting in smaller, better binaries. To do so, set the
BOOTLOADER_CC
environment variable to your musl-gcc
wrapper path
wehn invoking pip
or setup.py
:
sudo BOOTLOADER_CC=/usr/local/musl/bin/musl-gcc pip3 install https://github.com/JonathonReinhart/staticx/archive/master.zip
cd staticx
sudo BOOTLOADER_CC=/usr/local/musl/bin/musl-gcc pip3 install .
Basic wrapping of an executable
staticx /path/to/exe /path/to/output
StaticX will automatically discover and bundle most normal linked libraries.
However, libraries loaded by an application at runtime via dlopen()
cannot
currently be detected. These can be manually included in the application bundle
by using the -l
option (any number can be specified by repeating the -l
option).
staticx -l /path/to/fancy/library /path/to/exe /path/to/output
StaticX employs a number of tricks to run applications with only their bundled libraries to ensure compatibilitiy. Because of this, there are some caveats that apply to StaticX-bundled applications:
- The dynamic linker is instructed (via
nodeflib
) to only permit bundled libraries to be loaded. - Target NSS configuration (
/etc/nsswitch.conf
) is ignored (for GLIBC-linked applications) which means that some advanced name services (e.g. Active Directory) will not be available at runtime. For example, looking up the UID number of a domain user will not work.
StaticX sets the following environment variables for the wrapped user program:
STATICX_BUNDLE_DIR
: The absolute path of the "bundle" directory, the temporary dir where the archive has been extracted.STATICX_PROG_PATH
: The absolute path of the program being executed.
This software is released under the GPLv2, with an exception allowing the bootloader to be distributed. See LICENSE.txt for more details.