tag | 616f087f50cf3b093b131c9c41f9757290b0e916 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Thu Feb 18 11:07:00 2021 -0800 |
object | da532047ae149efa759c779ee727a7546d6be1ce |
Android VTS 10.0 Release 7 (7097708)
commit | da532047ae149efa759c779ee727a7546d6be1ce | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Mon Feb 25 04:00:57 2019 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Mon Feb 25 04:00:57 2019 +0000 |
tree | dea7a30f3bdd636d3617eb6d98d4acb9df7c1d01 | |
parent | 395a0ed56e5f72d75f865c63b8bf85385cecca4f [diff] | |
parent | 7fa58fa14436676f36c62bead0471c2e367d0af0 [diff] |
Snap for 5333170 from 7fa58fa14436676f36c62bead0471c2e367d0af0 to qt-release Change-Id: I88cf551967bbc92d9a95dc6c2aecc65cf37d204f
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 |
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