All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] genmanual: generates kconfiglib.pyc in Buildroot source tree
Date: Thu, 05 Dec 2013 09:00:06 +0100	[thread overview]
Message-ID: <52A03286.3070808@mind.be> (raw)
In-Reply-To: <20131204225227.GH3332@free.fr>

On 04/12/13 23:52, Yann E. MORIN wrote:
> Samuel, All,
>
> When one runs 'make manual', python will create:
>      support/scripts/kconfiglib.pyc
> in the Buildroot source tree.
>
> Python will happily run, even if it is not able to generate that file
> (eg. because the source tree is read-only).
>
> However, the file is not cleaned on 'make clean'. I'm a bit reluctant at
> adding it since it would try to remove a file outside of $(O), which
> could break parallel builds in multiple $(O) at the same time... Not
> sure what to do here.
>
> Since we do not really care about speed, would it be possible to tell
> python not to generate it at all?

  I do 'man python', and the first thing I see is

-B     Don't write .py[co] files on import. See also PYTHONDONTWRITEBYTECODE.


  I'd say, go for it! Unfortunately, you can't add it directly in the #! 
line of the script because all the arguments are concatenated together. 
So I guess the PYTHONDONTWRITEBYTECODE environment variable should be set 
when calling the script.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-12-05  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 22:52 [Buildroot] genmanual: generates kconfiglib.pyc in Buildroot source tree Yann E. MORIN
2013-12-05  8:00 ` Arnout Vandecappelle [this message]
2013-12-05 17:52   ` Yann E. MORIN
2013-12-05 18:04     ` Samuel Martin
2013-12-05 18:11       ` Yann E. MORIN

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=52A03286.3070808@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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.