CohenArthur
CohenArthur
`> gccrs -fdiagnostics-format=json src/main.rs &| jq .` ```json [ { "kind": "error", "column-origin": 1, "children": [], "locations": [ { "caret": { "byte-column": 1, "display-column": 1, "line": 1, "file": "src/main.rs", "column":...
This would also probably close #29
[Linked `gccrs` issue](https://github.com/Rust-GCC/gccrs/issues/490)
This ties a bit into #20 I think it's important that we handle stuff such as `RUSTFLAGS` so that users can ideally use `cargo build` and `cargo gccrs build` without...
I think having some sort of 'callback' would also be useful in order to compile static libraries. Since we need to spawn a second command to archive the object files...
yeah, I believe the best thing would be to go with a separate .exp file because we might eventually want to tweak it as you said Thomas. so I would...
This issue is related to this comment: https://github.com/Rust-GCC/gccrs/pull/3058#discussion_r1651013422 (might be invalid - I'll investigate it this week)
@badumbatish I thought the issue was quite easy to fix so I was writing a guide for you, but it turns out it's deeper than I thought because we're not...
This is also an issue for the `ffi` module in `core` 1.49
@antoniospg I think that's the correct way to go about it :) feel free to submit a PR/draft PR and ping me on it so I can have a look...