**** BEGIN LOGGING AT Mon Jul 20 02:59:58 2015 Jul 20 15:14:03 Hello world Jul 20 15:14:11 * pompomJuice waves Jul 20 15:14:43 * Crofton waves back Jul 20 17:56:42 which task gets called both when building from scratch and when re-running from sstate? deploy? package? Jul 20 17:57:23 that question doesn't really make sense Jul 20 17:57:33 first, sstate is done per-task, it's not recipe-wide Jul 20 17:57:52 so 're-running from sstate' isn't a yes or no for a recipe, it's yes or no for each sstate covered task within a recipe Jul 20 17:57:52 okay, let me rephrase Jul 20 18:00:07 if i have no sstate and no tmp my image is created fine. if i delete tmp and re-bitbake my image, i get failures because various special "cp" and "ln -s" things aren't run which setup ${DEPLOY_DIR_IMAGE} as required Jul 20 18:00:31 insufficient information to diagnose Jul 20 18:00:48 you'll need to determine exactly what wasn't run that should have been run Jul 20 18:03:02 http://pastebin.com/ABwcYMhc Jul 20 18:03:08 here's my recipe ^^ Jul 20 18:03:20 the "cp ../initrd.img ${DEPLOY_DIR_IMAGE} Jul 20 18:03:38 doesn't get run when tmp is missing but sstate exists Jul 20 18:04:24 so my guess is that there's some task that I need to define to move the "cp ..." line into Jul 20 18:05:07 that will get run both when (tmp and sstate are missing) and (when tmp is missing and sstate exists) Jul 20 18:13:06 uh, compile obviously isn't run when sstate is used Jul 20 18:13:15 that'd defeat the entire purpose of sstate, which is to avoid compiling crap we don't need to Jul 20 18:13:23 if you want to deploy, then create and use a deploy task Jul 20 18:13:27 there's a bbclass for it Jul 20 18:14:18 do_compile is for compilation, don't ever use it for anything else :) Jul 20 18:16:25 ah, i was probably missing the bbclass. i had created a do_deploy but bitbake kept telling me there was no such task Jul 20 18:16:50 ERROR: Task do_deploy does not exist for target firefly-emmc-initramfs-image Jul 20 18:16:54 deploy.bbclass just sets up the sstate bits for that Jul 20 18:17:03 great. thanks :-) Jul 20 18:17:38 addtask deploy before do_build after do_compile or addtask deploy before do_build after do_install are both common Jul 20 18:17:54 also, in your do_deploy, write to ${DEPLOYDIR} Jul 20 18:18:09 that'll be captured by the do_deploy sstate and put in the proper place Jul 20 18:18:23 grep the metadata for 'addtask deploy' or 'do_deploy' for examples Jul 20 18:19:10 ok, i actually saw some places where they did "addtask deploy before do_build..." but that seemed strange to me Jul 20 18:19:20 build isn't a synonym for compile? Jul 20 18:19:28 deploy before compile? Jul 20 18:27:46 no Jul 20 18:27:58 build is the default task when you don't specify a task Jul 20 18:28:19 it ensures tha tyour deploy task will automaitcally run Jul 20 18:28:29 without badly affecting the dependency graph Jul 20 18:28:43 e.g. putting it before do_package would cause package to rerun when you change deploy, which wouldn't make sense, its output isn't used by package Jul 20 19:21:10 kergoth: awesome thank you! my recipes work great in both situations [(missing tmp and sstate) and (existing sstate but missing tmp)] Jul 20 19:21:19 np Jul 20 20:01:46 has anyone fixed valgrind in fido for kernel 4.x? master is OK Jul 20 20:01:51 I know dizzy is broken Jul 20 20:05:06 fido looks OK :) Jul 20 21:04:59 anyone experienced with uclibc around to help me get a script that supports compiling with glibc and musl compiling with uclibc as well? Jul 20 21:06:45 not sure if that falls under "ditro support". my main goal right now is making a crosstool chain that responds well/easily to various libc **** ENDING LOGGING AT Tue Jul 21 02:59:58 2015