Skip to content

Commit 2bbabc3

Browse files
authored
Chore/cmd order (#10)
* Extend guide on using VS Code * Format & update README * Minor reorder
1 parent d22377e commit 2bbabc3

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

Containerfile

+1-2
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
# Build stage: basic development tools
22
FROM debian:trixie-slim AS builder
33

4-
5-
WORKDIR /root/
64
RUN apt-get update
75
RUN apt install -y \
86
git \
@@ -31,6 +29,7 @@ RUN apt install -y \
3129
zlib1g-dev
3230

3331
# Clone RISC-V GCC
32+
WORKDIR /root/
3433
RUN git clone --depth=1 --branch 2024.04.12 https://github.com/riscv-collab/riscv-gnu-toolchain
3534

3635
# Build RISC-V cross-compiler

README.md

+6-5
Original file line numberDiff line numberDiff line change
@@ -149,12 +149,13 @@ TL;DR:
149149
3. (podman only) Add to your VS Code settings: `"dev.containers.dockerPath": "podman"`
150150
4. Make sure the container is running, i.e.,
151151
`podman run --name rust-rv32emc -dt rust-rv32emc` or `podman start rust-rv32emc`
152-
5. Then `Command Palette` -> `Dev Containers: Attach to Running Container...`.
153-
For first time load, VS Code will take some time to set up the remote
154-
container.
152+
5. Make sure the container is running, i.e., `podman run --name rust-rv32emc -dt rust-rv32emc` or
153+
`podman start rust-rv32emc`
154+
6. Then `Command Palette` -> `Dev Containers: Attach to Running Container...`. For first time load,
155+
VS Code will take some time to set up the remote container.
155156
156-
If it doesn't work for you and something else is also required, open an issue
157-
and I might figure it out.
157+
If it doesn't work for you and something else is also required, open an issue and I might figure it
158+
out.
158159

159160
## Using your SSH keys with the container
160161

0 commit comments

Comments
 (0)