b63a433ba1
This was changed some time ago (https://google.github.io/oss-fuzz/getting-started/new-project-guide/) but the build didn't fail as there is a fallback mechanism. The main advantage of the new approach is that for libFuzzer this produces more performant binaries (as `$LIB_FUZZING_ENGINE` expands into `-fsanitize=fuzzer`, which links libFuzzer from the compiler-rt, allowing better optimization tricks). I'm also experimenting with dataflow (https://github.com/google/oss-fuzz/issues/1632) on your project, and the dataflow config doesn't have a fallback (as it's a new configuration), therefore I'm proposing a change to migrate from `-lFuzzingEngine` to `$LIB_FUZZING_ENGINE`. |
||
|---|---|---|
| .. | ||
| conformance | ||
| fuzzers | ||
| nonregression | ||
| performance | ||
| profiling | ||
| unit | ||
| CMakeLists.txt | ||
| compare_dump_files.c | ||
| compare_images.c | ||
| compare_raw_files.c | ||
| include_openjpeg.c | ||
| j2k_random_tile_access.c | ||
| pdf2jp2.c | ||
| ppm2rgb3.c | ||
| test_decode_area.c | ||
| test_tile_decoder.c | ||
| test_tile_encoder.c | ||