You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since this package requires having the ptx crate as a path dependency, it is impossible to publish a dependent crate to crates.io because of rust-lang/rfcs#2224.
It would be good if you could specify a crate from crates.io in your build.rs instead of a path.
The text was updated successfully, but these errors were encountered:
Could you please explain a little in details your use case and where is that path dependency?
Technically, there is no such requirement coming from this crate. It should be possible to create either a binary or library crate that contains both device and host code. With this approach, there is no need to depend on any other local crates via a path. As a bonus, you can still publish device-only crates, that would not even have a dependency on ptx-builder and would be treated any other crate on crates.io.
Since this package requires having the ptx crate as a path dependency, it is impossible to publish a dependent crate to crates.io because of rust-lang/rfcs#2224.
It would be good if you could specify a crate from crates.io in your build.rs instead of a path.
The text was updated successfully, but these errors were encountered: