Files

T

build(rust): add legacy feature scaffolding

The legacy decoders (lib/legacy/zstd_v01.c .. zstd_v07.c) are next in
the Rust migration. Each of those files is a frozen snapshot of the
FSE/Huff0 entropy coders and frame logic of one historical release, so
their ports must not reuse the modern Rust entropy modules and must not
share code with each other: outputs and error codes have to stay
byte-identical to the frozen C forever. This commit installs the
build-system scaffolding so seven per-version ports can land
independently, each adding only its own module file plus a one-line
registration in rust/src/legacy/mod.rs.

Cargo grows features legacy-v01 .. legacy-v07. They are never default
features: the C build defaults differ per build system, so each build
system passes the list explicitly, derived from its own legacy
configuration:

- lib/Makefile and programs/Makefile map ZSTD_LEGACY_SUPPORT=N to the
  features for versions N..7 (0 disables legacy), mirroring the
  ZSTD_LEGACY_FILES selection in lib/libzstd.mk.
- tests/Makefile always enables all seven features because its
  ZSTDLEGACY_FILES wildcard compiles every lib/legacy/*.c regardless of
  the dispatch level.
- build/meson maps legacy_level exactly like the makefiles; build/cmake
  enables all seven whenever ZSTD_LEGACY_SUPPORT is ON because it
  always compiles all seven C files (ZSTD_LEGACY_LEVEL only selects the
  C dispatch).

Every build system also encodes the legacy selection in the Rust target
directory name (e.g. c1-d1-default-legacy5), for the same reason the
HUF mode is encoded there: a cached archive built for one configuration
must never be linked into a build expecting another. In tests/Makefile
the legacy level additionally flows into the existing HUF C-mode stamp,
so the flat C test objects (which bake -DZSTD_LEGACY_SUPPORT into the
dispatch) are rebuilt whenever the level changes. In programs/Makefile
the compress-only, decompress-only, and CLI archives keep
level-independent directories (RUST_HUF_MODE) because they are only
linked into ZSTD_LEGACY_SUPPORT=0 program variants and carry no legacy
features.

A feature whose version has not been ported yet gates nothing: the
module registration in rust/src/legacy/mod.rs is added by each port,
so enabling e.g. legacy-v05 today simply leaves that decoder in C.
This is what makes mixed C/Rust legacy levels link cleanly while the
seven ports land in any order.

Test plan:
- cd rust && cargo fmt --check && cargo clippy --all-targets
  -- -D warnings && cargo test --all-targets
- cargo clippy with --no-default-features --features
  decompression,legacy-v01 and with all seven legacy features
- make -C tests fuzzer && ./tests/fuzzer -i1 --no-big-tests
- make -C tests test-rust-lib-smoke; make -C tests test-legacy
- make -C lib libzstd.a with ZSTD_LEGACY_SUPPORT=0, 1 and default (5)
- cmake configure and meson setup (including -Dlegacy_level=1) emit the
  expected --features lists and legacy-suffixed target directories

2026-07-11 23:07:55 +02:00

cmake

build(rust): add legacy feature scaffolding

2026-07-11 23:07:55 +02:00

meson

build(rust): add legacy feature scaffolding

2026-07-11 23:07:55 +02:00

single_file_libs

fix minor artifact error in single_file_lib

2024-12-20 10:36:58 -08:00

VS2008

fix Visual Studio solutions

2024-01-29 15:24:42 -08:00

VS2010

removed fullbench-dll project from visual solutions

2024-12-20 10:37:00 -08:00

VS_scripts

add prerelease option

2025-01-15 02:16:42 +08:00

.gitignore

fix gitignore errors

2019-07-09 21:08:13 +08:00

LICENSE

Add support for --output-dir-flat

2019-10-02 11:08:20 -04:00

README.md

added back documentation/notification for VS2005 in build directory

2017-06-02 10:25:30 -07:00

README.md

Projects for various integrated development environments (IDE)

Included projects

The following projects are included with the zstd distribution:

cmake - CMake project contributed by Artyom Dymchenko
VS2005 - Visual Studio 2005 Project (this project has been moved to the contrib directory and will no longer be supported)
VS2008 - Visual Studio 2008 project
VS2010 - 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 projects then VS2010 and open zstd.sln
Visual Studio will ask about converting VS2010 project to VS2015 and you should agree.
Change Debug to Release and if you have 64-bit Windows change also Win32 to x64.
Press F7 on keyboard or select BUILD from the menu bar and choose Build 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 arguments
datagen : Synthetic and parametrable data generator, for tests
fullbench : Precisely measure speed for each zstd inner functions
fuzzer : Test tool, to check zstd integrity on target platform
libzstd : A static ZSTD library compiled to libzstd_static.lib
libzstd-dll : A dynamic ZSTD library (DLL) compiled to libzstd.dll with the import library libzstd.lib
fullbench-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 Directories that can be found in Project Properties of Visual Studio IDE in the C/C++ Property Pages on the General page.
The import library has to be added to Additional Dependencies that can be found in Project Properties in the Linker Property Pages on the Input page. If one will provide only the name libzstd.lib without a full path to the library then the directory has to be added to Linker\General\Additional Library Directories.

The compiled executable will require ZSTD DLL which is available at visual\VS2010\bin\$(Platform)_$(Configuration)\libzstd.dll.