The depend fuzzers (hb-depend-fuzzer and hb-depend-closure-parity) use the depend API which is only available when the depend_api build option is enabled. However, the fuzzing meson.build was unconditionally building these fuzzers for all configurations, causing CI build failures when depend_api was disabled (the default). This change: - Splits the fuzzers list into regular tests and depend_tests - Only builds depend-related fuzzers when HB_DEPEND_API is defined - Maintains existing behavior for all other fuzzers - Keeps the test execution conditional as before (lines 142-166) This fixes all CI build failures across Linux, macOS, Windows (MSVC/MinGW), and sanitizer builds. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Security Fuzzers
To build the fuzzers with libFuzzer to perform actual fuzzing, build with:
CXX=clang++ CXXFLAGS="-fsanitize=address,fuzzer-no-link" meson fuzzbuild --default-library=static -Dfuzzer_ldflags="-fsanitize=address,fuzzer"
ninja -Cfuzzbuild
Then, run the fuzzer like this:
fuzzbuild/test/fuzzing/hb-{shape,raster,vector,subset,repacker,depend}-fuzzer [-max_len=2048] [CORPUS_DIR]
Where max_len specifies the maximal length of font files to handle. The smaller the faster.
Note: The depend fuzzer requires -Ddepend_api=true meson option.
For more details consult the following locations:
Depend Closure Parity Test
The hb-depend-closure-parity test is distinct from the security fuzzers.
While security fuzzers test robustness against malformed input, the closure
parity test validates correctness by emulating the glyph closure calculation
used for subsetting with one generated from the dependency graph to avoid
implementation divergence. It should only be run on valid fonts.