Comments

There is no point in compiling kernel modules in a separate task, run
right after do_compile. On the other hand merging those tasks will e.g.
make icecc used also for modules compilation, etc.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
---
meta/classes/kernel.bbclass | 6 +-----
1 files changed, 1 insertions(+), 5 deletions(-)

Op 14 dec. 2011, om 01:17 heeft Dmitry Eremin-Solenikov het volgende geschreven:
> On Wed, Dec 14, 2011 at 4:15 AM, Darren Hart <dvhart@linux.intel.com> wrote:>> >> >> On 12/13/2011 08:19 AM, Dmitry Eremin-Solenikov wrote:>>> There is no point in compiling kernel modules in a separate task, run>>> right after do_compile. On the other hand merging those tasks will e.g.>>> make icecc used also for modules compilation, etc.>> >> This split was done intentionally to allow tasks to be inserted between>> compile and compile_kernelmodules. See:> > Could you (or Koen) name any tasks that have to be inserted between kernel> and modules compilation please?
Building external modules that are referenced by internal ones for example. But besides that, this also allows me to build just *Image quickly and not having to wait for the modules to build.

On Thu, Dec 15, 2011 at 4:27 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Op 14 dec. 2011, om 01:17 heeft Dmitry Eremin-Solenikov het volgende geschreven:>>> On Wed, Dec 14, 2011 at 4:15 AM, Darren Hart <dvhart@linux.intel.com> wrote:>>>>>>>>> On 12/13/2011 08:19 AM, Dmitry Eremin-Solenikov wrote:>>>> There is no point in compiling kernel modules in a separate task, run>>>> right after do_compile. On the other hand merging those tasks will e.g.>>>> make icecc used also for modules compilation, etc.>>>>>> This split was done intentionally to allow tasks to be inserted between>>> compile and compile_kernelmodules. See:>>>> Could you (or Koen) name any tasks that have to be inserted between kernel>> and modules compilation please?>> Building external modules that are referenced by internal ones for example. But besides that, this also allows me to build just *Image quickly and not having to wait for the modules to build.
I've had the same thing here, just building the main image and not
wanting to wait for
kernel modules to compile. More of an incremental ad-hoc, scp and reboot sort of
workflow, but only building what you need in that situation is just
what a person wants.
Cheers,
Bruce
> -----BEGIN PGP SIGNATURE----->> iEYEARECAAYFAk7pvXkACgkQMkyGM64RGpE2pwCdFjZuuNW4ler8ES4OsKddTaB2> JnIAn0ME2FOwLyXeCS2DDBsTwKBFUKDt> =l9hr> -----END PGP SIGNATURE----->> _______________________________________________> Openembedded-core mailing list> Openembedded-core@lists.openembedded.org> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core>

On Tue, 2011-12-13 at 20:19 +0400, Dmitry Eremin-Solenikov wrote:
> There is no point in compiling kernel modules in a separate task, run> right after do_compile. On the other hand merging those tasks will e.g.> make icecc used also for modules compilation, etc.> > Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>> ---> meta/classes/kernel.bbclass | 6 +-----> 1 files changed, 1 insertions(+), 5 deletions(-)
Just to summarise the feedback, I think there valid reasons to have
these tasks separately so icecc is going to need to learn to deal with
this...
Cheers,
Richard