From: John Weber <rjohnweber@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: making building master-next just a little bit easier
Date: Tue, 27 Aug 2013 13:52:25 -0500 [thread overview]
Message-ID: <521CF569.2060803@gmail.com> (raw)
In-Reply-To: <521CE7B2.9030607@boundarydevices.com>
On 8/27/13 12:53 PM, Eric Nelson wrote:
> Thanks Christian,
>
> On 08/27/2013 10:36 AM, Christian Betz wrote:
>> hi everyone.
>>
>> i've cloned fsl-community-bsp-platform and created a master-next
>> branch with the correct repo XML file to use master-next branch for
>> all the meta-fsl-* repos and master for the rest. this makes building
>> and testing master-next from scratch a bit easier.
>>
>> this was pretty trivial to do but I wanted to mention it to the list.
>> i'd be happy to submit "official" patches to the list for these
>> changes if desired.
>>
>
> +1
>
> This is useful.
Agreed, and I'm sure Otavio would love some patches to review. Glad to see that
it does not checkout master-next from Poky or OE.
>
>> so instead of the normal dylan build:
>>
>> repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan
>>
>> I do this to build master-next using the repo XML on my cloned github repo:
>>
>> repo init -u https://github.com/cbetz421/fsl-community-bsp-platform -b
>> master-next
>>
>> NOTE: I also updated the README in my master-next branch (but I
>> suggest that the README in master also should be updated to replace
>> "-b dylan" with "-b master").
>>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
next prev parent reply other threads:[~2013-08-27 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 17:36 making building master-next just a little bit easier Christian Betz
2013-08-27 17:53 ` Eric Nelson
2013-08-27 18:52 ` John Weber [this message]
2013-08-29 20:03 ` Otavio Salvador
2013-08-30 6:48 ` Christian Betz
2013-08-30 14:23 ` Daiane Angolini
2013-08-30 18:58 ` Christian Betz
2013-08-30 19:35 ` Daiane Angolini
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=521CF569.2060803@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@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.