**** BEGIN LOGGING AT Wed Jul 15 02:59:58 2015 Jul 15 06:59:11 good morning Jul 15 07:18:14 hi mckoan Jul 15 14:43:22 Hello. Is there any example on how to use wic to populate a partition with arbitrary files? Jul 15 14:44:21 By "arbitrary" I mean I'll specify which files should be added to the file system. Jul 15 14:49:15 mario-goulart: the simplest way to do that would be to create an image with the desired contents Jul 15 14:51:19 bluelightning: the case I have is an installer image. I'd like to add the files to be installed (kernel, bootloader, rootfs etc.) to a different partition. Jul 15 14:53:34 The installer will write to NAND (ubi image). Jul 15 15:23:41 what is required to get the build to make a symlink to an artifact in tmp/deploy/images/? how can i choose the symlink name? Jul 15 15:27:11 that depends entirely on what you're looking to link Jul 15 15:31:13 i've created my own image class, firefly-update-img.bbclass, which is added to IMAGE_FSTYPES and generates a (e.g.) tmp/deploy/images/firefly/firefly-update-image-firefly-20150715142604.update.img Jul 15 15:31:44 i would like to have a symlink in tmp/deploy/images/firefly named update.img that points to this artifact Jul 15 15:31:58 (or whatever the latest is) Jul 15 15:45:10 ...or i could just add the necessary "ln -s ..." command in my class Jul 15 15:47:20 sounds about right Jul 15 15:49:21 :-) Jul 15 15:50:56 convenience links like that are handy Jul 15 17:40:49 Can somebody explain to me why we're poisoning sysroots instead of fixing the sysroot autodetection that already exists in gcc? Because I posted patches for the latter last year, and given those, I can't think of any good reason why sysroot poisoning is necessary, unless we want to make SDK users' lives more difficult Jul 15 17:42:28 (patch in question: http://article.gmane.org/gmane.comp.handhelds.openembedded.core/52754) Jul 16 01:28:47 is there something that is actively not allowing me to specify my PREFERRED_PROVIDER_virtual/kernel in an image definition .bb file? Jul 16 02:28:41 tlwoerner: yes, that variable controls scheduling, which is done up front using the configuration metadata. defining it in a random recipe will do nothing Jul 16 02:29:06 and what would that even do? you can't change what kernel is used based on what image you build, because you can build any number of images at once **** ENDING LOGGING AT Thu Jul 16 02:59:59 2015