Closed addisoncrump closed 1 year ago
I also added details in the README about CUSTOM_LIBFUZZER_PATH as it seemed relevant.
Can a release be cut for this? We would like to publish a downstream crate that depends on this but cannot depend on the git revision.
Published 0.4.7
Thank you!
We are implementing https://github.com/AFLplusplus/LibAFL/pull/981, but don't want to make too much impact on the downstream users of libfuzzer-sys. As a compromise, this PR adds a default feature,
link
, which, when enabled, links to the libfuzzer runtime or the CUSTOM_LIBFUZZER_RUNTIME. When not enabled, it does not link to the fuzzer runtime.This allows us to link to a custom runtime in our own dependency while reusing the infrastructure already provided by libfuzzer-sys (namely, fuzz_target and custom_mutator). See an example of this use case here: https://github.com/AFLplusplus/LibAFL/blob/libfuzzer/libafl_libfuzzer/build.rs https://github.com/AFLplusplus/LibAFL/blob/libfuzzer/libafl_libfuzzer/Cargo.toml#L17