**** BEGIN LOGGING AT Wed Jan 02 02:59:59 2013 Jan 02 08:06:16 morning! Jan 02 08:06:26 and happy new year ! Jan 02 08:06:27 :) Jan 02 08:49:23 good morning and Happy New Year Jan 02 09:17:04 good morning and happy new year Jan 02 09:22:34 morning all, and have a nice embedded 2013! Jan 02 09:38:40 Happy New Year all Jan 02 11:17:50 is it normal i cannot define (in a class) do_package_prepend ? Jan 02 11:18:20 NOTE: Error expanding variable do_package Jan 02 11:19:00 no, you're probably using wrong indentation Jan 02 11:19:41 the only examples i saw use "python" Jan 02 11:19:57 when i rename it to do_install_append it works Jan 02 11:20:54 i guess the do_package method is python only Jan 02 11:21:33 yes Jan 02 11:22:18 using a class is it possible to do_install_append after the do_install_append of the recipe or i must use do_package_prepend ? Jan 02 11:23:59 you can have multiple _appends and you need to know if you want to change do_install or do_package Jan 02 11:24:38 JaMa: i know i can have multiple append, the problem is the execution order of them... Jan 02 11:25:09 JaMa: i need my do_install_append to be at the end, after the recipe do_install_append (if defined) Jan 02 11:25:23 JaMa: if it's not possible, i guess i have to use do_package Jan 02 11:25:29 then use inherit in right place Jan 02 11:25:51 ok Jan 02 11:27:15 i never saw inherit after a do_something() Jan 02 11:29:39 well it works, but it looks weird :) Jan 02 11:29:48 thanks Jan 02 13:44:40 Hello. I am trying to cross-compile a package which depends on glib. But it seems that the Makefile is not well designed. The Makefile needs some glib headers and I added ${CROSS_COMPILE_SYSROOT}, ${DESTDIR} and ${D} but it seems that those variables do not work inside the Makefile... Any help ? Jan 02 14:09:40 ${STAGING_INCDIR} doesn't work too.. I am missing something ? Jan 02 14:14:02 try exporting the variable in the recipe in do_compile_prepend Jan 02 14:27:00 All is fine now Jan 02 14:29:31 thanks Jan 02 16:29:16 is there a way (task?) to reinstall a recipe without recompiling it ? Jan 02 16:29:44 'reinstall'? Jan 02 16:29:49 recipes don't get installed Jan 02 16:29:53 binary packages do Jan 02 16:30:10 a way to redo the do_install Jan 02 16:30:37 bitbake -c install -f Jan 02 16:30:42 ok Jan 02 16:30:53 i did not think of that Jan 02 16:30:57 thanks kergoth Jan 02 16:34:28 np Jan 02 17:24:32 HNY all Jan 02 17:30:15 happy new year moin... Jan 02 18:02:54 what is the best way to track a dependency resolutino issue Jan 02 18:03:07 oh, and happy new year Jan 02 18:06:46 levonmaa: insufficient information Jan 02 18:09:05 kergoth: sorry... I have to build environments and in the other one the 'bitbake -g ' generates to correct dependency graph Jan 02 18:09:25 and in the other one is does not and the compilation naturally fails Jan 02 18:09:53 the recipe is the same in both envs Jan 02 18:10:32 still not enough information to even begin to give ou any guidance Jan 02 18:10:39 what exactly is 'correct' about the graph and incorrect about the other? Jan 02 18:10:59 so I'm looking for tools that could help me trouble shoot why the DEPENDS assignment is not working in one env Jan 02 18:11:32 there are like 15 ways of declaring a dependency Jan 02 18:11:37 'DEPENDS' is only one of them Jan 02 18:12:09 the first step is always to use bitbake -e to verify that variables are set to what you think they are Jan 02 18:12:35 yes, did that and it seems sane to me Jan 02 18:36:53 kergoth: let me take that back ;) Jan 02 18:37:11 the DEPENDS line is missing the dependencies Jan 02 18:38:28 but they are listed in the recipe Jan 02 18:39:31 so in essence I guess I want to find out ways of tracking out the dependency resolution Jan 02 18:51:59 dependency resolution isn't the problem Jan 02 18:57:10 kergoth: hmmm.. what makes you say that Jan 02 18:57:36 kergoth: I mean the reason why to compilation fails in the other env is that a header is missing Jan 02 18:57:54 and that header is provided by a package that is listed in the DEPENDS line Jan 02 18:58:22 if I manually bitbake the missing package the header is there Jan 02 18:58:43 you are using bitbake -e , not just 'bitbake -e', right? Jan 02 18:58:51 kergoth: yes Jan 02 19:43:34 kergoth: fyi, found the cause... SUE (stupid user error) :) Jan 02 19:53:08 those darned SUEs!! Jan 02 21:01:18 d, sorry) Jan 02 21:41:49 so to run the simple-agent python script for bluetooth pairing Jan 02 21:42:05 I need to from gi.repository import GObject Jan 02 21:42:15 but it fails and I can't see where this module comes from Jan 02 21:42:18 any clues? **** ENDING LOGGING AT Thu Jan 03 02:59:59 2013