From: Roman I Khimov <khimov@altell.ru>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Development and Open Embedded
Date: Thu, 7 May 2009 09:25:32 +0400 [thread overview]
Message-ID: <200905070925.32935.khimov@altell.ru> (raw)
In-Reply-To: <loom.20090506T211326-740@post.gmane.org>
On Thursday 07 May 2009 01:33:45 Michael Sundius wrote:
> I'm wondering if anyone has done such a thing as creating a
> recipe that forgoes the "fetch" task and point the ${S} to
> a local devel tree.. then adds an extra onto the make command
> to place the object in another directory (maybe ${O})...
One of our engineers (Alexey Zaytsev <zaytsev@altell.ru>) have done this for
kernel:
==================================================================
python do_fetch() {
linux_prefetch = bb.data.getVar('LINUX_PREFETCH', d)
if not linux_prefetch:
bb.build.exec_func('base_do_fetch', d)
}
python do_unpack() {
import os
linux_prefetch = bb.data.getVar('LINUX_PREFETCH', d)
if not linux_prefetch:
bb.build.exec_func('base_do_unpack', d)
else:
s = bb.data.expand(bb.data.getVar('S', d), d)
os.system("ln -sf %s %s" % (linux_prefetch, s))
config = "file://" + bb.data.getVar('LINUX_CONFIG', d)
oe_unpack_file(bb.fetch.localpath(config, d), d)
}
==================================================================
You set LINUX_PREFETCH to point to git tree in local.conf and LINUX_CONFIG to
config file (LINUX_CONFIG is set in kernel .bb file). That's it. I think it's
very hacky and generally don't like the approach, but the thing works and he's
been working successfully with this hack building two kernels from the same
source base. Of course, there is also separate directory building there, but
that's done in classes (will try to extract a good patch).
Also, just to give more hack directions, there is "git/git_repo/.git" in
sources directory that can be symlinked into "${S}/git/.git", that would allow
using "bitbake -c compile -f" to rebuild the package working with sources in
normal way. I think making bitbake patch to add this symlink would be a bit
better to start with, but then there should be some enforcement of local HEAD
usage without constant "rev=..." specifying in .bb.
prev parent reply other threads:[~2009-05-07 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 21:33 Development and Open Embedded Michael Sundius
2009-05-06 21:44 ` Chris Larson
2009-05-06 22:09 ` Michael Sundius
2009-05-07 5:25 ` Roman I Khimov [this message]
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=200905070925.32935.khimov@altell.ru \
--to=khimov@altell.ru \
--cc=openembedded-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.