From: Trevor Woerner <twoerner@gmail.com>
To: Nicholas Krause <xerofoify@gmail.com>,
"Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Cc: "Hart, Darren" <darren.hart@intel.com>,
"Wold, Saul" <saul.wold@intel.com>
Subject: Re: Question on building out-of-tree modules on the target
Date: Fri, 29 May 2015 15:37:34 -0400 [thread overview]
Message-ID: <5568BFFE.6020303@gmail.com> (raw)
In-Reply-To: <B1A8DC16-337A-45ED-BF82-2F34487B32C4@gmail.com>
On 05/29/15 15:28, Nicholas Krause wrote:
> On May 29, 2015 3:21:04 PM EDT, Trevor Woerner <twoerner@gmail.com> wrote:
>> 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.
>>
>> ;-)
> Your assuming the target isn't powerful enough for compiling. What if it is?
That's why I included that part in parenthesis :-) Many "embedded"
devices are well powerful enough for compiling, but doing all your
development on the host computer demonstrates your cross-development
environment is properly configured for all development tasks.
next prev parent reply other threads:[~2015-05-29 19:37 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 [this message]
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
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=5568BFFE.6020303@gmail.com \
--to=twoerner@gmail.com \
--cc=darren.hart@intel.com \
--cc=saul.wold@intel.com \
--cc=scott.m.rifenbark@intel.com \
--cc=xerofoify@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.