`make all` exercises substantially more than the default zstd binary. It also builds compression-only and decompression-only archives, older contrib tools that compile program C shims directly, and the single-file amalgamations. The Rust migration had changed symbol ownership without updating every one of those feature and link boundaries. The first failure came from `fileio_asyncio`: it is always compiled, but its codec bindings unconditionally referenced both `zstd_compress` and `zstd_decompress`. A compression-only archive therefore required disabled decoder modules, and the decompression-only configuration had the symmetric problem. Gate the concrete codec imports, callback types, helpers, and exports with their Cargo features. Keep the format probe compilable without the legacy decoder predicate when decompression is disabled. Once that boundary compiled, the remaining `make all` paths exposed related integration gaps. Move the C decompression projection declarations out of the compression preprocessor block, while leaving destination callback types shared. Link the Rust CLI helpers archive into zlibWrapper, pzstd, and largeNbDicts, whose util/time/data-generator C files are now declaration shims rather than implementations. The generated single-file C sources also call Rust-owned symbols now. Build and link an appropriately featured Rust archive in their native smoke tests, and include the pool configuration shim in the decoder case. The full amalgamation combines `zstd_lazy.c` and `zstd_opt.c` into one translation unit, so guard their otherwise translation-unit-local dictionary mode enum against duplicate definition. A Rust-backed amalgamation is no longer a standalone Emscripten input. Remove the obsolete emcc/Docker path and report that limitation explicitly; restoring the WebAssembly smoke test requires a Rust WebAssembly archive and a defined cross-language amalgamation contract. Test Plan: - `cargo check --manifest-path rust/Cargo.toml --no-default-features --features compression` -- passed - `cargo check --manifest-path rust/Cargo.toml --no-default-features --features decompression` -- passed - `sh -n build/single_file_libs/build_decoder_test.sh build/single_file_libs/build_library_test.sh` -- passed - `make all` -- passed, including native single-file and seekable-format tests - `git diff --cached --check` -- passed
Projects for various integrated development environments (IDE)
Included projects
The following projects are included with the zstd distribution:
cmake- CMake project contributed by Artyom DymchenkoVS2005- Visual Studio 2005 Project (this project has been moved to the contrib directory and will no longer be supported)VS2008- Visual Studio 2008 projectVS2010- Visual Studio 2010 project (which also works well with Visual Studio 2012, 2013, 2015)VS_scripts- command line scripts prepared for Visual Studio compilation without IDE
How to compile zstd with Visual Studio
- Install Visual Studio e.g. VS 2015 Community Edition (it's free).
- Download the latest version of zstd from https://github.com/facebook/zstd/releases
- Decompress ZIP archive.
- Go to decompressed directory then to
projectsthenVS2010and openzstd.sln - Visual Studio will ask about converting VS2010 project to VS2015 and you should agree.
- Change
DebugtoReleaseand if you have 64-bit Windows change alsoWin32tox64. - Press F7 on keyboard or select
BUILDfrom the menu bar and chooseBuild Solution. - If compilation will be fine a compiled executable will be in
projects\VS2010\bin\x64\Release\zstd.exe
Projects available within zstd.sln
The Visual Studio solution file visual\VS2010\zstd.sln contains many projects that will be compiled to the
visual\VS2010\bin\$(Platform)_$(Configuration) directory. For example zstd set to x64 and
Release will be compiled to visual\VS2010\bin\x64_Release\zstd.exe. The solution file contains the
following projects:
zstd: Command Line Utility, supporting gzip-like argumentsdatagen: Synthetic and parametrable data generator, for testsfullbench: Precisely measure speed for each zstd inner functionsfuzzer: Test tool, to check zstd integrity on target platformlibzstd: A static ZSTD library compiled tolibzstd_static.liblibzstd-dll: A dynamic ZSTD library (DLL) compiled tolibzstd.dllwith the import librarylibzstd.libfullbench-dll: The fullbench program compiled with the import library; the executable requires ZSTD DLL
Using ZSTD DLL with Microsoft Visual C++ project
The header file lib\zstd.h and the import library
visual\VS2010\bin\$(Platform)_$(Configuration)\libzstd.lib are required to compile
a project using Visual C++.
- The path to header files should be added to
Additional Include Directoriesthat can be found in Project Properties of Visual Studio IDE in theC/C++Property Pages on theGeneralpage. - The import library has to be added to
Additional Dependenciesthat can be found in Project Properties in theLinkerProperty Pages on theInputpage. If one will provide only the namelibzstd.libwithout a full path to the library then the directory has to be added toLinker\General\Additional Library Directories.
The compiled executable will require ZSTD DLL which is available at
visual\VS2010\bin\$(Platform)_$(Configuration)\libzstd.dll.