question about kernel .scc and .cfg files

question about kernel .scc and .cfg files

[Robert P. J. Day]

  once a SRC_URI refers to an .scc file that further refers to a .cfg
file, is there any need for the SRC_URI file to *additionally* refer
explicitly to that same .cfg file? i ask only because i've noticed
this on occasion and i'm not sure if there's something subtle going on
that i don't know about.

rday

-- 

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

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

Re: question about kernel .scc and .cfg files

[Bruce Ashfield]

On Sat, Feb 21, 2015 at 2:43 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
>   once a SRC_URI refers to an .scc file that further refers to a .cfg
> file, is there any need for the SRC_URI file to *additionally* refer
> explicitly to that same .cfg file? i ask only because i've noticed
> this on occasion and i'm not sure if there's something subtle going on
> that i don't know about.

There's no need. Everything is migrated into the kernel workdir, and the
.scc processing picks up the .cfg. It's that way, since the .scc + .cfgs are
used elsewhere and in that format are fully standalone.

Cheers,

Bruce

>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
>
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: question about kernel .scc and .cfg files

[Robert P. J. Day]

On Sat, 21 Feb 2015, Bruce Ashfield wrote:

> On Sat, Feb 21, 2015 at 2:43 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> >   once a SRC_URI refers to an .scc file that further refers to a
> > .cfg file, is there any need for the SRC_URI file to
> > *additionally* refer explicitly to that same .cfg file? i ask only
> > because i've noticed this on occasion and i'm not sure if there's
> > something subtle going on that i don't know about.
>
> There's no need. Everything is migrated into the kernel workdir, and
> the .scc processing picks up the .cfg. It's that way, since the .scc
> + .cfgs are used elsewhere and in that format are fully standalone.

  ok ... so once a .scc file is picked up that further refers to .cfg
files, there is no need to refer to those same .cfg files directly.
that's what i'd understood, but every so often, i run across recipes
that do things i don't expect, and it always makes me wonder if i
don't quite understand something.

  it's my sheldon cooper-like OCD that motivates me to want to remove
stuff that has no need to be there. bazinga.

rday

-- 

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

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