**** BEGIN LOGGING AT Wed Sep 30 02:59:59 2015 Sep 30 07:07:01 whats the recommended way of applying a patch series using bitbake? like, i have an existing "series"-file and a large number of patches. do i have to convert the series file into a SRC_URI list in the same order? Sep 30 07:08:56 morning bluelightning Sep 30 07:14:04 morning mago__, all Sep 30 07:14:32 mago__: I'm afraid so yes... you may consider using a git branch instead though Sep 30 07:20:02 bluelightning: a git branch? Sep 30 07:20:47 good morning Sep 30 07:20:50 mago__: yes, as in commit the code to git, apply the patches and then push to a repo somewhere Sep 30 07:20:53 morning mckoan Sep 30 08:10:35 do you know an alternative to rdesktop working with Qt5 (no X11)? Sep 30 08:20:34 mckoan: not qt5, but there's the -a bit buggy- pure-wayland "wlfreerdp" client in freerdp Sep 30 08:20:47 not sure oe builds it, though, need to check Sep 30 08:22:55 Tarnyko: thank you, I suspected it was a mess Sep 30 08:23:21 mckoan: you're welcome. There's also a framebuffer one in freerdp, worst case... Sep 30 08:29:28 Tarnyko: I'll take a look at meta-openembedded/meta-oe/recipes-support/nonworking/freerdp/freerdp_git.bb Sep 30 08:29:38 Tarnyko: thanks Sep 30 11:21:51 i'm writing a recipe to build our documentation. The docs should be built and deployed to ${DEPLOY_DIR}/doc (i.e, it's machine-independent). It should not end up in the rootfs of target. What would be the best way to approach this? Create a native recipe that DEPENDS on the required tools and then hardcode the path ${DEPLOY_DIR}/docs in my do_install() task? How does the Yocto project generate its docs? Is it Sep 30 11:21:53 recipe-based, or generated totally separated from the buildtree? Sep 30 11:41:39 completely separate in our case Sep 30 11:41:56 I would imagine a native recipe would be the way to do it though yes Sep 30 11:42:22 also you shouldn't be installing anything during do_install to anywhere other than ${D} Sep 30 11:42:53 if you want to put things in ${DEPLOY_DIR} then create a do_deploy task, optionally using the deploy class Sep 30 19:09:59 kergoth: regarding our recent automount discussion -- Khem found this -- works pretty well: https://github.com/LemonBoy/ldm Sep 30 19:10:58 what is the best way to modify busybox config? is bbappend with config fragment, or is there something easier? Sep 30 19:11:49 i think bbappend with fragment is probably easiest, you can use diffconfig to generate the fragment from menuconfig, which is nice Sep 30 19:12:29 if you want, you should be able to use use recipetool's appendsrcfile command to add the fragment Sep 30 19:12:34 or if you need to script it Sep 30 19:12:49 mel's kernel_add_fragment command uses appendsrcfile under the hood Sep 30 19:13:19 er, kernel_add_fragments Sep 30 19:15:36 hmm, could be interesting to add a little command or script which just does menuconfig -> diffconfig -> appendsrcfile with the fragment as a convenience Sep 30 19:18:15 * cbrake tries recipetool for the first time .. Sep 30 19:32:44 I wish it would insert more elements to help keep variables in order :) Sep 30 19:44:54 kergoth: diffconfig/recipetool was so cool I had to blog about it: http://bec-systems.com/site/1145/modifying-the-busybox-config-in-openembedded Sep 30 19:45:41 nice Sep 30 19:45:55 glad it worked out for you Sep 30 19:46:41 -w would have simplified the append slightly (would avoid the subdir= on the SRC_URI, since it'd install it to workdir instead of the source tree Sep 30 19:47:04 probably doens't matter for a fragment though, should be used regardless Sep 30 19:47:52 you can also use appendsrcfile to override existing files from SRC_URI, like file://defconfig, though fragments are usually a better choice for that particular case Sep 30 19:55:31 thanks, added to the notes **** ENDING LOGGING AT Thu Oct 01 02:59:58 2015