tag | 104fe04da33eb29e2a3ceedba41c056e31974bc3 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Tue Jun 07 22:33:15 2022 -0700 |
object | ed3537b006b618ea1b0efc1efdd501728862065b |
Android Mainline 12.0.0 Release 100 (8305796,com.google.android.networkstack)
commit | ed3537b006b618ea1b0efc1efdd501728862065b | [log] [tgz] |
---|---|---|
author | Xin Li <delphij@google.com> | Sat Feb 20 15:33:44 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Sat Feb 20 15:33:44 2021 +0000 |
tree | 8ac1a7266fc264022adc90f0839f652add01ecbc | |
parent | cbedaad4aff398b8d87523e5c55711fd53edede8 [diff] | |
parent | 77c92534ef119fdd4e701a87ddec3c6264b6f190 [diff] |
[automerger skipped] Mark ab/7061308 as merged in stage. am: c49c3e1965 -s ours am: ec6c83734d -s ours am: 77c92534ef -s ours am skip reason: Change-Id Ie0f77abf4416296aef54b2519f5ec1db072b4fe9 with SHA-1 1967f06dd7 is in history Original change: undetermined MUST ONLY BE SUBMITTED BY AUTOMERGER Change-Id: I6bc36cd78276aef367b0b47e1820c927d319873e
kms++ is a C++17 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:
meson build ninja -C build
meson build --cross-file=<path-to-meson-cross-file> ninja -C build
Here is my cross file for arm32 (where ${BROOT} is path to my buildroot output dir):
[binaries] c = ['ccache', '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-gcc'] cpp = ['ccache', '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-g++'] ar = '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-ar' strip = '${BROOT}/host/bin/arm-buildroot-linux-gnueabihf-strip' pkgconfig = '${BROOT}/host/bin/pkg-config' [host_machine] system = 'linux' cpu_family = 'arm' cpu = 'arm' endian = 'little'
You can use meson options to configure the build. E.g.
meson build -Dbuildtype=debug -Dkmscube=true
Use meson configure build
to see all the configuration options and their current values.
kms++ specific build options are:
Option name | Values | Default | Notes |
---|---|---|---|
pykms | true, false | true | Python bindings |
kmscube | true, false | false | GLES kmscube |
omap | enabled, disabled, auto | auto | libdrm-omap support |
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