Subject: [bug#31520] [PATCH] gnu: u-boot-tools: Enable tests.

From: Danny Milosavljevic <[email-masked]>
Date: Mon, 28 May 2018 00:05:45 +0200

Hi Ludo,

On Sun, 27 May 2018 15:10:05 +0200
[email-masked] (Ludovic Courtès) wrote:

> > dtc has Python bindings and we build them.  
> 
> But then we do not need a search path definition in dtc itself; the one
> in Python is enough.  Or am I missing something?

There's a libfdt.py, provided by the dtc package, and u-boot-tools
tests use it.

Right now, we're not necessarily installing libfdt.py into python (?) or the
profile or anything.

Like u-boot-tools has somewhere (in its unit tests):

  #!/usr/bin/env python3
  import pylibfdt

And dtc provides

  libfdt.py

which could be useful for Python programmers, too.

>   1. dtc provides Python bindings that are useful to Python
>      programmers.  This is addressed by having both Python and dtc in
>      the same profile, in which case PYTHONPATH is automatically
>      defined.  Nothing special to do.

Yes.  But in this case u-boot-tools uses libfdt.py when building (testing) itself.