Forums

Hi,

I have successfully my build environment for pli3.0.


suppose I want to play around with sources in my tree and recompile without each time fetching updates from sources online, what is the best way to do so?

which files do I need to delete in order to run the "make" complete again?

Use bitbake to compile...

But if you really want to go developing on a certain program, you'd better clone the source repo of the program yourself, to another location on your harddisk, and work from there. The git checkouts that bitbake performs (by default) are not suitable for developing (the metadata is not fetched).

ok. thanks.

My goal is to understand how the build environment works. I have no experience in this and I'm also looking at the OE documentation regarding bitbake and recipes.

Suppose I want to play with some kernel settings (dm8000) and regenerate a new nfi, I can just edit the defconfig file in meta-openpli/recipes-linux/linux/linux-dreambox-3.2/dm8000 and run the bitbake task linux-dreambox-3.2.bb?

you'll have to increment the version (in this case: MACHINE_KERNEL_PR_append) as well, to force bitbake to rebuild it.

ok. thanks

without network I'm unable to "just compile"  using :

 

cd openpli-oe-core
MACHINE=dm8000 make image
(note that the build environment is complete as the same statements have downloaded and built the whole image fine while i was online)

 

 

On the other hand, when I want to update my build environment, while having internet, I start this command :

git clone git://openpli.git.sourceforge.net/gitroot/openpli/openpli-oe-core
cd openpli-oe-core
MACHINE=dm8000 make update
MACHINE=dm8000 make image
 

 

The git command updates the environment, but I still have the impression that not everything is rebuilded. Do I have to regenerate other things, like recipes, .... or delete binary files or even a whole directory?

 

Thanks.

bitbake -f -c compile xxxx

 

This forces a re-compile of a package xxxx.

 

bitbake -f -c compile linux-dreambox in a DMM OE will re-bild the kernel and produce a new vmlinux which you then can gzip and put to /boot for testing without the need for flashing an nfi.

Edited by gutemine, 29 March 2013 - 14:58.

you'll have to increment the version (in this case: MACHINE_KERNEL_PR_append) as well, to force bitbake to rebuild it.

with bitbake -f -c compile linux-vusolo2 I can force a recompile of the vusolo2 kernel. But is there a way to force rebuilding ipk files (for kernel modules) without incrementing MACHINE_KERNEL_PR_append? bitbake -f -c clean linux-vusolo2 doesn't seem to remove previously built ipk files, is there a "bitbake" way to remove them and rebuild them?
Edited by malakudi, 29 March 2013 - 19:15.

bitbake -f -c cleansstate

OK thanks. I'll try it out.