tag | 57f77f536931535fa341ad9473c5b06c4d5b9799 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Wed Jan 13 18:07:54 2021 -0800 |
object | b3dedeaa7107178b3f577cc986c91113c92e8edd |
Android mainline 11.0.0 release 3
commit | b3dedeaa7107178b3f577cc986c91113c92e8edd | [log] [tgz] |
---|---|---|
author | Xin Li <delphij@google.com> | Wed Oct 30 15:12:28 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Wed Oct 30 15:12:28 2019 -0700 |
tree | 6ac83782c853fe09e817de65a2908301672284e0 | |
parent | f75ab602bb5e781b843ef6e044fb1d24f7a4309e [diff] | |
parent | c09def76c347eda08c3405fe5a4f238f2438aaa9 [diff] |
[automerger skipped] DO NOT MERGE - qt-qpr1-dev-plus-aosp-without-vendor@5915889 into stage-aosp-master am: 90a6fa7c3b am: c09def76c3 -s ours am skip reason: subject contains skip directive Change-Id: Ie7e471b770ac98af25313598b5d83d4e2a28d024
kms++ is a C++11 library for kernel mode setting.
Also included are some simple utilities for KMS and python bindings for kms++.
To build the Python bindings you need to set up the git-submodule for pybind11:
git submodule update --init
And to compile:
$ mkdir build $ cd build $ cmake .. $ make -j4
Directions for cross compiling depend on your environment.
These are for mine with buildroot:
$ mkdir build $ cd build $ cmake -DCMAKE_TOOLCHAIN_FILE=<buildrootpath>/output/host/usr/share/buildroot/toolchainfile.cmake .. $ make -j4
Your environment may provide similar toolchainfile. If not, you can create a toolchainfile of your own, something along these lines:
SET(CMAKE_SYSTEM_NAME Linux) SET(BROOT "<buildroot>/output/") # specify the cross compiler SET(CMAKE_C_COMPILER ${BROOT}/host/usr/bin/arm-buildroot-linux-gnueabihf-gcc) SET(CMAKE_CXX_COMPILER ${BROOT}/host/usr/bin/arm-buildroot-linux-gnueabihf-g++) # where is the target environment SET(CMAKE_FIND_ROOT_PATH ${BROOT}/target ${BROOT}/host) SET(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM ONLY) SET(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) SET(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
You can use the following cmake flags to control the build. Use -DFLAG=VALUE
to set them.
Option name | Values | Default | Notes |
---|---|---|---|
CMAKE_BUILD_TYPE | Release/Debug | Release | |
BUILD_SHARED_LIBS | ON/OFF | OFF | |
KMSXX_ENABLE_PYTHON | ON/OFF | ON | |
KMSXX_ENABLE_KMSCUBE | ON/OFF | OFF | |
KMSXX_PYTHON_VERSION | python3/python2 | python3;python2 | Name of the python pkgconfig file |
You can use the following runtime environmental variables to control the behavior of kms++.
Variable | Description |
---|---|
KMSXX_DISABLE_UNIVERSAL_PLANES | Set to disable the use of universal planes |
KMSXX_DISABLE_ATOMIC | Set to disable the use of atomic modesetting |
KMSXX_DEVICE | Path to the card device node to use |
KMSXX_DRIVER | Name of the driver to use. The format is either “drvname” or “drvname:idx” |
You can run the python code directly from the build dir by defining PYTHONPATH env variable. For example:
PYTHONPATH=build/py py/tests/hpd.py