Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jian Liu <jian.liu@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] archiver.bbclass: do checkout for kernel
Date: Thu, 5 Nov 2015 10:14:08 +0800	[thread overview]
Message-ID: <563ABB70.8060400@windriver.com> (raw)
In-Reply-To: <6A9FCF09-82E7-4A16-AEDD-D081F67704E7@gmail.com>

Hi,

All kernels I list bellow will perform do_fetch(), do_unpack(), 
do_kernel_checkout().
do_unpack() will put a bare git repo under WORKDIR and then 
do_kernel_checkout()
will move the bare repo to bitbake/tmp/work-share/<board 
name>/kernel-source(value of variable S),
then performing "git checkout".

So do_ar_original must wait until do_kernel_checkout() is completed and 
then make tarball using the code under S.
Do I make that clear?


You refer to kernels other than linux-yocto. Can you give me an example?
I do not know how to build such kernel.

Thanks!
Jian

On 2015年11月04日 13:57, Khem Raj wrote:
>> On Nov 3, 2015, at 1:22 AM, Jian Liu<jian.liu@windriver.com>  wrote:
>> >
>> >Hi,
>> >
>> >I test linux-dummy linux-yocto-dev linux-yocto-rt linux-yocto-tiny and the result is as follows,
>> >
>> >linux-dummy: this package just meets some dependency and there is no source code for it.
>> >                      The patch does not impact it
>> >linux-yocto, linux-yocto-dev, linux-yocto-rt, linux-yocto-tiny: The S variable of all packages is set to STAGING_KERNEK_DIR.
>> >                       do_fetch and do_unpack just leave a bare git repo of kernel and do_kernel_checkout gets the source code
>> >
> does it cover the case when kernel is not linux-yocto was basic question, I am not clear if thats covered in any of above
>
>> >Thanks!



  reply	other threads:[~2015-11-05  2:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02  6:23 [PATCH] archiver.bbclass: do checkout for kernel Jian Liu
2015-11-02 21:30 ` Khem Raj
2015-11-03  9:22   ` Jian Liu
2015-11-04  5:57     ` Khem Raj
2015-11-05  2:14       ` Jian Liu [this message]
2015-11-05  2:22         ` Khem Raj
2015-11-13  8:16           ` Jian Liu
2015-12-14  5:37             ` Jian Liu
2015-12-16 22:29 ` Burton, Ross
2015-12-18  3:31   ` Jian Liu

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=563ABB70.8060400@windriver.com \
    --to=jian.liu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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