**** BEGIN LOGGING AT Thu Jun 06 03:00:22 2013 Jun 06 08:07:49 morning all Jun 06 08:52:19 morning Jun 06 10:13:44 Hi guy. I'm willing to write a recipe for glmark2 https://launchpad.net/glmark2. Which Yocto repository would you put it in? Jun 06 10:13:54 poky-contrib? Jun 06 11:06:48 panda84kde: I would think that's appropriate for meta-oe; there's even a recipes-benchmark directory Jun 06 11:12:25 bluelightning: thanks Jun 06 12:38:14 When trying to build core-image-x11 i get "Nothing PROVIDES 'mesa-dsi-driver-swrast' .. " Jun 06 12:38:18 how can i fix this Jun 06 12:38:27 dsi or dri? Jun 06 12:38:54 it is dri Jun 06 12:38:57 sorry for the typo Jun 06 12:39:33 it's provided by mesa recipe, do you have some mesa bbappend or something like that? Jun 06 12:42:20 it worked fine with poky-8.0. now I upgraded to the master and i get this error Jun 06 12:43:02 that doesn't answer my question.. Jun 06 12:51:49 daiane_: panda84kde is Diego (who is working in GPU stuff with me) Jun 06 12:52:12 panda84kde: daiane_ is Daiane :P Jun 06 12:52:33 panda84kde: Hi Jun 06 12:53:25 hi daiane_ :) Jun 06 12:54:11 I'm the one who turned you crazy to have vivante-gpu-sdk packaged :) Jun 06 12:54:54 I am not certain what a mesa bbappend is. But i don't think I altered nothing. Jun 06 12:57:22 ivali: I would assume what you need now is "mesa-driver-swrast" since mesa-dri was renamed to mesa Jun 06 12:57:37 thank you Jun 06 12:59:00 ivali: FYI, you may find the migration info in the reference manual useful: http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html#moving-to-the-yocto-project-1.4-release Jun 06 13:01:44 I understand the issue. That folder got renamed, but some references to it remained unchanged, thanks Jun 06 13:02:55 ivali: all of the references within the core metadata were updated, FWIW Jun 06 13:03:08 it wasn't the folder that got renamed, it was the recipe Jun 06 13:09:52 I am unsure what to do next. As I can see, lines 25-27 from meta/recipes-graphic/mesa/mesa.inc ( https://github.com/openembedded/oe-core/blob/master/meta/recipes-graphics/mesa/mesa.inc ) try to deal with this change. Is this correct? Jun 06 13:12:45 As i can see. This commit replaces mesa-dri to mesa in the whole tree https://github.com/openembedded/oe-core/commit/c8bbb9983bcc7cfc5332e89c3e8148505b4ca83f Jun 06 13:27:51 How can i clean all? Jun 06 13:29:06 ivali: what do you mean by all? Jun 06 13:29:57 All the deleted packages, downloaded archives, configs Jun 06 13:30:06 I deleted the tmp folder from build Jun 06 13:33:24 ivali: just delete tmp and sstate-cache Jun 06 13:45:47 hi guys. Here is a draft of glmark2 recipe. Could you please take a look at it? http://pastebin.com/DU6jxWAN Jun 06 13:46:58 It works fine for me and splits correctly dbg, doc and main package Jun 06 13:52:58 mmm... nope, some errors on paths at runtime Jun 06 13:54:06 still, please take a look at the recipe for other errors (I'm still looking on how to list COPYING.SGI in LICENSE) Jun 06 14:06:02 Hi all, did someone tried to export yocto build appliance VM to a customized VM (like ubuntu)? What kind of mechanism is used to start hob a start of the linux ? (daemon or simple script in /etc/init.d ?) Jun 06 14:06:40 at start of the yocto linux * Jun 06 14:07:12 panda84kde: recipe looks mostly OK but I'd question if the means of doing the build will avoid host contamination; it looks like there's nothing to prevent it from linking to host libraries etc. Jun 06 14:09:17 bluelightning: I've took http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/python/python-pycairo_1.10.0.bb as a source of inspiration, as I'm not a bitbake expert Jun 06 14:09:32 rburton: back? :) Jun 06 14:10:12 panda84kde: I don't know waf very well, just pointing out a potential issue Jun 06 14:10:32 well, me neither Jun 06 14:11:40 bluelightning: which directive warns you the most? Jun 06 14:11:41 hopefully it should be possible to tell where the waf build process is looking for libraries, and if it ever looks on the host then try to find a way to stop it from doing that Jun 06 14:12:52 panda84kde: actually looking at your paste again I had missed the --prefix= so that might be enough Jun 06 14:13:43 bluelightning: actually that's a source of problem. In fact binaries search for data in my yocto build path, instead of target path Jun 06 14:13:59 I'm looking into splitting prefix and destdir Jun 06 14:14:23 panda84kde: right; it depends what waf understands prefix to be Jun 06 14:14:41 panda84kde: if prefix means where it should be installed to on the target then yes that would be a problem Jun 06 14:15:22 panda84kde: with other tools there is an understanding of a "sysroot" which is the path to be looked at at build time, separate from runtime Jun 06 14:15:25 bluelightning: here's waf help: http://pastebin.com/vNg85qMa Jun 06 15:34:27 morning bluelightning_ Jun 06 15:36:58 morning mranostay Jun 06 15:39:24 bluelightning: fixed the problem :) Minor issure: the result has an empty -dev package. How do I avoid building that empty package? Jun 06 15:42:18 unset ALLOW_EMPTY Jun 06 15:45:16 guys, what should I write in the LICENSE files for this one? http://bazaar.launchpad.net/~glmark2-dev/glmark2/trunk/view/head:/COPYING.SGI Jun 06 15:45:28 *LICENSE field Jun 06 15:52:10 mranostay: thanks Jun 06 16:00:35 hi there, I'm trying to compile a native package for the same architecture as used for the target package. However, I can't find the appropriate way to get the target's -march and -m values. Does anyone have a pointer on where to look or possibly even an example recipe? Jun 06 16:08:15 tolbrino: if you have special compiler flags you can add them in your machine definition http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html#var-CFLAGS Jun 06 16:08:59 or if you just want the FLAG for you recipe add them in the recipe Jun 06 16:12:25 mranostay: should ALLOW_EMPTY_${PN} = "" undefine it? Jun 06 16:12:50 yes that would be the correct way in a bbappend Jun 06 16:13:51 uhm... I'm not in a bbappend, so I should use ALLOW_EMPTY = "" , right? Jun 06 16:18:58 mranostay: nope. None of those work. I did a -c cleansstate but the (empty) dev packages is still there Jun 06 16:26:47 panda84kde: I'm using CFLAGS already. The difficulty is knowing which in the native package which target cflags will be used. Jun 06 16:27:32 tolbrino: you can try a devshell and see how build works inside that Jun 06 16:27:54 e.g. "bitbake -c devshell " Jun 06 17:33:04 Can OE help in creating an SDK for the generated Linux distribution, that runs on Win32 ? Right now I'm struggling with getting gcc compiled with mingw, using the sys-root from the linux created sdk Jun 06 23:55:57 do any of the standard images include resolvconf? I can see the recipe in meta/recipes-connectivity, but can't see anything pulling it in **** ENDING LOGGING AT Fri Jun 07 02:59:58 2013