simple dependency question

simple dependency question

[Robert P. J. Day]

  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?

  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.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: simple dependency question

[Robert P. J. Day]

On Thu, 24 Jul 2014, 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?
>
>   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.

  sorry, i shouldn't have described that as an "inter-task"
dependency, i realize that's different, as in:

ncurses.inc:do_test[depends] = "unifdef-native:do_populate_sysroot"

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: simple dependency question

[Richard Purdie]

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.

Cheers,

Richard

Re: simple dependency question

[Robert P. J. Day]

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
========================================================================