From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Examples of srctree and gitver
Date: Tue, 01 Jun 2010 09:36:40 -0400 [thread overview]
Message-ID: <4C050CE8.4080102@cbnco.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE894455A0F458@dlee02.ent.ti.com>
Ambrose, Martin wrote:
> On Sun, May 30, 2010 at 14:49:32, Chris Larson wrote:
>> Aside: the way it does so is quite the hack, we need to figure out
>> a better way to manipulate the task graph like this.
>
> Maybe that explains the problem I'm seeing with the dependency graph when using srctree.
> Then it goes straight to the configure phase without ensuring the dependencies are present.
Yes, I see similar things. I'm still on an ancient tree with
do_populate_staging(). If memory serves, the prerequisite packages are
unpacked, compiled and installed, but do_stage isn't run before the
srctree recipe's do_configure.
As long as you're not doing parallel builds it's easy enough to work
around: just put the libraries you need in your IMAGE_INSTALL before the
srctree packages.
Mike
next prev parent reply other threads:[~2010-06-01 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 15:07 Examples of srctree and gitver Ambrose, Martin
2010-05-30 16:16 ` Chris Larson
2010-05-30 19:26 ` Ambrose, Martin
2010-05-30 19:49 ` Chris Larson
2010-05-31 22:47 ` Ambrose, Martin
2010-06-01 13:36 ` Michael Smith [this message]
2010-06-01 14:33 ` Chris Larson
2010-06-02 21:47 ` Ambrose, Martin
2010-06-03 13:55 ` Ambrose, Martin
2010-05-30 16:27 ` Michael Smith
2010-05-30 17:10 ` Chris Larson
2010-05-30 19:26 ` Ambrose, Martin
2010-05-30 20:37 ` Michael Smith
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=4C050CE8.4080102@cbnco.com \
--to=msmith@cbnco.com \
--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.