Skip to content

executables: (optional) equivalent? #2433

@cfcs

Description

@cfcs

For the library stanza there's a <optional-field> called (optional) which causes the library to only be built all of the required libraries are present.

Is there a way to achieve the same for executables?

In my project I'd like to have binaries for use with afl-fuzz, but I don't want to make afl-persistent a hard dependency for all users of the project.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions