innoextract

When using innoextract, be aware of the following constraints:

• No component selection: There is no support for extracting individual components or filtering by name.
• No script execution: Included installer scripts and checks are not executed.
• Hard-coded mappings: The mapping from Inno Setup variables (like the application directory) to subdirectories is hard-coded.
• Multi-file naming: For multi-file installers, data slice/disk files must follow the standard Inno Setup naming scheme.

To compile and install innoextract, you need CMake 2.8, a C++ compiler, and development headers for Boost and liblzma.

Follow these steps to build the project:

1. Create a build directory and enter it.
2. Run CMake to generate build files.
3. Run make to compile.

To install the binaries system-wide, run make install as root.

When running cmake, you can pass -D<option>=<value> to customize the build.

Key options include:

• DEVELOPER: Set to 1 to enable debug output, fast incremental builds, and unit tests. This is recommended if you are modifying the source code.
• USE_LZMA: Controls whether liblzma is used (default ON).
• WITH_CONV: Sets the charset conversion library. Valid values: iconv, win32, or builtin (supports only Windows-1252 and UTF-16LE).
• CMAKE_BUILD_TYPE: Set to Debug for debug output.
• USE_STATIC_LIBS: Enables static linking for all libraries.

When extracting files, you can specify how innoextract should behave if multiple files attempt to write to the same path. This is controlled via the CollisionAction enum assigned to the collisions member of extract_options.

Available actions:

• OverwriteCollisions (Default)
• RenameCollisions
• RenameAllCollisions
• ErrorOnCollisions

enum CollisionAction {
	OverwriteCollisions,
	RenameCollisions,
	RenameAllCollisions,
	ErrorOnCollisions
};

If an Inno Setup installer is encrypted, you must provide a password to extract the files. You can provide the password in two ways:

1. Directly via CLI: Use the --password or -P flag.
2. From a file: Use the --password-file flag. If you use - as the filename, it will read from standard input.

Note: You cannot use both --password and --password-file at the same time.

Example (from file):

innoextract --password-file my_password.txt setup.exe

Example (from stdin):

echo "my_secret_password" | innoextract --password-file - setup.exe

You can use innoextract to inspect the metadata of an Inno Setup installer without extracting its contents. This allows you to view the setup version, supported languages, and file lists.

Key capabilities include:

• Viewing the setup data version.
• Listing supported languages.
• Retrieving GOG.com game IDs.
• Inspecting password hashes and salts (if present).
• Listing files and directories contained within the installer.

The following options control the installation location of innoextract.

| Option                      | Default   | Description |
|:----------------------------|:---------:|:----------- |
| `CMAKE_INSTALL_PREFIX`      | `/usr/local` | Where to install innoextract. |
| `CMAKE_INSTALL_BINDIR`       | `bin`       | Location for binaries (relative to prefix). |
| `CMAKE_INSTALL_DATAROOTDIR` | `share`      | Location for data files (relative to prefix). |
| `CMAKE_INSTALL_MANDIR`      | `${DATAROOTDIR}/man` | Location for man pages (relative to prefix). |

The following dependencies are required or recommended:

• Boost (1.37 or newer): Requires headers and the following libraries: iostreams, filesystem, date_time, system, and program_options. Note that boost::iostreams must be built with zlib and bzip2 support.
• liblzma (from xz-utils): Highly recommended. While you can build with -DUSE_LZMA=OFF, you will likely be unable to extract installers from newer Inno Setup versions without it.
• iconv: Optional. Can be part of the system libc (glibc/uClibc) or a separate libiconv library. Used for charset conversion.

To extract an Inno Setup installer to the current directory, use the following command:

innoextract <file>

To see all available command-line options, run:

innoextract --help

Detailed documentation is also available via the manual page:

man 1 innoextract

$ innoextract <file>
$ innoextract --help
$ man 1 innoextract