From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Luo Zhenhua-B19537 <B19537@freescale.com>
Subject: Re: Using external source trees with OE-Core
Date: Fri, 24 Feb 2012 17:36:02 +0000 [thread overview]
Message-ID: <1330104962.8430.4.camel@ted> (raw)
In-Reply-To: <CAEsOVNe0Fe5qyzYWK3Tf5P1=oYMnB3n-LoOVdE5bk-EkHdPf3A@mail.gmail.com>
On Fri, 2012-02-24 at 16:55 +0000, McClintock Matthew-B29882 wrote:
> We do something very similar to this currently. I've pushed what we
> are using here:
>
> https://github.com/mattsm/meta-fsl-local-sdk
>
> It would be nice to consolidate all the required bits upstream... =)
I would warn you that there is code in there that is clearly
inappropriate for OE-Core.
It would also explain that bug report you sent me which referenced
"do_populate_sysroot_post" and I asked what local modifications you had
and you said "none" ;-).
Does the patch in this thread take care of your needs regarding the
srctree and clean classes?
For cleanobjs, I can see advantages in merging something like that into
the core...
Cheers,
Richard
next prev parent reply other threads:[~2012-02-24 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 12:55 Using external source trees with OE-Core Richard Purdie
2012-02-24 13:49 ` Andreas Oberritter
2012-02-24 14:41 ` Mark Hatle
2012-02-24 14:01 ` Bruce Ashfield
2012-02-24 16:55 ` McClintock Matthew-B29882
2012-02-24 17:36 ` Richard Purdie [this message]
2012-02-24 17:44 ` McClintock Matthew-B29882
2012-02-24 16:59 ` Chris Larson
2012-02-24 18:25 ` Rich Pixley
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=1330104962.8430.4.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B19537@freescale.com \
--cc=B29882@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox