All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] kernel.bbclass: make external module compile
Date: Wed, 6 Jul 2011 19:31:43 +0200	[thread overview]
Message-ID: <CADF341D-7B4B-416D-BAEE-38A5FC373788@chargestorm.se> (raw)
In-Reply-To: <4E148F5C.4020902@linux.intel.com>

Hi Darren,

On 6 jul 2011, at 18:37, "Darren Hart" <dvhart@linux.intel.com> wrote:
> Please see the following commit log:
> 
> commit 3b49416fc7a7ee9bfe722f2e6089aa18df41dc58
> Author: Darren Hart <dvhart@linux.intel.com>
> Date:   Tue Mar 8 17:09:10 2011 -0800
> 
>    kernel/bbclass: rework kernel and module classes to allow for building out-of-tree modul
> 
> 
> In particular, the following:
> 
>    Care is also taken to clean the hostprogs in scripts, and the modules are
>    responsible for building them as needed. Although it is unclear to me if this is
>    really necessary, especially considering that modules put these bits back as
>    soon as they compile. If we are not generating an sstate package, I suspect we
>    can ignore these.
> 
> The scripts are recreated during the build of module.bbclass derived recipes.
> Are you trying to build modules independently of this method? Richard expressed
> concerns about not including host specific binaries in the sstate, which was
> part of the reason this approach was taken.

Thanks for pointing out this, especially the first sentence in this paragraph. No matter how many times I've looked at both the recipes in question, as well as the meta/classes directory, I haven't noticed that the old, inherited recipes were not using module.bbclass, but rather inherited module-base.bbclass directly. I'll assume that once I change that, and fix the recipes properly all my issues will go away.

Once more, thanks for pointing me to the real problem.

Cheers,
Anders


  reply	other threads:[~2011-07-06 17:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 12:01 [PATCH 0/1] Fix external module compilations Anders Darander
2011-07-05 12:01 ` [PATCH 1/1] kernel.bbclass: make external module compile Anders Darander
2011-07-05 12:44   ` Phil Blundell
2011-07-05 12:54     ` Anders Darander
2011-07-05 13:09       ` Richard Purdie
2011-07-05 15:04         ` Anders Darander
2011-07-06 16:37           ` Darren Hart
2011-07-06 17:31             ` Anders Darander [this message]
2011-07-06 18:22               ` Darren Hart
2011-07-08 13:31                 ` Anders Darander

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=CADF341D-7B4B-416D-BAEE-38A5FC373788@chargestorm.se \
    --to=anders@chargestorm.se \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@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.