-
-
Notifications
You must be signed in to change notification settings - Fork 225
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rely on mkdoxy to generate documentation site
- Loading branch information
Showing
13 changed files
with
340 additions
and
2,842 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,283 @@ | ||
# Development guide | ||
|
||
## Getting the source code | ||
|
||
First check out the source code. | ||
The following commands will fetch the latest code. | ||
|
||
```sh | ||
# For this document we will assume you are inside a folder for development. | ||
# We will refer to that as `dev`. | ||
# | ||
# I usually have a folder called `dev` in my user folder and inside a subfolder | ||
# for each software project, here that would be `/home/user/dev/qfield`. | ||
# You are free to choose yours. | ||
|
||
git clone git@github.com:opengisch/QField.git | ||
# Alternatively you can use the following URL in case you have not set up SSH keys for github | ||
# https://github.com/opengisch/QField.git | ||
``` | ||
|
||
## Linux | ||
|
||
You need to have cmake installed. | ||
|
||
You have two options to build QField. Using system packages which will | ||
reuse packages installed from your package manager. Or using vcpkg which | ||
will build all the packages from source. | ||
|
||
### Using system packages | ||
|
||
This will use your system packages. | ||
Make sure you have installed the appropriate `-dev` or `-devel` packages | ||
using your system package manager. | ||
This is much faster to build than the using vcpkg and often the preferred | ||
development method. | ||
|
||
Installing all [QGIS development packages](https://github.com/qgis/QGIS/blob/master/INSTALL.md#33-install-build-dependencies) | ||
is a good start. The next step is to install QField specific dependencies, | ||
here is a non-exhaustive list of them on Ubuntu 24.10. | ||
|
||
``` | ||
sudo apt install build-essential cmake qt6-sensors-dev qt6-declarative-dev qt6-positioning-dev qt6-svg-dev qt6-webview-dev qt6-multimedia-dev qt6-connectivity-dev libzxing-dev libqt6charts6 qml6-module-qtcharts qml6-module-qtlocation qml6-module-qtwebengine qml6-module-qt-labs-settings qml6-module-qtquick-controls qml6-module-qtquick-layouts qml6-module-qtwebview qml6-module-qtmultimedia qml6-module-qtquick-shapes qml6-module-qtsensors qml6-module-qtquick-particles zipcmp zipmerge ziptool | ||
``` | ||
|
||
### Configure | ||
```sh | ||
cmake -S QField -B build | ||
``` | ||
|
||
If you use a locally built QGIS installed to a different | ||
location, use `-DQGIS_ROOT=` to specify this path. | ||
|
||
### Using vcpkg | ||
|
||
This will build the complete dependency chain from scratch. | ||
|
||
```sh | ||
cmake -S QField -B build -DWITH_VCPKG=ON | ||
``` | ||
|
||
Since this is now building a lot, grab yourself a cold or hot drink | ||
and take a good break. It could well take several hours. | ||
|
||
### Build | ||
|
||
Now build the application. | ||
|
||
```sh | ||
cmake --build build | ||
``` | ||
|
||
### Tests | ||
|
||
To build with tests, you can specify `-DENABLE_TESTS=ON`. | ||
To run the tests, run `ctest` in the build folder. | ||
|
||
The testing framework `Catch2` has minimal version 3, so you might need to install it separately and pass it with `-DCatch2_ROOT=${HOME}/vcpkg/packages/catch2_x64-linux`. | ||
|
||
## Macos | ||
|
||
You need to have cmake and Xcode installed. | ||
|
||
The following line will configure the build. | ||
|
||
```sh | ||
# We call this from the `dev` folder again | ||
cmake -S QField -B build -GXcode -Tbuildsystem=1 -DWITH_VCPKG=ON | ||
``` | ||
|
||
Please note that this will download and build the complete dependency | ||
chain of QField. If you ever wanted to read a good book, you will have | ||
a couple of hours to get started. | ||
|
||
```sh | ||
cmake --build build | ||
``` | ||
|
||
## Windows | ||
|
||
You need to have the following tools available to build | ||
|
||
- cmake | ||
- Visual Studio | ||
|
||
### Configure | ||
|
||
QField on Windows is always built using vcpkg. | ||
A couple of specific variables should be specified. | ||
The `x-buildtrees-root` flag needs to point to a short path | ||
in order to avoid running into [issues with long paths](https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#enable-long-paths-in-windows-10-version-1607-and-later). | ||
|
||
|
||
```sh | ||
cmake -S QField -B build \ | ||
-D VCPKG_TARGET_TRIPLET=x64-windows-static \ | ||
-D CMAKE_MSVC_RUNTIME_LIBRARY="MultiThreaded$<$<CONFIG:Debug>:Debug>" \ | ||
-D PKG_CONFIG_EXECUTABLE=build/vcpkg_installed/x64-windows-static/tools/pkgconf/pkgconf.exe \ | ||
-D VCPKG_INSTALL_OPTIONS="--x-buildtrees-root=C:/build" | ||
``` | ||
|
||
### Build | ||
|
||
```sh | ||
cmake --build build | ||
``` | ||
|
||
## Android | ||
|
||
Android runs on a number of different CPU architectures. | ||
The most common one is `arm64`. The platform to build for is specified via triplet. | ||
|
||
The following triplets are possible: | ||
|
||
- `arm64-android` | ||
- `arm-neon-android` | ||
- `x64-android` | ||
- `x86-android` | ||
|
||
### Using a docker image | ||
|
||
There is a simple script that helps building everything by using a docker image. | ||
|
||
```sh | ||
triplet=arm64-android ./scripts/build.sh | ||
``` | ||
|
||
### Building locally | ||
|
||
Make sure you have the following tools installed | ||
|
||
- cmake | ||
- The Android SDK including NDK | ||
|
||
#### Configure | ||
|
||
```sh | ||
export ANDROID_NDK_HOME=[path to your android ndk] | ||
cmake -S QField \ | ||
-B build \ | ||
-D VCPKG_TARGET_TRIPLET=arm64-android | ||
``` | ||
|
||
#### Build | ||
|
||
```sh | ||
cmake --build build | ||
``` | ||
|
||
## iOS Simulators for x64 processors | ||
|
||
To compile for iOS simulator, make sure you have installed recent versions of flex and bison (e.g. via homebrew) and added to the path. | ||
You also need the Qt sdk for ios installed. | ||
|
||
```sh | ||
brew install flex bison | ||
``` | ||
|
||
```sh | ||
export PATH="$(brew --prefix flex)/bin:$PATH" | ||
export PATH="$(brew --prefix bison)/bin:$PATH" | ||
``` | ||
|
||
### Configure | ||
|
||
```sh | ||
cmake -S . -B build-x64-ios \ | ||
-DVCPKG_TARGET_TRIPLET=x64-ios \ | ||
-GXcode \ | ||
-DWITH_VCPKG=ON \ | ||
-DCMAKE_SYSTEM_NAME=iOS \ | ||
-DCMAKE_OSX_SYSROOT=iphonesimulator \ | ||
-DCMAKE_SYSTEM_PROCESSOR=x86_64 \ | ||
-DWITH_SERIALPORT=OFF | ||
|
||
# Build | ||
cmake --build build-x64-ios | ||
``` | ||
|
||
## iOS application (ARM-64 processors architecture) | ||
|
||
```sh | ||
# Firstly, some compilation dependencies need to be installed | ||
# Homebrew can be used for this : https://docs.brew.sh/Installation | ||
brew install cmake flex bison python pkg-config autoconf automake libtool autoconf-archive nasm | ||
|
||
# Secondly, Xcode must be installed through the AppStore, then configured | ||
xcode-select --install | ||
sudo xcode-select --switch /Library/Developer/CommandLineTools | ||
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer | ||
xcodebuild -downloadPlatform iOS | ||
|
||
# Setup the environment for the build tools | ||
export PATH="$(brew --prefix flex)/bin:$(brew --prefix bison)/bin:$PATH" | ||
|
||
# Configure using CMake | ||
|
||
cmake -S . -B build-arm64-ios \ | ||
-DVCPKG_TARGET_TRIPLET=arm64-ios \ | ||
-DWITH_VCPKG=ON \ | ||
-DVCPKG_BUILD_TYPE=release \ | ||
-DCMAKE_SYSTEM_NAME=iOS \ | ||
-DCMAKE_OSX_SYSROOT=iphoneos \ | ||
-DCMAKE_OSX_ARCHITECTURES=arm64 \ | ||
-DCMAKE_SYSTEM_PROCESSOR=aarch64 \ | ||
-GXcode | ||
|
||
# Then, compile. To install an app on iOS, it must be signed using Xcode tools. | ||
cmake --build build-arm64-ios | ||
``` | ||
|
||
## Contribute | ||
|
||
Before commiting, install pre-commit to auto-format your code. | ||
|
||
``` | ||
pip install pre-commit | ||
pre-commit install | ||
``` | ||
|
||
## Developer Walkthrough for Linux | ||
|
||
The commands below are using `apt`, so they are written for Debian based systems like Ubuntu. Adapt accordingly for other distributions. | ||
|
||
### Initial Setup | ||
|
||
1. **Clone the Source Code:** | ||
- Use `git` to clone the repository from GitHub. | ||
|
||
2. **Install Required Tools:** | ||
- Install Qt Creator, a compiler, and other dependencies: | ||
```bash | ||
sudo apt update | ||
sudo apt install qtcreator build-essential | ||
``` | ||
|
||
#### Build | ||
|
||
1. **Build from Command Line:** | ||
- Run the convenience script to build the project: | ||
```bash | ||
./scripts/build-for-linux.sh | ||
``` | ||
|
||
2. **Resolve Dependencies:** | ||
- If the build fails, check the error output for missing dependencies and install them as recommended. | ||
|
||
#### Setup the IDE | ||
|
||
1. **Open Qt Creator:** | ||
- Launch Qt Creator from your application menu or terminal. | ||
|
||
2. **Setup Qt Installation:** | ||
- Go to `Preferences -> Kits -> Qt Versions -> Add`. | ||
- Select `qmake` from `build-x64-linux/vcpkg_installed/x64-linux/tools/Qt6/bin/qmake`. | ||
|
||
3. **Create a New Kit:** | ||
- Add a new kit in the `Kits` tab, selecting the newly added Qt version. | ||
|
||
4. **Create a New Project:** | ||
- Open the `CMakeLists.txt` file from the source code directory. | ||
- Select the newly created kit with a Debug configuration, pointing to the `build-x64-linux` directory. | ||
|
||
You are now ready to develop and run the project using Qt Creator! |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# QField API documentation | ||
|
||
## Introduction | ||
|
||
[QField](https://qfield.org) focuses on efficiently getting GIS fieldwork | ||
done and exchanging data between the field and the office in a comfortable | ||
and user-friendly way. QField runs on Android and iOS as well as Linux, | ||
macOS, and Windows. | ||
|
||
Built on top of the popular QGIS open-source project, QField lets users | ||
consume fully configured projects in the field, allowing for customized | ||
feature forms, map themes, print layouts, and more, bringing the power of | ||
QGIS to your fingertips. | ||
|
||
Leveraging open source libraries such as gdal, SQLite and PostGIS, QField | ||
reads, displays and allows editing of a wide variety of spatial vector and | ||
raster datasets. Users can view and modify datasets wherever they are, | ||
whether they have been downloaded onto your device, shared in emails or | ||
transferred via USB cable. | ||
|
||
QField source code is available at | ||
[https://github.com/opengisch/QField](https://github.com/opengisch/QField). |
Oops, something went wrong.