cargo-gccrs
cargo-gccrs copied to clipboard
Gaining support for cargo via rustc-wrapper
``` error: output of --print=split-debuginfo missing when learning about target-specific information from rustc command was: `gccrs-driver rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type...
Since https://github.com/Rust-GCC/gccrs/pull/788 was merged, we can now set the crate name in gccrs via the cargo wrapper
In order to avoid always relying on `cargo install --path .` to test your changes, let's add some instructions regarding PATH manipulation and whatnot to enable faster feedback.
It's currently really annoying to add new arguments to give to our `gccrs` invocation. We should think about having an `Argument` trait which could be converted from a rustc arg,...
We now support the `--edition` argument and should use it in the cargo wrapper
Since --cfg support is now merged in gccrs, we should make use of it in the cargo wrapper
IIUC most of the `Options` are common to all `gccrs` invocations. So ```bash rustc --crate-type=dyn --crate-type=bin src/.rs --other-flag-1 --other-flag-2 ``` becomes ```bash gccrs src/.rs --converted-other-flag-1 --converted-other-flag-2 # bin gccrs -shared...
This is something I think you should consider doing when you are finishing up with google summer of code. I think being able to rely on bors will be nice...
I think this should get split up in multiple PRs in order to better the review process. This issue shall become the tracking issue for the subtasks of the final...