All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe REYNES <philippe.reynes@softathome.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 2/2] tools: binman: main.py: add /tmp/sandbox sys.path
Date: Thu, 27 Jan 2022 16:15:49 +0100	[thread overview]
Message-ID: <1d1e6038-e600-a72f-e4ed-39f553a26c8c@softathome.com> (raw)
In-Reply-To: <CAPnjgZ2UDFXmfy=aLJ8ixKmCrhZc9AP9m4MPJ4NDJ4ZTEfgu3g@mail.gmail.com>

Hi Simon,

Le 27/01/2022 à 16:06, Simon Glass a écrit :
> Hi Philippe,
>
> On Thu, 27 Jan 2022 at 07:03, Philippe Reynes
> <philippe.reynes@softathome.com> wrote:
>> Adds /tmp/sandbox to sys.path to look for libfdt,
>> otherwise ci is broken if a py_test uses binman.
>>
>> Signed-off-by: Philippe Reynes <philippe.reynes@softathome.com>
>> ---
>>   tools/binman/main.py | 1 +
>>   1 file changed, 1 insertion(+)
> Which test uses /tmp/sandbox to build U-Boot? We might need to use
> --toolpath for this, or set PYTHONPATH in the caller?


I have added a test that use binman in vboot (for global image signature,
a header added before the image). This path should be added for the CI,
otherwise tests "sandbox test.pyt " and "sandbox with clan test.py" fail.


>> diff --git a/tools/binman/main.py b/tools/binman/main.py
>> index f62394043d..7d52482c0c 100755
>> --- a/tools/binman/main.py
>> +++ b/tools/binman/main.py
>> @@ -42,6 +42,7 @@ sys.path.insert(2, 'scripts/dtc/pylibfdt')
>>   sys.path.insert(2, os.path.join(srctree, 'scripts/dtc/pylibfdt'))
>>   sys.path.insert(2, os.path.join(srctree, 'build-sandbox/scripts/dtc/pylibfdt'))
>>   sys.path.insert(2, os.path.join(srctree, 'build-sandbox_spl/scripts/dtc/pylibfdt'))
>> +sys.path.insert(2, os.path.join(srctree, '/tmp/sandbox/scripts/dtc/pylibfdt'))
>>
>>   # When running under python-coverage on Ubuntu 16.04, the dist-packages
>>   # directories are dropped from the python path. Add them in so that we can find
>> --
>> 2.17.1
>>
> Regards,
> Simon
Regards,
Philippe




  reply	other threads:[~2022-01-27 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 14:03 [PATCH 1/2] tools: binman: main.py: add build-sandbox in sys.path Philippe Reynes
2022-01-27 14:03 ` [PATCH 2/2] tools: binman: main.py: add /tmp/sandbox sys.path Philippe Reynes
2022-01-27 15:06   ` Simon Glass
2022-01-27 15:15     ` Philippe REYNES [this message]
2022-02-26 18:36       ` Simon Glass
2022-02-26 18:36 ` [PATCH 1/2] tools: binman: main.py: add build-sandbox in sys.path Simon Glass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1d1e6038-e600-a72f-e4ed-39f553a26c8c@softathome.com \
    --to=philippe.reynes@softathome.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.