-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always build eBPF; remove xtask #132
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can fix the current failure by putting
components = ["rust-src"]
into {{project-name}}-ebpf/rust-toolchain.toml
nvm, we are installing rust-src in the Github workflow yaml, so that's not the issue. Something more fishy is going in with clippy. I still think that putting it into |
As always, cargo-in-cargo issue. Should be fixed now.
Done. |
Use `cargo build`, `cargo check`, etc. as normal. Run your program with: | ||
|
||
```shell | ||
cargo run --release --config 'target."cfg(all())".runner="sudo -E"' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why don't we set this in config.toml? It's what I do for my projects
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like that as a default. It should be opt in to invoke sudo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From one hand I find this command quite annoying - the syntax looks really weird.
From the other hand, I do agree that calling sudo
should be opt in. Maybe someone wants to use doas
or something else.
Only if cargo supported something env var like CARGO_RUNNER
, so users could just do export CARGO_RUNNER="sudo -E"
, which looks less wild.
At the end I think I have a slight preference towards not defaulting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there are still concerns with this I'll address them in a follow-up.
984e537
to
a5bf57d
Compare
90bd7fe
to
270aa0f
Compare
No description provided.