**** BEGIN LOGGING AT Sun Nov 11 02:59:57 2012 Nov 11 14:42:55 hi Nov 11 14:43:12 how do I add device nodes to the image these days? Nov 11 14:43:50 I've tried IMAGE_DEVICE_TABLES and _TABLE and adding /dev/... files to the package but nothing worked Nov 11 14:45:50 all I want is to have /dev/net/tun available immediately after the first boot Nov 11 15:01:59 hi Nov 11 16:36:15 I quite liked bitbake. I made a hello world project, defined base.bbclass, added fetch,unpack,patch,.....,install tasks and override them using another bbclass. I issued autotools.bbclass and made it print another string on do_make Nov 11 16:36:52 my question is that what does " do_task[foobar] = 'baz' " mean? Nov 11 16:37:20 I'm reading base.bbclass and I see: do_configure[dirs] = "${CCACHE_DIR} ${S} ${B}" Nov 11 16:37:29 as well as: do_configure[deptask] = "do_populate_sysroot" Nov 11 16:37:43 how does OE make use of these assignments, what do they mean? Nov 11 16:40:37 eren: that's the way varflags are set in the metadata Nov 11 16:40:58 certain varflags are read by bitbake Nov 11 16:41:12 others are read within the metadata Nov 11 16:42:12 getVarFlag and setVarFlag are used within python code to read and set them Nov 11 16:58:52 bluelightning: can you give an example code (metadata and its class maybe) ? Nov 11 16:58:59 why do we need varflags? Nov 11 16:59:54 they are particularly useful for flags on functions; e.g. noexec Nov 11 17:00:25 it seems that they set some variable within the context of task functions, ie do_configure Nov 11 17:01:28 so, when we are inside do_configure, we can get the variable using d.getVarFlags("DIRS") to access "${CCACHE_DIR} ${S} ${B}" in the example above Nov 11 17:02:29 no, it's not contextual Nov 11 17:02:37 (not in the way you describe anyway) Nov 11 17:02:38 of if the task is a shell function, ${@d.getVarFlags("DIRS")) ? Nov 11 17:03:11 just like the variables themselves the values of the varflags are accessible anywhere Nov 11 17:03:30 flags are just variables describing variables Nov 11 17:03:32 that's all Nov 11 17:04:32 kergoth: well, I haven't got the meaning of it Nov 11 17:04:52 as bluelightning says, they aren't contextual. they arent' variables to use from the task. they're variables used to *describe* the task Nov 11 17:05:04 e.g. they tell bitbake how to do things (what dirs to create/enter when starting a task, for 'dirs') Nov 11 17:05:27 or how to interpret the variable (e.g. the variable typing module's 'type' flag) Nov 11 17:05:41 kergoth: ok, so it's bitbake specific? Nov 11 17:05:44 huh? Nov 11 17:05:47 I mean Nov 11 17:05:49 let me explain :) Nov 11 17:05:52 everything in the metdata is bitbake specific, by definition Nov 11 17:05:56 they're bitbake files Nov 11 17:07:51 yeah right, I meant that it has a special meaning to bitbake before or after the task. You said that before bitbake starts a task, it creates/enters the "dirs". Similarly, when the task finishes, it removes the files specified in "do_unpack[cleandirs] = ${S}/patches" I guess Nov 11 17:08:04 is it right? Nov 11 17:09:55 yeah I see, bb/build.py: 152 Nov 11 17:11:20 ka6sox: de ta1aet, 73! Nov 11 17:13:55 kergoth: ok, so variable flags are not specific to functions or tasks. Any variable can have flags and it can be used arbitrarily in metadatas. However, there are some specific flags to tell bitbake what to do before entering/leaving a function or task (as we see in bb/build.py) Nov 11 17:19:04 bluelightning, the only sure way I know of killing the wikispam issue is to turn off account creation, then turn it on when someone asks... Nov 11 17:20:31 ka6sox: I think Richard has put something in place now, see his reply Nov 11 17:24:18 I did see that...but that is only a speedbump... Nov 11 17:24:48 perhaps wmat's solution will slow them down (but it will only slow them down..not stop it) Nov 11 17:25:25 the problem is that humans set up the accounts then turn them over to the bots. Nov 11 17:52:50 ka6sox-away: I think we're mostly seeing bot-created accounts at the moment Nov 11 23:14:50 I've built a kernel for my board (beaglebone) and am now trying to build a kernel module (using bitbake/setup-scripts), I'm trying to figure out how to call bitbake to build the thing can anyone point me in the right direction? Nov 11 23:15:39 I've found this http://www.kunen.org/uC/beagle/oe_kmod.html on how to write the bitbake recipe, but I'm not sure how to actually run the thing. Nov 11 23:28:51 Maybe I should back up. I know it's just bitbake to run it, but at the bottom of the post I linked above he says to untar his example "somewhere where OE knows where it is" -- I guess this is what confuses me. setup-scripts builds a massive directory tree and I'm not sure where I can add custom modules... Nov 12 02:03:36 finalyl **** ENDING LOGGING AT Mon Nov 12 02:59:58 2012