#36 How do we deal with "plugin"s?
Closed: Won't Fix 17 days ago by decathorpe. Opened 5 years ago by ignatenkobrain.

https://crates.io/crates/afl-plugin

[lib]
name = "afl_plugin"
plugin = true
path = "lib.rs"

What are we supposed to do with that? Distribute as a normal lib or ...?


Metadata Update from @ignatenkobrain:
- Issue assigned to jistone

5 years ago

For proc_macro plugins, you don't need to do anything special. Just package foo-devel as normal and cargo will use it as a build-dependency.

But afl-plugin is a full compiler plugin, using unstable #[plugin]. That means it requires nightly rustc, and we can't support it.

Given that this is, 5 years later, still a nightly-only feature which we can't support, I'll close this ticket.

Metadata Update from @decathorpe:
- Issue close_status updated to: Won't Fix
- Issue status updated to: Closed (was: Open)

17 days ago

Login to comment on this ticket.

Metadata