You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/developer_guide/tutorials/build_system/build_program_using_sdk.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@ This page will guide you through building a very simple application for FunKey u
2
2
3
3
FunKey is an embedded Linux device with an ARM processor at its core. Programs made for other computers will not work on FunKey, and developing programs on the FunKey itself is rather impractical. Instead, development for embedded devices like FunKey almost always uses a method known as cross compilation: building software on one platform (such as a desktop computer) to be used on another (like FunKey).
4
4
5
-
The FunKey-SDK contains a cross-compilation environment based on GCC, including the compiler toolchain and the libraries available on the FunKey.
5
+
The FunKeySDK contains a cross-compilation environment based on GCC, including the compiler toolchain and the libraries available on the FunKey.
6
6
7
7
Before we can begin, setup a Linux-based compilation environment as shown on [this page][1].
8
8
9
-
## Installing the FunKey-SDK
9
+
## Installing the FunKeySDK
10
10
11
-
The FunKey-SDK is included in releases of the FunKey-OS, starting from version 2.0.0, and can be found on [GitHub][2]. Alternatively, you can [compile the SDK yourself][3].
11
+
The FunKey-SDK is included in releases of the FunKeyOS, starting from version 2.0.0, and can be found on [GitHub][2]. Alternatively, you can [compile the SDK yourself][3].
12
12
13
13
Unpack the SDK's .tar.gz file somewhere on your build system. Before you can use the SDK you must first run the **relocate-sdk.sh** script. This will update all references paths in the SDK to its current location. If you decide to move the SDK to another directory at a later point, don't forget to re-run the script.
Copy file name to clipboardExpand all lines: docs/developer_guide/tutorials/build_system/compilation_environments.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ corresponding sources and the compilation by-products tend to be
4
4
rather large, such that an available disk space of at least 12GB is
5
5
required during the build.
6
6
7
-
And even if the resulting FunKey-OS boots in less than 5s, it still
7
+
And even if the resulting FunKeyOS boots in less than 5s, it still
8
8
requires a fair amount of time to compile: please account for
9
9
1/2 hour on a modern multi-core CPU with SSD drives and a decent
10
10
Internet bandwidth.
11
11
12
-
The FunKey-OS is meant to be built on a native Ubuntu or Debian Linux
12
+
The FunKeyOS is meant to be built on a native Ubuntu or Debian Linux
13
13
host machine (Ubuntu 20.04 LTS in our case, but this should also work
14
14
with other versions, too). And with only a few changes to the
15
15
prerequisites, it can certainly be adapted to build on other common
@@ -138,7 +138,7 @@ With `<versionNumber>` set to `2` to use WSL2. You can use the same command with
138
138
139
139
Your Ubuntu installation is now ready to be used. Starting Ubuntu from the Start Menu will open a terminal with a Bash prompt. Everything you type here will be executed in Ubuntu. You can run and install applications within Ubuntu as you would on a complete installation or virtual machine.
140
140
141
-
Follow the instructions in the **Build on a Physical/Virtual Machine** section to install the requirements needed to build FunKey-OS.
141
+
Follow the instructions in the **Build on a Physical/Virtual Machine** section to install the requirements needed to build FunKeyOS.
142
142
143
143
You can access the Windows filesystem via `/mnt`; the C: drive is mounted as `/mnt/c`. From Windows you can access the Linux filesystem via the special path `\\wsl$`. Note that you can only access the files there when Ubuntu is running on WSL2.
0 commit comments