# Building FriiDump

## Windows

The maintained direct build path is:

```powershell
.\build_msvc32.cmd
```

It calls `.vscode\msvc32.cmd`, which currently locates the Visual Studio 2019
Build Tools 32-bit environment, then invokes:

```text
cl @msvc32_friidump.rsp
```

The build script runs `friidump.exe --help` after compilation and packages a
local result ZIP. These generated files are ignored by Git.

## Linux / Unix

```bash
cmake -S . -B build -DBUILD_STATIC_BINARY=ON
cmake --build build
./build/src/friidump --help
```

The standalone repository candidate was tested with GCC 14.2 and CMake. The
build succeeded. The inherited `libfriidump/rs.c` shift-count warning remains
open and should be corrected only as a separately reviewed source change.

## External runtime requirements

Dumping requires operating-system access to the selected optical drive.
Privileges and device permissions vary by platform. Avoid broadly running
unrelated tools with elevated privileges; grant only the access required for
the optical device.
