From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Making machine config a build dependency for core-image recipes
Date: Wed, 18 Jan 2012 15:20:22 -0700 [thread overview]
Message-ID: <4F1745A6.3050502@mlbassoc.com> (raw)
In-Reply-To: <02E7334B1630744CBDC55DA8586225831FAEC2@ORSMSX102.amr.corp.intel.com>
On 2012-01-18 15:04, Yang, Fei wrote:
> I encountered a build issue when trying to generate /etc/inittab.
> I have a meta-xxx/conf/machine/conf file which contains serial console information such as SERIAL_CONSOLE = "115200 ttyXYZ" or "115200 ttyS0" by default.
> When I update that conf file and make an incremental build, the /etc/inittab doesn't get updated, I finally have to remove all the binaries and force a complete re-build to generate correct /etc/inittab with updated serial console settings, which take more than an hour to finish.
> How do I create a dependency so that when I update my machine/conf file, an incremental build would take care of the change and re-generate the files in root FS accordingly? If that is impossible for now, can I just delete one or a few task binaries to trigger a rebuild on /etc/inittab? This would greatly reduce my build time.
You really only need to rebuild the sysvinit package.
% ... make your modifications to machine/conf
% bitbake sysvinit -c cleansstate
% bitbake <whatever-image-you-like>
This package is not marked as machine dependent via
PACKAGE_ARCH = "${MACHINE_ARCH}"
perhaps it should be since /etc/inittab is target dependent?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-01-18 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 22:04 Making machine config a build dependency for core-image recipes Yang, Fei
2012-01-18 22:20 ` Gary Thomas [this message]
2012-01-18 23:50 ` Yang, Fei
2012-01-19 0:03 ` Gary Thomas
2012-01-19 4:06 ` McClintock Matthew-B29882
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=4F1745A6.3050502@mlbassoc.com \
--to=gary@mlbassoc.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.