Makefile: deprecate in favor of Meson

Building the python bindings is complicated and not very practical to do
in a Makefile. The setuptools invocations previously used are confusing
and don't work very well compared to Meson. Having two build systems
that do different things is also confusing though.

Since Meson can do everything that Make can do, but the reverse is not
true, we deprecate the latter and warn when you use it.

GNU Make can emit a $(warning) on every Makefile run, which is a bit
noisy but means we don't need to have every target depend on a PHONY
target (preventing built targets from being seen as up to date).

Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Message-ID: <20250430152601.43554-2-eschwartz@gentoo.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
1 file changed
tree: 47e99e205ff431331dbeff2151f11cf3e62f7064
  1. .github/
  2. Documentation/
  3. libfdt/
  4. pylibfdt/
  5. scripts/
  6. tests/
  7. .clang-format
  8. .editorconfig
  9. .gitignore
  10. BSD-2-Clause
  11. checks.c
  12. CONTRIBUTING.md
  13. convert-dtsv0-lexer.l
  14. data.c
  15. dtc-lexer.l
  16. dtc-parser.y
  17. dtc.c
  18. dtc.h
  19. dtdiff
  20. fdtdump.c
  21. fdtget.c
  22. fdtoverlay.c
  23. fdtput.c
  24. flattree.c
  25. fstree.c
  26. GPL
  27. livetree.c
  28. Makefile
  29. Makefile.convert-dtsv0
  30. Makefile.dtc
  31. Makefile.utils
  32. MANIFEST.in
  33. meson.build
  34. meson_options.txt
  35. README.license
  36. README.md
  37. setup.py
  38. srcpos.c
  39. srcpos.h
  40. TODO
  41. treesource.c
  42. util.c
  43. util.h
  44. VERSION.txt
  45. version_gen.h.in
  46. yamltree.c
README.md

Device Tree Compiler and libfdt

The source tree contains the Device Tree Compiler (dtc) toolchain for working with device tree source and binary files and also libfdt, a utility library for reading and manipulating the binary format.

dtc and libfdt are maintained by:

Python library

A Python library wrapping libfdt is also available. To build this you will need to install swig and Python development files. On Debian distributions:

$ sudo apt-get install swig python3-dev

The library provides an Fdt class which you can use like this:

$ PYTHONPATH=../pylibfdt python3
>>> import libfdt
>>> fdt = libfdt.Fdt(open('test_tree1.dtb', mode='rb').read())
>>> node = fdt.path_offset('/subnode@1')
>>> print(node)
124
>>> prop_offset = fdt.first_property_offset(node)
>>> prop = fdt.get_property_by_offset(prop_offset)
>>> print('%s=%s' % (prop.name, prop.as_str()))
compatible=subnode1
>>> node2 = fdt.path_offset('/')
>>> print(fdt.getprop(node2, 'compatible').as_str())
test_tree1

You will find tests in tests/pylibfdt_tests.py showing how to use each method. Help is available using the Python help command, e.g.:

$ cd pylibfdt
$ python3 -c "import libfdt; help(libfdt)"

If you add new features, please check code coverage:

$ sudo apt-get install python3-coverage
$ cd tests
# It's just 'coverage' on most other distributions
$ python3-coverage run pylibfdt_tests.py
$ python3-coverage html
# Open 'htmlcov/index.html' in your browser

The library can be installed with pip from a local source tree:

$ pip install . [--user|--prefix=/path/to/install_dir]

Or directly from a remote git repo:

$ pip install git+git://git.kernel.org/pub/scm/utils/dtc/dtc.git@main

The install depends on libfdt shared library being installed on the host system first. Generally, using --user or --prefix is not necessary and pip will use the default location for the Python installation which varies if the user is root or not.

You can also install everything via make if you like, but pip is recommended.

To install both libfdt and pylibfdt you can use:

$ make install [PREFIX=/path/to/install_dir]

To disable building the python library, even if swig and Python are available, use:

$ make NO_PYTHON=1

More work remains to support all of libfdt, including access to numeric values.

Mailing lists