Skip to content

Commit 78479de

Browse files
committed
Update build guide to use the Toltec toolchain
1 parent 0d94c7f commit 78479de

2 files changed

Lines changed: 24 additions & 36 deletions

File tree

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
[VNC](https://en.wikipedia.org/wiki/Virtual_Network_Computing) client for the [reMarkable tablet](https://remarkable.com) allowing you to use the device as a second screen.\
88
(Previously called _rmvncclient_.)
99

10-
<img alt="Illustration of a reMarkable table connected to a computer, showing half of a terminal window through its E-Ink screen" src="media/setup.gif" width="700">
10+
<img alt="Illustration of a reMarkable tablet connected to a computer, showing half of a terminal window through its E-Ink screen" src="media/setup.gif" width="700">
1111

1212
## Disclaimer
1313

@@ -33,7 +33,7 @@ After installing Toltec, simply run `opkg install vnsee` and you should be all s
3333
To remove VNSee, run `opkg remove vnsee`.
3434

3535
You can also install this program manually.
36-
Download the latest build from the [releases page](https://github.com/matteodelabre/vnsee/releases) (or build the software yourself by following the [build guide](docs/build.md)), then copy the `vnsee` and `vnsee-gui` executables to the tablet [using SSH](https://remarkablewiki.com/tech/ssh).
36+
Download the latest build from the [releases page](https://github.com/matteodelabre/vnsee/releases) (or build the binary yourself by following the [build guide](docs/build.md)), then copy the `vnsee` and `vnsee-gui` executables to the tablet [using SSH](https://remarkablewiki.com/tech/ssh).
3737
If you’re using a reMarkable 2, you’ll need to setup the [remarkable2-framebuffer](https://github.com/ddvk/remarkable2-framebuffer) before proceeding.
3838
To run `vnsee-gui`, you’ll also need to install [simple](https://rmkit.dev/apps/sas) and, optionally, [nmap](https://nmap.org/book/install.html).
3939

docs/build.md

Lines changed: 22 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,56 +1,44 @@
11
# Build guide
22

3-
**This build guide assumes you’re using a Linux system.**
3+
_This build guide uses the [Toltec Docker toolchain](https://github.com/toltec-dev/toolchain), which requires a working Docker install._
44

5-
Download the [reMarkable toolchain](https://web.archive.org/web/20201129102245/https://remarkable.engineering/oecore-x86_64-cortexa9hf-neon-toolchain-zero-gravitas-1.8-23.9.2019.sh), install it and source it.
6-
7-
```sh
8-
curl https://web.archive.org/web/20201129102245/https://remarkable.engineering/oecore-x86_64-cortexa9hf-neon-toolchain-zero-gravitas-1.8-23.9.2019.sh -o install-toolchain.sh
9-
chmod u+x install-toolchain.sh
10-
./install-toolchain.sh
11-
source /usr/local/oecore-x86_64/environment-setup-cortexa9hf-neon-oe-linux-gnueabi
12-
```
13-
14-
Download the `OEToolchainConfig.cmake` file that is missing from the toolchain and install it in `/sysroots/x86_64-oesdk-linux/usr/share/cmake` directory of the toolchain.
15-
16-
```sh
17-
curl https://raw.githubusercontent.com/openembedded/openembedded-core/master/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake -o OEToolchainConfig.cmake
18-
sudo mkdir -p /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/share/cmake
19-
sudo mv OEToolchainConfig.cmake /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/share/cmake
20-
```
21-
22-
Clone this repository with its dependencies and change directory into it.
5+
Start by cloning this repository with its dependencies, then change directory into it.
236

247
```sh
258
git clone --recursive https://github.com/matteodelabre/vnsee
269
cd vnsee
2710
```
2811

29-
Create a directory for build artifacts.
12+
Use the following command to spin up a container and run a build in the `build/Release` subdirectory.
3013

3114
```sh
32-
mkdir -p build/Release
33-
cd build/Release
15+
docker container run -it --rm \
16+
--mount type=bind,src="$(realpath .)",dst=/src \
17+
ghcr.io/toltec-dev/base:v2.1 \
18+
bash -c "cmake \
19+
-DCMAKE_TOOLCHAIN_FILE=/usr/share/cmake/arm-linux-gnueabihf.cmake \
20+
-DCMAKE_BUILD_TYPE=Release \
21+
-S /src -B /src/build/Release \
22+
&& cmake --build /src/build/Release"
3423
```
3524

36-
Run CMake configuration.
25+
This command will first run the CMake configuration command, which will automatically locate the appropriate compiler and determine flags.
26+
This step should end with the following lines:
3727

38-
```sh
39-
cmake ../.. -DCMAKE_BUILD_TYPE=Release
4028
```
41-
42-
The output should not contain any error and should end with those lines:
43-
44-
```txt
29+
...
4530
-- Configuring done
4631
-- Generating done
47-
-- Build files have been written to: …/vnsee/build/Release
32+
-- Build files have been written to: /src/build/Release
4833
```
4934

50-
Run build.
35+
Right after the configuration step has finished, the command will start the actual build.
36+
You should see CMake’s colorful output logging the files it compiles, with lines similar to this one:
5137

52-
```sh
53-
make
38+
```
39+
...
40+
[ 16%] Building CXX object CMakeFiles/vnsee.dir/src/main.cpp.o
41+
...
5442
```
5543

56-
You now have a `vnsee` executable ready to be executed on your reMarkable!
44+
When this step completes, you should have a working `vnsee` executable in the `build/Release` subdirectory, ready to be executed on your reMarkable!

0 commit comments

Comments
 (0)