Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: How to rebuilt the package after modified the source code in open embedded bitbake ...
Date: Wed, 04 Apr 2012 12:31:06 +0100	[thread overview]
Message-ID: <1333539066.11559.36.camel@ted> (raw)
In-Reply-To: <20120404094728.01c3ba51@eb-e6520>

On Wed, 2012-04-04 at 09:47 +0200, Eric Bénard wrote:
> Le Wed, 4 Apr 2012 09:21:02 +0200,
> Samuel Stirtzel <s.stirtzel@googlemail.com> a écrit :
> 
> > 2012/4/4 Eric Bénard <eric@eukrea.com>:
> > > Hi Surenda,
> > >
> > > Le Wed, 4 Apr 2012 06:34:39 +0000 (UTC),
> > > surendra dhobale <surendra.dhobalelinux@gmail.com> a écrit :
> > >>  I am working with the open embedded environment.
> > >>
> > >> I have added one u-boot package in that. First time by default the compilation
> > >> done successfully using the bitbake. But Now i made some changes in the source
> > >> .
> > >>
> > >> Now i have to built the same package with neglecting the fetch() stage.
> > >> and rebuilt it means need to compilation.
> > >>
> > >> Is any commands for that...
> > >> Can please anyone explain me in deatails about that. I am newbie in the open
> > >> embedded.
> > >>
> > > bitbake u-boot -c cleansstate
> > > bitbake u-boot
> > >
> > > Eric
> > 
> > Hi,
> > please note this will delete local changes (in thework directory) to
> > the sourcecode!
> > 
> > If you only want to compile again you can use
> > 
> > bitbake -c compile -f u-boot
> > and then "bitbake u-boot" to build the other tasks.

There is some documentation in the manual about this:
http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#platdev-appdev-insitu

> oops, I read his message to fast and didn't notice the "i made some
> changes in the source code , which is created in the Temp work
> directory".
> 
> For this kind of work, I prefer to do :
> bitbake u-boot -c configure
> copy the source from workdir to a directory outside OE
> then change to this dir and
> git init
> git add .
> git commit -m init
> then you can hack it outside OE (and compile it using a meta-toolchain
> for example)
> and in the end you can easily produce a patch using git that you
> integrate back into OE.

Eric: You should probably look at the externalsrc.bbclass since it gives
you a way to do things like this yet also build and package it with the
usual build system:

http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#ref-classes-externalsrc

Cheers,

Richard




  reply	other threads:[~2012-04-04 11:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04  6:34 How to rebuilt the package after modified the source code in open embedded bitbake surendra dhobale
2012-04-04  7:18 ` Eric Bénard
2012-04-04  7:21   ` Samuel Stirtzel
2012-04-04  7:47     ` Eric Bénard
2012-04-04 11:31       ` Richard Purdie [this message]
2012-04-04 11:37         ` Eric Bénard
2012-04-06  7:31           ` surendra dhobale

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=1333539066.11559.36.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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