**** BEGIN LOGGING AT Tue Mar 08 02:59:59 2016 Mar 08 12:43:22 Come one, come all! http://openembedded.org/wiki/OEDAM_2016 Mar 08 13:01:26 Crofton|work: hear me, hear me! Mar 08 14:06:21 Hi, I've made a genericx86 system image with yocto kernel. System is bootable from pendrive. Kernel boots then gave to systemd control. Everything is ok but i didn't se getty on screen. I don't have graphical target and xserver. I want only to boot to getty? How to do that? Mar 08 14:07:29 On my pc LCD i see only some dmesg messages and some messages from systemd, but it looks like stderr not stdout. For example i see errors but i didn't see systemd services messages and status [OK]. Mar 08 14:12:20 Any idea? Mar 08 15:02:55 http://pastebin.com/L5Vh9XFV Mar 08 15:03:06 with DISTRO_FEATURES = "" in distro.conf Mar 08 15:03:12 any idea what triggers this? Mar 08 15:12:45 you've actually set DISTRO_FEATURES to ""? Mar 08 15:18:23 well, I did in distro.conf Mar 08 15:18:35 trying to get a minimal set of features Mar 08 15:18:46 that still left me with some :) Mar 08 15:28:45 yeah, that is a crappy approach :) Mar 08 15:47:41 Crofton|work: I have a really experimental class which disables all packageconfigs which pull in extra deps by default, regardless of the recipe's default :) Mar 08 15:48:07 I think that _remove a few features gets things sane Mar 08 15:49:14 I need to make a smallish image and I figured I'd take a little tim eto see what happens we you do silly thing Mar 08 16:01:40 in a recipe that BBCLASSEXTENDs native (ie provides both target and native versions), is it possible to "addtask" only for the native version or is such requirement an indicator that I should split the recipe into two separate bb-files? Mar 08 16:02:09 (specifically, i'd like for the -native version to run do_deploy after do_compile, this should not happen in the target-version) Mar 08 16:05:03 using deploy in a native sounds like it's already wrong Mar 08 16:05:18 but beyond that, addtask can't be done separately using the normal command, but you could use the addtask method from anonymous python conditionally Mar 08 16:13:25 epic: https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomment-193772935 Mar 08 16:19:27 If I export a variable defined in my image, shouldn't it be be defined globally? Or vice versa, have some internal variables to a recipe that end-users can overload similar to how the local.conf can have things like MACHINE ??= "qemuarm"? Mar 08 16:25:59 kergoth: i'd like to deploy a tool that should go along with our images (it's a tool to flash the images onto a device). So i've written a recipe for it. Where would you put such deployment code if not into -native recipe? Mar 08 16:27:03 eengie: no, configuration metadata is global and flows into recipes, recipes cannot affect the config metadata or other recipes metadata Mar 08 16:27:55 So could I define a variable in a recipe for example: MY_VAR ??="somedefault" and allow the user to change that value using either their local.conf or my own image definition? Mar 08 16:28:19 again, a recipe cannot affect config metadata Mar 08 16:28:20 period Mar 08 16:28:48 if that recipe is the only recipe to use that value, then yes, that would do the job. if the image needs it, no, that's not going to work, because again, one recipe can't get to a variable in another recipe Mar 08 16:29:19 I'm not sure I understand how that would be affecting metadata since it would be inheriting the upstream defined value like MACHINE, etc. Right? Mar 08 16:29:28 Oh, I understand your point now. Mar 08 16:29:49 it depends on whether that recipe is the only user of your default value. if you put that default in every recipe that needs it, sure Mar 08 16:31:22 Hmm...maybe the better way to do this would be to have a default in an include file that gets imported when necessary. This is the only recipe requiring the variable(s) I'm thinking about, but I can see how doing it this way might lead users to the wrong impression (that they could add their own recipe to read that variable, as modified by the recipe) Mar 08 16:32:05 as with everything else in the proejct, there are always many ways to do things, figuring out which is cleanest is always the challenge, and the answer is it always depends :) Mar 08 16:33:49 kergoth: Thanks, by the way for clarifying. And yes, indeed. What I'm trying to setup is a way for a recipe to know which other layer-specific recipes it should be depending against. So in someone's local.conf, they specify SOME_VAR="apples oranges" and in this recipe, DEPENDS = " ${SOME_VAR}", and then down in the remaining parts of the recipe it behaves like those things did already get installed. Mar 08 16:34:17 Because how it is built will vary based on other installed items Mar 08 16:38:50 TAKE ONE BUILD SYSTEM INTO THE SHOWER? Mar 08 16:39:00 * rburton gasps at waf needing distutils to work Mar 08 16:39:47 * rburton steps slowly away Mar 08 18:23:44 hi everyone, i want to install tomcat7 but i know oe has recipes tomcat5.5 and 4.1 so which i install jsp2.0 or servlet api, when i use archarmlinux, i said pacman -S tomcat7 but i don't know it is servlet api or server page ? **** ENDING LOGGING AT Wed Mar 09 02:59:58 2016