tag | bd402b88f993b8e607334be655db212c1a22bcd0 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Wed Apr 24 19:43:57 2024 -0700 |
object | 5843aaced4b6b308d0a02b58901b3ff1acfab005 |
aml_per_341614000 (11428529,com.google.android.go.permission,com.google.android.permission)
commit | 5843aaced4b6b308d0a02b58901b3ff1acfab005 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue May 10 06:58:22 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Tue May 10 06:58:22 2022 +0000 |
tree | 2a349626debe337534905374d428e93e594fb813 | |
parent | 984f6fc527c1ed1d1ef6e848bd87931ba38167fa [diff] | |
parent | f0687c8a10b3e371dbe09214db6664e37c283cca [diff] |
Snap for 8564071 from f0687c8a10b3e371dbe09214db6664e37c283cca to mainline-permission-release Change-Id: I2a6c8a667f29c3726446f9a2ca41a9ef95f2c526
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