**** BEGIN LOGGING AT Mon May 23 02:59:58 2016
May 23 09:42:41 <ant_work> bluelightning: hi
May 23 09:42:58 <bluelightning> hi ant_work
May 23 09:43:14 <ant_work> I'll have to pull and build anew after last changes in oe-core
May 23 09:43:26 <ant_work> I've seen you pulled most of the patches. thanks
May 23 09:43:40 <ant_work> I plan to fix the staging in our recipes now
May 23 09:43:56 <ant_work> seems we can use SYSROOT_DIRS now
May 23 09:44:34 <ant_work> about opie, pls think about fixing the qa_error
May 23 09:51:35 <ant_work> but there is smthing wrong under the hood
May 23 09:51:47 <ant_work> include( $(OPIEDIR)/include.pro )
May 23 09:51:56 <ant_work> ^ anything there to include
May 23 10:29:06 <bluelightning_> ant_work: I've pulled in all of the patches except for a few which looked suspect - I'm not sure that that is the right fix for the problem
May 23 10:29:29 <bluelightning_> ant_work: what do you mean by "anything there to include" ?
May 23 10:59:38 <ant_work> bluelightning: at least in opie-multikey (but I think it's wider) the .pro file meant to be included is in a subdir
May 23 10:59:49 <ant_work>   +-include( $(OPIEDIR)/include.pro )
May 23 10:59:49 <ant_work> ++include( $(OPIEDIR)$(palmtopdir)/include.pro )
May 23 11:00:30 <bluelightning> the question with something like this is always what changed in order to make this now fail when it worked before?
May 23 11:00:53 <bluelightning> and is simply inserting that path correct or is it something lower down that needs fixing?
May 23 11:01:24 <ant_work> is OPIEDIR right pointing just to sysroot?
May 23 11:02:17 <ant_work> qht does *some* packages, the plugins, install under /lib/opie ?
May 23 11:05:20 <bluelightning> the plugins are plugins, not general use libraries
May 23 11:05:51 <bluelightning> I don't know what OPIEDIR should point to off the top of my head, I'd need to read the code
May 23 11:07:30 <ant_work> imho we could just let the .so live under $libdir but the recipes seems expecting $libdir/opie/lib
May 23 11:07:53 <ant_work> and if you install a .so in $libdir you get the QA
May 23 11:08:12 <bluelightning> what multikey is apparently doing (linking to another plugin as a dynamic lib) is unusual though
May 23 11:08:32 <bluelightning> it's not the norm, so we shouldn't go rearranging the layout to fit that
May 23 11:10:13 <ant_work> then it is indeed opie-multikey wo need fix, not the plugin
May 23 11:10:30 <ant_work> argh.. I can't type today :/
May 23 11:10:58 <ant_work> iirc there are only 3 plugins once you build the opie-image
May 23 11:11:23 <ant_work> I mean, 3 .so staged under /usr/lib/opie/lib
May 23 11:13:40 <ant_work> in case of i.e. opie-unikeyboard there is an empty do_install
May 23 11:14:05 <ant_work> but for opie-pickboard someone sometime decided to stage a second .so
May 23 11:14:12 <ant_work> and the headers
May 23 11:15:54 <ant_work> I still miss the magic...I get is is in opie_do_opie_install()
May 23 11:16:41 <bluelightning> yep, the opie class adds its own do_opie_install (which was the source of other QA issues earlier since it wasn't fakeroot)
May 23 11:16:56 <bluelightning> opie_do_opie_install becomes do_opie_install via EXPORT_FUNCTIONS FYI
May 23 11:18:01 <ant_work> it seems installing under palmtopdir
May 23 11:18:15 <ant_work> #103
May 23 11:20:10 <ant_work> ah..and about the .pro
May 23 11:20:14 <ant_work> #20
May 23 11:20:28 <ant_work> err.. #29
May 23 11:36:50 <bluelightning> I'll have to take a closer look at this later
May 23 11:37:03 <bluelightning> for now I need to get some sleep
May 23 11:37:04 <bluelightning> g'night
**** ENDING LOGGING AT Tue May 24 02:59:58 2016