All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hart, Darren" <darren.hart@intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
	Trevor Woerner <twoerner@gmail.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Cc: "Wold, Saul" <saul.wold@intel.com>
Subject: Re: Question on building out-of-tree modules on the target
Date: Fri, 29 May 2015 19:58:37 +0000	[thread overview]
Message-ID: <D18E10A4.D001E%darren.hart@intel.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237988EFAF5B@ORSMSX101.amr.corp.intel.com>

On 5/29/15, 12:46 PM, "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
wrote:

>Ok - so we established that we want it... If I get some clarifications in
>there about the "rarity" of the situation that would allow someone to
>develop on the target and also the benefits of having a verified
>cross-development system if they were to develop on the host, does the
>rest of the section stand as is?  Are there any issues with it?


Adding something like:

"While the traditional Yocto Project development model would be to include
kernel modules as part of the normal build process, some developers find
it useful to build modules on the target."

This section is lagging the 1.8 addition of kernel-devsrc, which was not
applied uniformly across all included SDK images. There is probably a
patch necessary to do that for a 1.8 point release, and then this document
could be made to reflect that.

--
Darren

>
>Thanks, 
>Scott
>
>>-----Original Message-----
>>From: Hart, Darren
>>Sent: Friday, May 29, 2015 12:40 PM
>>To: Trevor Woerner; Rifenbark, Scott M; yocto@yoctoproject.org
>>Cc: Wold, Saul
>>Subject: Re: [yocto] Question on building out-of-tree modules on the
>>target
>>
>>On 5/29/15, 12:21 PM, "Trevor Woerner" <twoerner@gmail.com> wrote:
>>
>>>Hi Scott,
>>>
>>>On 05/18/15 10:42, Rifenbark, Scott M wrote:
>>>> I have a section in the YP Linux Kernel Development Manual that talks
>>>>about building out-of-tree-modules on the target -
>>>
>>>Interestingly enough, I was just reading through that document the
>>>other day. As soon as I saw a section titled "Building Out-Of-Tree
>>>Modules _On The Target_" I thought to myself "why would anyone be doing
>>>development on the target and not the host?" and skipped to the next
>>section.
>>>
>>>If it were me, I'd just remove that section altogether. I'm of the
>>>opinion that doing development work on the target is wrong (if for no
>>>other reason than to prove your cross-development setup is working
>>>correctly), but that's just me.
>>>
>>>;-)
>>>
>>
>>I personally agree, but having it documented means I get to answer a lot
>>few
>>emails about people insisting on doing this. The section stays.
>>
>>--
>>Darren Hart
>>Intel Open Source Technology Center
>>
>
>


-- 
Darren Hart
Intel Open Source Technology Center




  reply	other threads:[~2015-05-29 19:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 14:42 Question on building out-of-tree modules on the target Rifenbark, Scott M
2015-05-29 19:21 ` Trevor Woerner
2015-05-29 19:28   ` Nicholas Krause
2015-05-29 19:37     ` Trevor Woerner
2015-05-29 19:40       ` Nicholas Krause
2015-05-29 19:40   ` Hart, Darren
2015-05-29 19:46     ` Rifenbark, Scott M
2015-05-29 19:58       ` Hart, Darren [this message]
2015-05-29 20:03         ` Rifenbark, Scott M
2015-05-29 20:53         ` Rifenbark, Scott M

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=D18E10A4.D001E%darren.hart@intel.com \
    --to=darren.hart@intel.com \
    --cc=saul.wold@intel.com \
    --cc=scott.m.rifenbark@intel.com \
    --cc=twoerner@gmail.com \
    --cc=yocto@yoctoproject.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.