commit | 6fa8696774c4bda4bb7e3efabd7e1e58a899f5c1 | [log] [tgz] |
---|---|---|
author | Tomi Valkeinen <tomi.valkeinen@ti.com> | Tue Dec 01 09:14:19 2020 +0200 |
committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | Tue Dec 01 09:14:34 2020 +0200 |
tree | 33325ca8d790849ac8bd3e0847320bba38d8328b | |
parent | 0d6e3a43c2719263b907e8e03ac9ab35fc765013 [diff] |
Fix clang-tidy reported issues
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