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
If I understood correctly, external crates referenced in the Cargo.toml files are still not supported, right? So there's no way at the moment to build something that depends on external crates, am I right?
The text was updated successfully, but these errors were encountered:
There's not really a way currently .... or at least not one that has feature parity with Cargo itself. I've been making efforts to facilitate automatic BUILD generation from Cargo.toml -- but I'm doubtful that there will ever be the sort of "drop a Cargo.toml here and get going" experience that you might be imagining.
The above hacky project doesn't support many usecases, one of which is anything that depends on a pkg-config dependency. That includes openssl, and half of crates.io that depends on it, so don't get too excited yet.
Still, I'm working on it!
EDIT: I don't speak for any bazel developers (or project maintainers), by the way.
A "drop and go" sort of workflow is supported with google/cargo-raze if you use the remote mode.
Toml would need to add a snippet like this:
[raze]
genmode = "Remote"
This has some deficiencies. For now, I'll close this issue as "not actionable". Feel free to reopen (or file a new issue here or @ cargo-raze) if you have any more specific issues.
If I understood correctly, external crates referenced in the Cargo.toml files are still not supported, right? So there's no way at the moment to build something that depends on external crates, am I right?
The text was updated successfully, but these errors were encountered: