mirror of
https://github.com/iNavFlight/inav.git
synced 2025-07-24 16:55:29 +03:00
Merge remote-tracking branch 'origin/master' into mosca-target-converter
This commit is contained in:
commit
2fe6f0405b
118 changed files with 3386 additions and 1173 deletions
|
@ -566,7 +566,6 @@ The log end marker is an optional Event ("E") frame of type 0xFF whose payload i
|
|||
<li> Sticks</li>
|
||||
<li> Switch_3D</li>
|
||||
<li> Switch</li>
|
||||
<li> Killswitch</li>
|
||||
<li> Failsafe</li>
|
||||
<li> Navigation</li>
|
||||
</ol>
|
||||
|
|
|
@ -1,5 +1,7 @@
|
|||
# Building with Docker
|
||||
|
||||
> **On Windows building with this method is not advised and should be used only if Windows Linux Subsystem can not be used. In all other cases all Windows users should be using Linux Subsystem (WSL) instead**
|
||||
|
||||
Building with [Docker](https://www.docker.com/) is remarkably easy: an isolated container will hold all the needed compilation tools so that they won't interfere with your system and you won't need to install and manage them by yourself. You'll only need to have Docker itself [installed](https://docs.docker.com/install/).
|
||||
|
||||
The first time that you'll run a build it will take a little more time than following executions since it will be building its base image first. Once this initial process is completed, the firmware will be always built immediately.
|
||||
|
|
|
@ -1,5 +1,7 @@
|
|||
# Building with Vagrant
|
||||
|
||||
> **On Windows building with this method is not advised and should be used only if Windows Linux Subsystem can not be used. In all other cases all Windows users should be using Linux Subsystem (WSL) instead**
|
||||
|
||||
Setting up build environment with Vagrant is remarkably simple, but you still need to have some basic knowlage of your OS.
|
||||
|
||||
## Installing Vagrant
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# Building in Windows 10 with Linux subsystem [Recommended]
|
||||
# Building in Windows 10/11 with Linux subsystem (WSL) [Recommended]
|
||||
|
||||
Linux subsystem for Windows 10 is probably the simplest way of building INAV under Windows 10.
|
||||
Linux subsystem for Windows (WSL) 10/11 is probably the simplest way of building INAV under Windows.
|
||||
|
||||
## Setting up the environment
|
||||
|
||||
|
@ -9,7 +9,6 @@ run `windows features`
|
|||
enable `windows subsytem for linux`
|
||||
reboot
|
||||
|
||||
|
||||
Install Ubuntu:
|
||||
1. Go to Microsoft store https://www.microsoft.com/en-gb/store/b/home
|
||||
1. Search and install most recent Ubuntu LTS version
|
||||
|
@ -56,12 +55,12 @@ You can fix this with by remounting the drive using the following commands
|
|||
1. `sudo umount /mnt/c`
|
||||
2. `sudo mount -t drvfs C: /mnt/c -o metadata`
|
||||
|
||||
## Building (example):
|
||||
## Building with Make (example):
|
||||
|
||||
For detailed build instrusctions see [Building in Linux](Building%20in%20Linux.md)
|
||||
For detailed build instructions see [Building in Linux](Building%20in%20Linux.md)
|
||||
|
||||
Launch Ubuntu:
|
||||
Click Windows Start button then scroll and lauch "Ubuntu"
|
||||
Click Windows Start button then scroll and launch "Ubuntu"
|
||||
|
||||
Building from Ubuntu command line
|
||||
|
||||
|
@ -80,6 +79,39 @@ cd build
|
|||
make MATEKF722
|
||||
```
|
||||
|
||||
## Building with Ninja (example):
|
||||
|
||||
[Ninja](https://ninja-build.org/) is a popular cross-platform tool. It is both lightweight and executes parallel builds by default. It is advantageous to use this over the old _make_ method. There are detailed instructions for building with Ninja in [Building in Linux](Building%20in%20Linux.md#building-with-ninja).
|
||||
|
||||
Launch Ubuntu:
|
||||
Click Windows Start button. Then scroll and launch **Ubuntu**.
|
||||
|
||||
> [!TIP]
|
||||
> Before using Ninja, you will need to install it. From the Ubuntu command prompt type `sudo apt-get install ninja-build -y` and press enter.
|
||||
|
||||
Building from the command line:
|
||||
|
||||
First, change to the INAV directory with
|
||||
```cd /mnt/c/inav```
|
||||
|
||||
Before building, you will need to prepare the build environment. You only need to do this once, unless you reinstall WSL or cmake.
|
||||
|
||||
```
|
||||
mkdir build
|
||||
cd build
|
||||
cmake -GNinja ..
|
||||
```
|
||||
|
||||
From then on, you can build your target by calling the following from inside the build directory.
|
||||
```
|
||||
ninja MATEKF722
|
||||
```
|
||||
|
||||
If you want to build multiple targets. You can use:
|
||||
```
|
||||
ninja MATEKF722 MATEKF405SE SPEEDYBEEF405
|
||||
```
|
||||
|
||||
## Updating the documents
|
||||
```
|
||||
cd /mnt/c/inav
|
||||
|
|
|
@ -1,4 +1,7 @@
|
|||
# Building in Windows with MSYS2
|
||||
|
||||
> **Building with this method is not advised and should be used only if Windows Linux Subsystem can not be used. In all other cases all Windows users should be using Linux Subsystem (WSL) instead**
|
||||
|
||||
- This environment does not require installing WSL, which may not be available or would get in the way of other virtualization and/or anti-cheat software
|
||||
- It is also much faster to install and get set up because of its small size(~3.65 GB total after building hex file as of 6.0.0)
|
||||
## Setting up the environment
|
||||
|
|
|
@ -1,4 +1,8 @@
|
|||
# Building in windows light [Deprecated]
|
||||
|
||||
> **Building with this method is deprecated and not advised. All Windows users should be using
|
||||
Linux Subsystem (WSL) instead**
|
||||
|
||||
no cygwin and no path changes
|
||||
|
||||
## Install Git for windows
|
Loading…
Add table
Add a link
Reference in a new issue