WHAT |
Option |
CMD & Description |
build |
-c build |
$ bitbake -c build [receipe] To clean a single package, type |
compile |
|
$ bitbake -c compile -f [receipe]
참고)git에서 source를 tmp에 받아두고 local에서 수정 후 build에도 유용 $ bitbake -c patch virtual/kernel $ bitbake -c compile -f virtual/kernel (option) $ bitbake -c install -f virtual/kernel (option) $ bitbake -c package -f virtual/kernel 출처: <http://forum.falinux.com/zbxe/?mid=lecture_tip&page=4&l=tr&document_srl=828316&m=1>
|
clean |
-c clean |
$ bitbake -c clean [receipe] To clean a single package, type |
debugging |
-vDDD
|
$ bitbake -vDDD world --debug Increase the debug level. You can specify this more than once. -D sets the debug level to 1, where only bb.debug(1, ...) messages are printed to stdout; -DD sets the debug level to 2, where both bb.debug(1, ...) and bb.debug(2, ...) messages are printed; etc. Without -D, no debug messages are printed. Note that -D only affects output to stdout. All debug messages are written to ${T}/log.do_taskname, regardless of the debug level. |
|
-s --show-version |
$ bitbake -s world --show-versions Show current and preferred versions of all recipes. |
변수 정보 |
-e |
$ bitbake -e emptytest > env.txt |
Debugging? |
|
$ bitbake -c devshell emptytest |
Image는 어디 있을까? |
$bitbake -e [receipe] | grep ^S=
$ bitbake -e linux-quic | grep "DEPLOY_DIR_IMAGE" |
$bitbake -e busybox | grep ^S= |
Log |
Where do I find build logs?
bitbake -e <recipename> | grep ^T=
출처: <https://wiki.yoctoproject.org/wiki/Technical_FAQ#Where_do_I_find_build_logs.3F>
|
|
Warning |
WARNING: /data001/kisoo.bang/work/01.src/PRJ/sources/meta-[PRJ]/recipes-kernel/linux/linux-imx_4.9.88.bb: Variable do_test_print contains tabs, please remove these (/data001/kisoo.bang/work/01.src/PRJ/sources/meta-[PRJ]/recipes-kernel/linux/linux-imx_4.9.88.bb) |
Tab을 없애야 함 |
'잘좀하자 개발 > Yocto' 카테고리의 다른 글
[AutoTool] Troubleshooting (0) | 2019.10.17 |
---|---|
[AutoTool] #2 Tutorial (0) | 2019.10.17 |
[AutoTool] #1 Install (0) | 2019.10.17 |
[BitBake] Tutorial (0) | 2019.03.12 |