Build options

The library is highly customizable; here's a list of the available build options:

Build Option	Description	Changes the Public API
BIT7Z_7ZIP_VERSION	The version of 7-zip to be used by bit7z (default: 23.01). Note: if BIT7Z_CUSTOM_7ZIP_PATH is specified, this option is not available.
BIT7Z_AUTO_FORMAT	Enables the automatic format detection of input archives (default: OFF).	☑️
BIT7Z_BUILD_TESTS	Enables building the testing executables (default: OFF).
BIT7Z_BUILD_DOCS	Enables building the Doxygen documentation (default: OFF).
BIT7Z_CUSTOM_7ZIP_PATH	A custom path to the 7-zip source code (default: "").
BIT7Z_DISABLE_USE_STD_FILESYSTEM	Disable using the standard filesystem library and always use ghc::filesystem (default: OFF).	☑️
BIT7Z_DISABLE_ZIP_ASCII_PWD_CHECK	Disables checking if passwords are ASCII when compressing using the Zip format (default: OFF).
BIT7Z_ENABLE_SANITIZERS	Enables compiler's sanitizers (default: OFF).
BIT7Z_GENERATE_PIC	Enables generating Position Independent Code (default: OFF).
BIT7Z_REGEX_MATCHING	Enables the support for extracting files matching regular expressions (default: OFF).	☑️
BIT7Z_USE_NATIVE_STRING	Enables using the OS native string type (i.e., std::wstring on Windows, std::string elsewhere; default: OFF).	☑️
BIT7Z_USE_STD_BYTE	Enables using a type-safe byte type (like C++17's std::byte) for buffers (default: OFF).	☑️
BIT7Z_VS_LIBNAME_OUTDIR_STYLE	Force using Visual Studio output library name and directory structure convention when using other CMake generators than Visual Studio ones (default: OFF).

Windows-only options

Build Option	Description
BIT7Z_AUTO_PREFIX_LONG_PATHS	Enables or disables automatically prepending paths with the Windows long path prefix, allowing to handle archives and files with long paths (default: OFF).
BIT7Z_PATH_SANITIZATION	Enables or disables path sanitization when extracting archives containing files with invalid Windows filenames (default: OFF).
BIT7Z_USE_SYSTEM_CODEPAGE	Enables or disables using the default Windows codepage for string conversions (default: OFF).

MSVC-only options

Build Option	Description
BIT7Z_ANALYZE_CODE	Enable or disable MSVC's code analysis (default: OFF).
BIT7Z_STATIC_RUNTIME	Enable or disable using MSVC's /MT flag (default: OFF).

Unix-only options

Build Option	Description
BIT7Z_USE_LEGACY_IUNKNOWN	Enable or disable building bit7z using the legacy version of IUnknown (default: OFF). This option is available only when compiling for 7-zip 23.01+, and must be used if you compile the 7-zip's DLL with the flag Z7_USE_VIRTUAL_DESTRUCTOR_IN_IUNKNOWN.

Clang-only options

Build Option	Description
BIT7Z_LINK_LIBCPP	Enable or disable linking to libc++ instead of libstdc++ (default: OFF).

Test-only options

Build Option	Description
BIT7Z_TESTS_FILESYSTEM	Enables testing any class that needs to read/write to the filesystem (default: ON).
BIT7Z_TESTS_USE_SYSTEM_7ZIP	Enables using system's 7-zip shared library when executing tests (default: ON).

📌 7-zip Version

While configuring bit7z via CMake, it automatically downloads the latest version of 7-zip currently supported by the library.

Optionally, you can specify a different version of 7-zip via the CMake option BIT7Z_7ZIP_VERSION (e.g., -DBIT7Z_7ZIP_VERSION="22.01").

Alternatively, you can specify a custom path containing the 7-zip source code via the option BIT7Z_CUSTOM_7ZIP_PATH.

Please note that, in general, it is best to use the same version of 7-zip of the shared libraries that you will use at runtime.

Using 7-zip v23.01 on Linux and macOS

By default, bit7z is compatible with the 7z.so from 7-zip v23.01 and later.

If you plan to use the 7z.so from p7zip or 7-zip v22.01 and earlier instead, you have two ways to make bit7z compatible:

• Configure bit7z with the CMake option -DBIT7Z_USE_LEGACY_IUNKNOWN=ON; or
• Configure bit7z for 7-zip v22.01 (i.e., -DBIT7Z_7ZIP_VERSION="22.01").

On Linux and macOS, 7-zip v23.01 introduced breaking changes to the IUnknown interface. As a result, if you build bit7z for such a version of 7-zip (the default), it will not support using the shared libraries from previous versions of 7-zip (or from p7zip). Conversely, bit7z made for earlier versions of 7-zip or for p7zip is incompatible with the shared libraries from 7-zip v23.01 and later.

You can build the shared libraries of 7-zip v23.01 in a backward-compatible mode by defining the macro Z7_USE_VIRTUAL_DESTRUCTOR_IN_IUNKNOWN. If this is your case, you'll need to enable the BIT7Z_USE_LEGACY_IUNKNOWN to make bit7z work (in this case, bit7z will be compatible also with previous versions of 7-zip/p7zip).

🗺️ String Encoding

By default, bit7z follows the UTF-8 Everywhere Manifesto to simplify the use of the library within cross-platform projects. In short, this means that:

• The default path string type is std::string.
• Input std::strings are considered as UTF-8 encoded; output std::strings are UTF-8 encoded.

On POSIX systems, std::strings are usually already UTF-8 encoded, and no configuration is needed.

The situation is a bit more complex on Windows since, by default, Windows treats std::strings as encoded using the system code page, which may not necessarily be UTF-8, like, for example, Windows-1252.

If your program deals exclusively with ASCII-only strings, you should be fine with the default bit7z settings (as ASCII characters are also UTF-8).

However, if you need to handle non-ASCII/Unicode characters, as it is likely, you have the following options:

• Enforcing using the UTF-8 code page for your whole application, as explained by Microsoft here:

  • Recommended, but supported only since Windows 10 1903 and later.

• Manually ensuring the encoding of the std::strings passed to bit7z:

  • You can use some string encoding library or C++11's UTF-8 string literals for input strings.
  • User-input strings (e.g., the password of an archive) can be handled as explained here; in short: read the input as an UTF-16 wide string (e.g., via ReadConsoleW), and convert it to UTF-8 (bit7z provides a utility function for this, bit7z::to_tstring).
  • You can correctly print the UTF-8 output strings from bit7z (e.g., the path/name metadata of a file in an archive) to the console by calling SetConsoleOutputCP(CP_UTF8) before.

• Configuring bit7z to use UTF-16 encoded wide strings (i.e., std::wstring) by enabling the BIT7Z_USE_NATIVE_STRING option via CMake.

  • If your program is Windows-only, or you already use wide strings on Windows, this might be the best choice since it will avoid any internal string conversions (7-zip always uses wide strings).

  • This option makes developing cross-platform applications slightly inconvenient since you'll still have to use std::string on POSIX systems.

  • The library provides a type alias bit7z::tstring and a macro function BIT7Z_STRING for defining wide string variables and literals on Windows and narrow ones on other platforms.

  • You must programmatically set the standard input and output encoding to UTF-16 to correctly read and print Unicode characters:

    #include <fcntl.h> //for _O_U16TEXT
    #include <io.h>  //for _setmode
    
    _setmode(_fileno(stdout), _O_U16TEXT); // setting the stdout encoding to UTF16
    _setmode(_fileno(stdin), _O_U16TEXT); // setting the stdin encoding to UTF16

• Configuring bit7z to use the system code page encoding for std::string by enabling the BIT7Z_USE_SYSTEM_CODEPAGE option via CMake.

  • Not recommended: using this option, your program will be limited in the set of characters it can pass to and read from bit7z.