Hello Pierre,
Monday, February 26, 2007, 10:07:38 PM, you wrote:
> Patrick,
> I need a way to rebuild efficiently Angstrom kernel and modules each
> time I try to change something (a frequency for example).
> For now, I am deleting stamps, but it is really not user friendly...
> Moreover, bitbake tries to download the kernel-of-the-day each day !!!
bitbake does what you tell it. If you say it to use floating date
for kernel, it will update (not download from scratch!) its internal
checkout each day, otherwise, no pulls will be made - bitbake caches
any version checked out in a tarball, and uses it afterwards.
But anyway, you're right that OE is not the most perfect fit for
*development*. It's a tool to build distributions. I personally
build development kernels outside OE, and just use them
with existing rootfs images. All in all, I may offer following tips
for comfortable development, based on my more than year long experience
and working on 3 ports in parallel:
1. Build kernels for interim testing in adhoc manner, not with OE. (Of
course, you need to build with OE for (sub)releases, to ensure
reproducibility).
2. Use static kernel - don't waste your time with modules. They are
*optional*. And having something as module is useful on devel stage
only if you want to debug that module specifically.
3. Use NFS - real life-saver.
YMMV ;-)
> Pierre
-- Best regards, Paul mailto:pmiscml_at_gmail.comReceived on Mon Feb 26 2007 - 15:39:13 EST
This archive was generated by hypermail 2.2.0 : Mon Feb 26 2007 - 15:40:11 EST