Bitbake cheat sheet: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 1: | Line 1: | ||
==Intention== | ==Intention== | ||
This page is intended to make the live of new developers easier. Feel free to add all your usual bitbake commands to this page | This page is intended to make the live of new developers easier. Feel free to add all your usual bitbake commands to this page | ||
==Start a build== | |||
To get a package build just type | |||
bitbake foo | |||
where foo is the name of the package without any extension or version number. | |||
==Clean up== | |||
bitbake -c clean foo | |||
This command will clean up your tmp dir for the given package. It is very useful if you work on a new .bb recipe. Without it your changes to the recipe may not work. | |||
==Working with tmp/work== | ==Working with tmp/work== | ||
A thing you usually do not want to miss is to be able to recompile your source code if you change a line in it. | A thing you usually do not want to miss is to be able to recompile your source code if you change a line in it. |
Revision as of 17:44, 19 September 2008
Intention
This page is intended to make the live of new developers easier. Feel free to add all your usual bitbake commands to this page
Start a build
To get a package build just type
bitbake foo
where foo is the name of the package without any extension or version number.
Clean up
bitbake -c clean foo
This command will clean up your tmp dir for the given package. It is very useful if you work on a new .bb recipe. Without it your changes to the recipe may not work.
Working with tmp/work
A thing you usually do not want to miss is to be able to recompile your source code if you change a line in it.
bitbake -f -c compile foo
will only recompile your source nothing else after that do a
bitbake foo
to get a new package