All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: jags gediya <jags.gediya@gmail.com>,
	 "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Building own kernel instead of taking from git
Date: Mon, 08 Sep 2014 07:25:01 +0200	[thread overview]
Message-ID: <540D3DAD.1000304@gmail.com> (raw)
In-Reply-To: <CAP3RZogHv9R=+fG_e3xHeZ-L2WJgWwGMRAqi3UaBYh_dWYsDgg@mail.gmail.com>

Am 08.09.2014 06:21, schrieb jags gediya:
> I want to build my kernel source code in yocto. For that i have
> modified the required linux-imx.inc file.
> 
> Inside that i have given kernel source directory in SRC_URI and S variable.
> 
> Is this approach fine, or is there any better solution i can get?
> 
I would always create my own layer and add a .bbappend for the
kernel-recipe I want to modify. There you could of course change the
SRC_URI and S variable but you could also provide your changes to
linux-imx.inc as a patch.

Then you could manage your changes to this layer via git. And you don't
lose the opportunity to pull changes from the remote repositories
without destroying your own changes.


WARNING: multiple messages have this Message-ID (diff)
From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: jags gediya <jags.gediya@gmail.com>,
	 "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [yocto] Building own kernel instead of taking from git
Date: Mon, 08 Sep 2014 07:25:01 +0200	[thread overview]
Message-ID: <540D3DAD.1000304@gmail.com> (raw)
In-Reply-To: <CAP3RZogHv9R=+fG_e3xHeZ-L2WJgWwGMRAqi3UaBYh_dWYsDgg@mail.gmail.com>

Am 08.09.2014 06:21, schrieb jags gediya:
> I want to build my kernel source code in yocto. For that i have
> modified the required linux-imx.inc file.
> 
> Inside that i have given kernel source directory in SRC_URI and S variable.
> 
> Is this approach fine, or is there any better solution i can get?
> 
I would always create my own layer and add a .bbappend for the
kernel-recipe I want to modify. There you could of course change the
SRC_URI and S variable but you could also provide your changes to
linux-imx.inc as a patch.

Then you could manage your changes to this layer via git. And you don't
lose the opportunity to pull changes from the remote repositories
without destroying your own changes.


  reply	other threads:[~2014-09-08  5:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08  4:21 Building own kernel instead of taking from git jags gediya
2014-09-08  5:25 ` Sven Ebenfeld [this message]
2014-09-08  5:25   ` [yocto] " Sven Ebenfeld
2014-09-08  9:37 ` Richard Leitner

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=540D3DAD.1000304@gmail.com \
    --to=sven.ebenfeld@gmail.com \
    --cc=jags.gediya@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --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.