From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: What builds 'netbase'?
Date: Sun, 20 Feb 2011 08:51:47 -0600 [thread overview]
Message-ID: <4D612A83.7040302@windriver.com> (raw)
In-Reply-To: <466E08F0-1ADF-4618-A7DA-B6390C7AC2A9@keylevel.com>
On 2/19/11 8:58 AM, Chris Tapp wrote:
> I want to make some changes to /etc/interfaces.
>
> It looks to me as if this this comes from 'netbase', but what do I
> need to rebuild to get my changes in to the rootfs? i.e. is there
> something I can
>
> bitbake -c clean ???; bitbake ???
>
> to get my changes in to the rootfs image?
>
> I tried cleaning 'netbase', but that made no difference when I then
> 'bitbake poky-image-minimal'.
If you already have a built copy of netbase in your sstate-cache, all clean will
do is remove the built version, and resync from the cache. (bitbake -c cleanall
will remove the sstate-cache files as well, forcing a complete rebuild from
fetch down to packaging...)
To avoid this, the best way (after changing the netbase) is to adjust the PR
within the recipe.
My suggestion is if the PR is "12", change it to "12.1" on your first
modification, "12.2" on your second, etc..
--Mark
> Chris Tapp
>
> opensource@keylevel.com
> www.keylevel.com
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-02-20 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 14:58 What builds 'netbase'? Chris Tapp
2011-02-19 16:16 ` Gary Thomas
2011-02-19 21:39 ` Chris Tapp
2011-02-21 2:25 ` Tian, Kevin
2011-02-20 14:51 ` Mark Hatle [this message]
2011-02-20 15:31 ` Chris Tapp
2011-02-20 15:37 ` Mark Hatle
2011-02-20 15:50 ` Chris Tapp
2011-02-20 17:46 ` Mark Hatle
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=4D612A83.7040302@windriver.com \
--to=mark.hatle@windriver.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.