From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] genmanual: generates kconfiglib.pyc in Buildroot source tree
Date: Wed, 4 Dec 2013 23:52:27 +0100 [thread overview]
Message-ID: <20131204225227.GH3332@free.fr> (raw)
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?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2013-12-04 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 22:52 Yann E. MORIN [this message]
2013-12-05 8:00 ` [Buildroot] genmanual: generates kconfiglib.pyc in Buildroot source tree Arnout Vandecappelle
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=20131204225227.GH3332@free.fr \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox