This allows the usage of an already installed llvm-profdata binary.
If the user does not provide an llvm-path cargo-fuzz will try to use the one installed through rustup component add llvm-tools-preview.
If that fails the same instructions to install llvm-tools-preview as before as shown.
The name of the option and the fact that a user should set it to the bin folder of an LLVM installation (not to the binary itself) follows the same convention as grcov.
Closes #353
Let me know if something needs to change, or if there's a reason why we should avoid allowing the user to set its own llvm-profdata
This allows the usage of an already installed
llvm-profdatabinary. If the user does not provide anllvm-pathcargo-fuzz will try to use the one installed throughrustup component add llvm-tools-preview. If that fails the same instructions to installllvm-tools-previewas before as shown.The name of the option and the fact that a user should set it to the bin folder of an LLVM installation (not to the binary itself) follows the same convention as
grcov.Closes #353
Let me know if something needs to change, or if there's a reason why we should avoid allowing the user to set its own
llvm-profdata