From: "Rémi Peuvergne" <remi.peuvergne@openwide.fr>
To: bitbake-devel@lists.openembedded.org
Subject: Question about python interpreter in methods embedded in recipes
Date: Wed, 12 Aug 2015 11:23:55 +0200 (CEST) [thread overview]
Message-ID: <2007448077.5597509.1439371435023.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <461580693.5596129.1439370747631.JavaMail.root@openwide.fr>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Hi everyone !
I've been investigating on an issue when building an image, and I gave up doing what I first wanted.
I'd like to know more about the issue, and possibly suggest an improvement to bitbake...
The issue is related to "embedded python methods" in recipes.
In my image recipe, I'm modifying the rootfs (basically to add a hashed password to /etc/shadow), with something like :
python set_password() {
<some piece of python script here>
}
The thing is, this piece of code is executed by the *host* interpreter, so it depends on the dev machine (in my case I ran into an issue with crypt.mksalt() not being available).
It would be nice to allow executing this with the *native* interpreter, the one built during the whole image build process.
I tried inheriting pythonnative, which sets the PYTHON variable the correct way, but it's not used for those methods...
I guess it's not easy, since it would need to pass the datastore, but I wonder if there's any smart solution to this ?
Thanks for your help !
Remi
[-- Attachment #2: Type: text/html, Size: 1323 bytes --]
next parent reply other threads:[~2015-08-12 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <461580693.5596129.1439370747631.JavaMail.root@openwide.fr>
2015-08-12 9:23 ` Rémi Peuvergne [this message]
2015-08-17 7:43 ` Question about python interpreter in methods embedded in recipes Richard Purdie
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=2007448077.5597509.1439371435023.JavaMail.root@openwide.fr \
--to=remi.peuvergne@openwide.fr \
--cc=bitbake-devel@lists.openembedded.org \
/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.