The instructions in the book are now out of date for projects generated
with this template. Since the instructions are much shorter these days,
put them in the README.
Adapt https://github.com/aya-rs/aya/commit/3d463a3 and subsequent work
to the template. This has worked very well for us in the main project,
and our users should get the same hotness.
Note that xtask is still used for running, as it is in the main project.
This matches the version used in the bpf-linker binstall job. Otherwise
we fail with:
```
= note: bpf-linker: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by bpf-linker)
bpf-linker: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by bpf-linker)
bpf-linker: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by bpf-linker)
```
Add a nightly build so we catch these earlier.
- Emacs vectors do not have "," separator.
- The .dir-locals.el list is checked against major mode names, but
lsp-mode could be a minor mode. Use the generic prog-mode instead.
.dir-locals.el is the emacs equivalent of .vim directory in the project here.
This PR adds a simple configuration to map the same rust-analyzer
configuration variable as the vim version to make use of new aya
projects seamless with emacs projects that use emacs-lsp + rust analyzer.
This patch allows the helix editor to correctly initialize the
rust-analyzer when opening a source file from {{project-name}}-ebpf.
To find the Cargo.toml the helix editor must be launched from
the {{project-name}}-ebpf directory or provide the workspace path
as follows:
hx -w <path to {{project-name}}-ebpf> [relative path in {{project-name}}-ebpf]
The patch was tested using helix version 23.10.
Add a new command to build ebpf and userspace programs without running.
```
cargo xtask build
```
Co-authored-by: Michal Rostecki <vadorovsky@protonmail.com>