[yocto] do_compile() isn't run when building

Chris Tapp opensource at keylevel.com
Fri Feb 18 16:04:37 PST 2011


On 18 Feb 2011, at 09:42, Cui, Dexuan wrote:

> Chris Tapp wrote:
>> I've created a simple recipe based on an example from the Poky
>> Reference manual (I've added a license to get it to build):
> The code looks ok.
>
>> However, if I 'bitbake test' the code isn't compiled:
>>
>> NOTE: Running setscene task 178 of 276 (/home/chris/poky-dev/meta/
>> recipes-keylevel/test/test_0.1.0.bb:do_populate_sysroot_setscene)
>> NOTE: Running setscene task 179 of 276 (/home/chris/poky-dev/meta/
>> recipes-keylevel/test/test_0.1.0.bb:do_package_setscene)
>> NOTE: package test-0.1.0-r0: task do_populate_sysroot_setscene:
>> Started NOTE: package test-0.1.0-r0: task do_package_setscene:  
>> Started
>> NOTE: package test-0.1.0-r0: task do_populate_sysroot_setscene:
>> Succeeded
>> NOTE: Running setscene task 180 of 276 (/home/chris/poky-dev/meta/
>> recipes-keylevel/test/test_0.1.0.bb:do_populate_lic_setscene)
>> NOTE: package test-0.1.0-r0: task do_package_setscene: Succeeded
>> NOTE: package test-0.1.0-r0: task do_populate_lic_setscene: Started
>> NOTE: Running setscene task 181 of 276 (/home/chris/poky-dev/meta/
>> recipes-keylevel/test/test_0.1.0.bb:do_package_write_ipk_setscene)
>> NOTE: package test-0.1.0-r0: task do_populate_lic_setscene: Succeeded
>> NOTE: package test-0.1.0-r0: task do_package_write_ipk_setscene:
>> Started NOTE: package test-0.1.0-r0: task
>> do_package_write_ipk_setscene: Succeeded
>> NOTE: Executing RunQueue Tasks
>> NOTE: Running noexec task 828 of 829 (ID: 9,
>> /home/chris/poky-dev/meta/ recipes-keylevel/test/test_0.1.0.bb,
>> do_package_write)
>> NOTE: Running noexec task 829 of 829 (ID: 4,
>> /home/chris/poky-dev/meta/ recipes-keylevel/test/test_0.1.0.bb,
>> do_build)
>>
>>
>> Why doesn't the code get built?
> Is this the complete log?
> I don't find any tasks(e.g., do_fetch, do_unpack, do_install...)  
> that should be there. This is odd.

Yes, that's the complete log ! I thought it was odd too.

> Maybe you can try "bitbake -c cleanall test; bitbake test" to see if  
> any change?

That does work, but it seems as if 'make clean' quite often (though  
not always) doesn't do enough.

Chris




More information about the yocto mailing list