From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: simple dependency question
Date: Thu, 24 Jul 2014 08:25:35 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407240825160.10708@localhost> (raw)
In-Reply-To: <1406203585.27697.5.camel@ted>
On Thu, 24 Jul 2014, Richard Purdie wrote:
> On Thu, 2014-07-24 at 07:13 -0400, Robert P. J. Day wrote:
> > i realize that "DEPENDS" represents build-time dependencies, as in
> > ... all of the DEPENDS recipes must build *completely* before this
> > recipe can *begin* to build, is that correct?
> >
> > however, in something like module.bbclass where one finds:
> >
> > do_make_scripts[deptask] = "do_populate_sysroot"
> >
> > does that now *override* the normal build-time dependency to say only
> > that this recipe's do_make_scripts task need only wait until all of
> > the "DEPENDS" recipes have completed their do_populate_sysroot tasks?
>
> The original DEPENDS meaning remains unchanged and applies to the
> configure task. The behaviour of DEPENDS comes from:
>
> do_configure[deptask] = "do_populate_sysroot"
>
> which means the configure task waits for all the populate_sysroot tasks
> of DEPENDS to complete before executing this task.
>
> do_make_scripts[deptask] = "do_populate_sysroot"
>
> Adds constraints to the make_scripts task where it also must wait until
> all DEPENDS populate_sysroot have run before it can.
>
> > in other words, the instant i define an inter-task dependency, does
> > that relax the normal strong build dependency? since, if it didn't,
> > this wouldn't make any sense.
>
> and hence no, it doesn't relax other rules.
ah, i should have known/remembered that. thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-07-24 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 11:13 simple dependency question Robert P. J. Day
2014-07-24 11:15 ` Robert P. J. Day
2014-07-24 12:06 ` Richard Purdie
2014-07-24 12:25 ` Robert P. J. Day [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=alpine.LFD.2.11.1407240825160.10708@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox