From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Rohit2 Jindal <rohit2.jindal@aricent.com>
Cc: yocto@yoctoproject.org
Subject: Re: Recompile the recipe everytime
Date: Fri, 14 Jun 2013 13:30:20 +0100 [thread overview]
Message-ID: <14746932.1IgOpEMSZM@helios> (raw)
In-Reply-To: <17797116383D4341B029FDF34C22BF6A52C4CCB36E@GUREXMB01.ASIAN.AD.ARICENT.COM>
Hi Rohit,
On Thursday 13 June 2013 20:54:08 Rohit2 Jindal wrote:
> Please help me out I am stuck in some issue, actually I want my recipe to do
> compilation everytime on every run of
>
> Bitbake linux-yocto
>
> ie can I remove stamping or sstate-cache that it allows me to run
> compilation everytime on every run of bitbake linux-yocto.
>
>
> I tried do_compile[nostamp] ="1" but it did not work but same thing worked
> for do_install[nostamp]="1"
If you really want to do this, I think you'll need to mark all tasks in the
normal flow from do_compile onwards as nostamp i.e.:
do_compile
do_compile_kernelmodules
do_kernel_link_vmlinux
do_install
do_package
do_packagedata
do_package_write
do_package_write_rpm
do_populate_sysroot
do_strip
do_deploy
do_uboot_mkimage
do_sizecheck
I have to say I don't recommend doing this. I would strongly suggest you use
"bitbake -c compile -f linux-yocto" or "bitbake -C compile linux-yocto" (the
latter will force compile and then automatically run all the needed tasks up
to the default task).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-06-14 12:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11.1371063601.16784.yocto@yoctoproject.org>
2013-06-13 15:24 ` Recompile the recipe everytime Rohit2 Jindal
2013-06-14 12:30 ` Paul Eggleton [this message]
2013-06-14 12:35 ` Paul Eggleton
2013-06-14 16:38 ` Richard Purdie
2013-06-19 9:51 ` Yocto root permission issue Rohit2 Jindal
2013-06-19 10:05 ` Paul Barker
2013-06-10 14:50 menuconfig not working in FEDORA18 Rohit2 Jindal
[not found] ` <51B5EA46.8040609@linux.intel.com>
[not found] ` <17797116383D4341B029FDF34C22BF6A52C4CCADBD@GUREXMB01.ASIAN.AD.ARICENT.COM>
[not found] ` <51B5EEC6.4040007@linux.intel.com>
[not found] ` <17797116383D4341B029FDF34C22BF6A52C4CCADC1@GUREXMB01.ASIAN.AD.ARICENT.COM>
[not found] ` <51B639AC.3050200@linux.intel.com>
2013-06-12 13:15 ` Recompile the recipe everytime Rohit2 Jindal
2013-06-12 14:30 ` Paul Barker
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=14746932.1IgOpEMSZM@helios \
--to=paul.eggleton@linux.intel.com \
--cc=rohit2.jindal@aricent.com \
--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.