Skip to content

cargo-fuzz workspace support seems to be lacking? #430

Description

@LebedevRI

Hi!

If anything this is a request for better docs.

Roughly, i have a top-level workspace, that contains a fine-grained set of members.
I would like to have the same pattern for fuzz, but as far as i can tell,
the fuzz directory must be a single package, in the sense that

  1. it can't be a workspace that forces all of it's members to be fuzz-packages
  2. If i add each separate fuzz package as a member of top-level workspace, then i have to build/run each one of them manually, specifying --fuzz-dir .
  3. Since there is no way to have conditional workspace members, i'm not sure if it is possible to exclude fuzz packages from normal build

Are my observations correct? It would be nice if there could be better support for workspaces...

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions