From: Ciprian Ciubotariu <cheepeero@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Package selection
Date: Tue, 19 Jun 2012 03:32:03 +0300 [thread overview]
Message-ID: <7888297.NxAaM4fFbI@pink> (raw)
In-Reply-To: <CAE9DZUTckmmxoW_kdKksyT7tq86zV-AacJGwrEqpCFh+vBZYFw@mail.gmail.com>
On Monday 18 June 2012 11:57:01 Dallas Clement wrote:
> Lastly, it is possible to avoid the repeated fetching of source
> packages? In other words, can the source URI's point to packages in a
> local file system repository?
I have extracted some minimal code from the old OE srctree.bbclass file that
allows us to do minimal rebuilds when developing:
S="/path/to/your/sources/"
SRC_URI=""
def remove_tasks(deltasks, d):
for task in filter(lambda k: d.getVarFlag(k, "task"), d.keys()):
deps = d.getVarFlag(task, "deps")
for preptask in deltasks:
if preptask in deps:
deps.remove(preptask)
d.setVarFlag(task, "deps", deps)
#addtask configure after do_setscene
python () {
remove_tasks(["do_patch", "do_unpack", "do_fetch"], d)
}
Note that setting S there makes bitbake treat this as the work folder, so
you'll get oe-core build artifacts there.
Also, you need to bitbake -c cleanall <your-package> to make bitbake forget it
has already built your package, and next bitbake <your-package> to perform the
minimal build.
>
> Thanks much,
>
> Dallas
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2012-06-19 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 16:57 Package selection Dallas Clement
2012-06-18 18:26 ` Mark Hatle
2012-06-18 18:31 ` Khem Raj
2012-06-19 0:32 ` Ciprian Ciubotariu [this message]
2012-06-19 1:19 ` Dallas Clement
2012-06-19 4:34 ` j
2012-06-19 4:40 ` Khem Raj
2012-06-19 4:46 ` j
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=7888297.NxAaM4fFbI@pink \
--to=cheepeero@gmx.net \
--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.