Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide crate directory conventions and repository organization #34

Closed
frewsxcv opened this issue Mar 9, 2017 · 0 comments · Fixed by #102
Closed

Decide crate directory conventions and repository organization #34

frewsxcv opened this issue Mar 9, 2017 · 0 comments · Fixed by #102

Comments

@frewsxcv
Copy link
Member

frewsxcv commented Mar 9, 2017

What should the layout of this repository be?

So far, it's been:

/<published crate name>/{Cargo.toml, <targets>.rs}

With the exception of the crypto-hashes directory which is just a collection of different crates. What if a crate isn't published?
@frewsxcv frewsxcv changed the title Decide directory/crate convention Decide crate directory conventions and repository organization Mar 9, 2017
@PaulGrandperrin PaulGrandperrin mentioned this issue Apr 21, 2018
Merged
bors bot added a commit that referenced this issue Apr 25, 2018
@bors @PaulGrandperrin
Merge #102
0fc9e09 
102: Generalize the project to other fuzzers: AFL and Honggfuzz r=frewsxcv a=PaulGrandperrin

This is far from perfect (all targets are compiled at once) but it works and it's easy to work with (look at and add targets).

All the targets have been ported with only 1 or 2 exceptions that were broken and not easily fixable.
All seeds have been moved over too.
I added a few more targets like `url` and `proc_macro2`.

closes #100 
closes #98 
closes #66 I guess
closes #34 not relevant anymore
closes #73 

Co-authored-by: Paul Grandperrin <[email protected]>
@bors bors bot closed this as completed in #102 Apr 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Generalize the project to other fuzzers: AFL and Honggfuzz PaulGrandperrin/targets
1 participant
@frewsxcv