From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: using OE efficiently for development
Date: Fri, 07 Mar 2014 12:19:11 -0500 [thread overview]
Message-ID: <5319FF8F.3060608@balister.org> (raw)
In-Reply-To: <CACgAsMdwRRbraDhMCQ17JMDq_dC2AN7q=oXqvCWR96VDidziZA@mail.gmail.com>
On 03/07/2014 10:08 AM, Kevyn-Alexandre Paré wrote:
> Hi Nicolas,
>
> On Thu, Mar 6, 2014 at 1:32 PM, Cliff Brake <cbrake@bec-systems.com> wrote:
>
> <snip>
>
>>
>> Here is another example using repo: https://github.com/kraj/angstrom-manifest
>>
>> The OE build system is complex, but is very flexible and works very
>> well. The flexibility of fetching sources in different ways is nice,
>> as different parts of the system really need different tools (are they
>> under heavy development, etc) vs forcing everything to be in git, etc.
>>
>
> Have seen kind of the same pattern as angstrom:
> https://github.com/gumstix/Gumstix-YoctoProject-Repo
I've also had good luck with this pattern for communicating with third
party builders.
Philip
>
> -KA
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
>
prev parent reply other threads:[~2014-03-07 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 23:25 using OE efficiently for development Nicolas Dechesne
2014-03-06 18:32 ` Cliff Brake
2014-03-07 8:38 ` Matthieu CRAPET
2014-03-07 15:08 ` Kevyn-Alexandre Paré
2014-03-07 17:19 ` Philip Balister [this message]
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=5319FF8F.3060608@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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