[01:48] <kdub> thanks for the review duflu
[01:49] <duflu> kdub: I don't claim to have tested it, but I support the idea :)
[07:14] <RAOF> Oh, wow.
[07:14] <RAOF> bzr merge -i --uncommitted works exactly like how I want it to work.
[08:40] <mlankhorst> morning
[10:29] <anpok_> alan_g: duflu alf_: which direction should i go now..
[10:29] <anpok_> keep report::, but drop lttng:: and report::logging?
[10:30] <duflu> anpok_: Ever forward... ?!
[10:30] <duflu> Oh
[10:31] <duflu> anpok_: I prefer the namespaces how they are today. And would prefer even more if we had fewer than that. So abstain
[10:31]  * duflu -> dinner
[10:31] <duflu> Good night
[10:31] <alf_> duflu: bye!
[10:31] <alan_g> Bye
[15:46] <greyback> AlbertA: hey, quick comment on https://code.launchpad.net/~albaguirre/unity-mir/cross-compile-link-fix/+merge/205690
[15:48] <anpok> alan_g: alf_: ... 200 lines less
[15:49] <AlbertA> greyback: at least the mirserver library
[15:49] <AlbertA> should be there
[15:49] <AlbertA> as it's a direct dependency - it makes sure the api signatures haven't changed
[15:50] <alan_g> anpok: It isn't the number of lines in the diff that matters. It is how easy it is to follow.
[15:54] <AlbertA> greyback: Or not sure if you mean to use only the _LDFLAGS?
[15:54] <greyback> AlbertA: yeah that was what I was asking. I was pouring over cmake manual to understand the difference
[15:55] <greyback> AlbertA: _LIBRARIES seems to not set the -L path, which -LDFLAGS definitely does
[15:55] <AlbertA> greyback: the LDFLAGS for those 3 packages at least just return -L path
[15:55] <AlbertA> and the libraries flag sets -l<libname>
[15:56] <greyback> AlbertA: http://www.cmake.org/cmake/help/v2.8.12/cmake.html <- searching for "_LDFLAGS" was what I was reading. I'm surprised now
[15:59] <greyback> as it implies LDFLAGS contains all required linker flags (which I'd expect), whereas LIBRARIES contains list of lib names that need their pkgconfig scanned for linker flags
[15:59] <greyback> do I mis-understand?
[16:02] <anpok> greyback: the cmake pkg-config module creates a load of variables for each found library
[16:02] <AlbertA> greyback: that's what I read too
[16:02] <anpok> there is for example also PKG_NAME_LIBRARY_DIRS
[16:02] <AlbertA> greyback: but it's essentially the output of pkg-config
[16:02] <anpok> and that one could be used in link_directories() which is just symetric to include_directories()
[16:02] <greyback> AlbertA: right
[16:03] <greyback> So I guess I'm confused :)
[16:03]  * greyback needs to dig a little more
[16:03] <anpok> i.e. look inside CMakeCache.txt of your build dir..
[16:05] <greyback> anpok: yeah I've been doing that, to check AlbertA's patch did what I expected, but now I'm unclear what's really happening
[16:18] <greyback> mterry: comment on https://code.launchpad.net/~mterry/unity-mir/alpha-greeter/+merge/204069
[16:21] <mterry> greyback, noted.  I tested on android and it worked!  So apply_to must be doing something currently...
[16:22] <greyback> mterry: nested in android? Or standalone?
[16:22] <mterry> greyback, testing yourself is a little tricky.  You'd need to install several branches to see the difference, but will add to MP
[16:22] <mterry> greyback, nested
[16:22] <mterry> greyback, oh, you say that
[16:22] <greyback> mterry: yeah, that I expect to be ok. Just standalone I found apply_to wasn't being called
[16:23] <mterry> greyback, fair.  Though I don't happen to care about standalone case
[16:23] <greyback> mterry: yep
[16:23] <greyback> mterry: but I did for a while :)
[16:24] <mterry> greyback, :)  hey, how is the scenegraph stuff going, btw?
[16:25] <greyback> mterry: oh I've not been able to touch it for weeks now. Hope to resume it after MWC. racarr is doing some Mir adjustments to help integrate it however
[16:26] <mterry> greyback, cool.  Poke me when it is more play-with-able.  I eventually plan to use it in the USC for interstitial animations between sessions
[16:27]  * mterry heads out to buy a ladder
[16:27] <greyback> mterry: really? Ok. /me thinks we'd better profile it carefully before nesting it like that
[16:45] <AlbertA> greyback: you were right
[16:45] <AlbertA> greyback: we only need LDFLAGS
[16:45] <AlbertA> greyback: it does include everything like the docs say :)
[16:45] <AlbertA> greyback: i.e. -L<path>;-l<libname>
[16:49] <greyback> AlbertA: but I just tried compiling without LIBRARIES and it failed to link to mir!
[16:52] <AlbertA> greyback: really? I tried here just using LDFLAGS it worked ok on both
[16:52] <AlbertA> native and cross compiling
[16:53] <greyback> let me try again, maybe I screwed something up
[16:57] <greyback> AlbertA: you're correct, it works with just LDFLAGS
[16:58] <AlbertA> I pushed a new revision
[16:58] <AlbertA> to the branch
[16:59] <greyback> AlbertA: and approved as it's exactly what I now have. Thank you!
[16:59] <AlbertA> greyback: thanks!
[21:41] <RAOF> anpok: It's not clear to me why logging:: should be under report::, as they're kinda two separate things. Not doing that move also reduces the namespace nesting somewhat.