Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lauri Hintsala <lauri.hintsala@bluegiga.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: after modifying source code in work/, how to rebuild package?
Date: Fri, 16 Dec 2011 10:13:30 +0200	[thread overview]
Message-ID: <4EEAFDAA.7000100@bluegiga.com> (raw)
In-Reply-To: <4EEAFD28.1060609@bluegiga.com>

Sorry, this workflow will clean all your changes. How about that:

bitbake projectname -c compile -f
bitbake projectname

Lauri

On 12/16/2011 10:11 AM, Lauri Hintsala wrote:
> bitbake projectname -c cleanall
> bitbake projectname
>
> Cleanall command will clean the workdir and sstatefiles from sstate folder.
>
> BR,
> Lauri Hintsala
>
>
> On 12/16/2011 09:55 AM, Leon Woestenberg wrote:
>> Hello all,
>>
>>
>> after modifying source code in the work directory, what is the set of
>> commands to rebuild the package (from the compile stage and further)?
>>
>> Under classic OpenEmbedded, I removed the compile, install, package
>> stages stamp files and ran bitbake. However, shared staging "broke" that
>> workflow.
>>
>> Is there an equivalent approach with OpenEmbedded Core? Possibly
>> disabling 'sstage' on a per build, or per package basis?
>>
>>
>> Thanks,
>>
>> Leon.
>>
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



  reply	other threads:[~2011-12-16  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  7:55 after modifying source code in work/, how to rebuild package? Leon Woestenberg
2011-12-16  8:11 ` Lauri Hintsala
2011-12-16  8:13   ` Lauri Hintsala [this message]
2011-12-16  8:14     ` Luo Zhenhua-B19537
2011-12-16 22:54     ` Leon Woestenberg
2011-12-16 17:37 ` Henning Heinold

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=4EEAFDAA.7000100@bluegiga.com \
    --to=lauri.hintsala@bluegiga.com \
    --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