**** BEGIN LOGGING AT Tue Jan 31 02:59:58 2012
Jan 31 07:12:43 <eFfeM_work> gm
Jan 31 08:07:17 <mckoan> good morning
Jan 31 09:32:06 <bluelightning> morning all
Jan 31 09:32:11 <Jin^eLD> mornin
Jan 31 10:40:14 <pb_> morning all
Jan 31 11:03:59 <bluelightning> hi pb_
Jan 31 11:08:31 <pb_> does anybody have a concise explanation of how the gcc, gcc-runtime and libgcc recipes are all supposed to interact?
Jan 31 11:08:38 <pb_> I'm a little bit confused by which ones are meant to be doing what.
Jan 31 11:30:19 <bluelightning> pb_: maybe RP__ can advise
Jan 31 11:30:40 <bluelightning> assuming the git history is of no help...
Jan 31 11:35:07 <pb_> well, the checkin comment for 0df3c481309e89b93e8a57773eb9c470b4dd13a7 seems to be trying to explain it.
Jan 31 11:35:52 <pb_> but it is a monster sentence spanning seven lines and I haven't quite managed to read to the end of it without going cross-eyed yet
Jan 31 11:36:42 <pb_> however, I think I've now managed to figure out enough to solve my immediate problem so I am happy :-)
Jan 31 11:57:52 <RP__> pb_: quick summary is we wanted to take packaging of gcc bits out of the cross recipes
Jan 31 11:58:13 <RP__> pb_: We can build most bits of gcc runtime standalone. libgcc has to be copied from gcc-cross
Jan 31 12:08:54 <pb_> righto, thanks, that makes sense
Jan 31 12:10:01 <pb_> the gcc packaging is a bit of a maze right now, loads of tiny files which all include each other. 
Jan 31 12:10:13 <pb_> e.g. gcc-cross4.inc which just contains a single line "require gcc-cross.inc" :-}
Jan 31 13:22:32 <denisATeukrea> khem, I'll look now
Jan 31 13:22:35 <denisATeukrea> hi btw
Jan 31 13:32:22 <denisATeukrea> khem, stepi is way too long because it goes into a loop
Jan 31 13:32:40 <denisATeukrea> and reverse-stepi fails
Jan 31 14:22:02 <otavio> denisATeukrea: update the meta-freescale as we did some merges
Jan 31 14:22:17 <otavio> denisATeukrea: so you're  GNUtoo ? /me confused now
Jan 31 14:42:54 <GNUtoo> otavio, yes
Jan 31 14:43:12 <GNUtoo> otavio, GNUtoo is my nick for community projects and denisATeukrea is for work
Jan 31 14:43:12 <otavio> GNUtoo: :)
Jan 31 14:43:19 <otavio> I see
Jan 31 14:43:43 <GNUtoo> and the work computer and community computer are separated too
Jan 31 14:43:49 <GNUtoo> mail too are separated etc...
Jan 31 14:44:09 <otavio> gosh
Jan 31 14:44:16 <otavio> two separated persons, :P
Jan 31 14:44:22 * otavio more confused now lol
Jan 31 14:44:22 <denisATeukrea> lol
Jan 31 14:44:23 <otavio> hehheh
Jan 31 14:44:49 <denisATeukrea> for the mail it's quite normal procedure
Jan 31 14:45:05 <denisATeukrea> so when you send a patch you send it on behalf of the company
Jan 31 14:45:12 <otavio> yes
Jan 31 14:46:20 <denisATeukrea> but since my laptop does not have enough ram(it blocks during some compilation) the company sent me a laptop
Jan 31 14:46:49 <denisATeukrea> for instance compiling asio boost fails with OOM
Jan 31 14:48:14 <otavio> denisATeukrea: heh
Jan 31 14:48:53 <denisATeukrea> and they had an unused laptop....
Jan 31 15:25:09 <denisATeukrea> hi JaMa 
Jan 31 15:25:18 <denisATeukrea> I've that in compiling webkit-efl:
Jan 31 15:25:20 <denisATeukrea> ../wtf/libwtf_efl.so.0.1.0: error: undefined reference to 'eina_module_free'
Jan 31 15:25:32 <denisATeukrea> it's in angstrom-bleeding
Jan 31 15:26:50 <JaMa> does it continue with something about DSO and being defined in libeina which is missing on ld command line?
Jan 31 15:28:02 <denisATeukrea> let me look
Jan 31 15:28:33 <denisATeukrea> no it doesn't
Jan 31 15:28:49 <denisATeukrea> when grepping for eina no trace of DSO or .so
Jan 31 15:29:22 <khem> denisATeukrea: it uses gold linker which does nt do over linking like gnu ld
Jan 31 15:29:39 <khem> so this library is missing from link cmdline 
Jan 31 15:29:41 <denisATeukrea> ahh ok
Jan 31 15:30:03 <denisATeukrea> khem, btw I abandoned with firefox stepi in assembly takes ages
Jan 31 15:30:05 <khem> denisATeukrea: its righly called angstrom-bleeding
Jan 31 15:30:26 * denisATeukrea looks at ericben who told him to try angstrom-bleeding
Jan 31 15:31:09 <khem> denisATeukrea: its ok to try though but expect some problems I mean to say
Jan 31 15:31:35 <khem> denisATeukrea: it should speed up linking webkit though
Jan 31 15:32:34 <denisATeukrea> ok
Jan 31 15:32:52 <denisATeukrea> does gold offers more performance at compile time only?
Jan 31 15:33:02 <denisATeukrea> or does it also offers more performance at runtime too?
Jan 31 15:59:44 <Tartarus> Anyone using just oe-core behind a corporate proxy?
Jan 31 16:00:51 <likewise> Tartarus: at a customer I once did, I finally managed to get them "open up" a (REMOTE) port. Sigh.
Jan 31 16:01:04 <Tartarus> heh
Jan 31 16:01:21 <likewise> As if the remote port number has anything to do with what is on it... :)
Jan 31 16:02:03 <Tartarus> This all works fine w/ angstrom (well, as fine as this crap ever can)
Jan 31 16:02:12 <Tartarus> Looks like something wasn't making it up the wrapper scripts tho
Jan 31 16:02:27 <likewise> Tartarus: not sure if we have an exact oe-core mirror on a GIT HTTP-capable server (it that's what you are looking for)?
Jan 31 16:02:47 <Tartarus> likewise: No, I'm looking for http_proxy/etc to be obeyed
Jan 31 16:02:59 <likewise> Tartarus: ah, ok.
Jan 31 16:03:10 <msm> Tartarus: i am
Jan 31 16:03:12 <Tartarus> It wasn't, but I didn't set the env until after I did . oe-init-build-env
Jan 31 16:03:29 <Tartarus> So I'm trying again now, w/ the proxy stuff on before I start
Jan 31 16:04:00 <Tartarus> msm, oe-core or poky?
Jan 31 16:04:59 <msm> mostly poky
Jan 31 16:05:06 <msm> so nevermind, if it's that specific =)
Jan 31 16:05:40 <Tartarus> Well, just worried about sync stuff
Jan 31 16:05:47 <Tartarus> but, ah, nm, it looks like I'm just in svn-hell
Jan 31 16:15:24 <likewise> denix: hi there denys
Jan 31 16:16:04 <denix> likewise: good morning!
Jan 31 16:16:19 <likewise> gm
Jan 31 17:02:22 <likewise> denisATeukrea: hi denis, you involved with i.mx53 now also?
Jan 31 17:04:04 <khem> likewise: howdy
Jan 31 17:05:40 <likewise> khem: hey khem, good morning
Jan 31 17:07:02 <denisATeukrea> likewise, yes
Jan 31 17:07:17 <denisATeukrea> for work tough
**** BEGIN LOGGING AT Tue Jan 31 17:23:32 2012
Jan 31 17:30:03 <spacecolonyone> hi guys, So I've managed to get a message like: NOTE: multiple providers are available for runtime kernel-module-blah-blah (linux-omap-psp, linux-kexecboot, linux-omap, linux-dummy, linux). I got it because I changed my  preferred_provider_virtual/kernel from "linux" to "linux-3.2", which clearly didn't work.
Jan 31 17:31:45 <spacecolonyone> Now I'm curious about two things: 1) how do I go setting what particular release "linux" points to and 2) where is this mysterious list of options defined? 
Jan 31 17:32:16 <likewise> spacecolonyone: PREFERRED_PROVIDER_
Jan 31 17:32:50 <likewise> PREFERRED_PROVIDER_virtual/kernel = "linux-imx"
Jan 31 17:32:51 <likewise> PREFERRED_VERSION_linux-imx = "2.6.35.3"
Jan 31 17:33:40 <likewise> spacecolonyone: you first specify what package you want to provide the virtual/kernel, then for that package you can specify the version. At least, that's how I use it.
Jan 31 17:34:28 <likewise> spacecolonyone: the available versions depend on your meta layers (recipes/linux/linux*.bb or recipes-kernel/linux/linux*bb)
Jan 31 17:34:29 <spacecolonyone> likewise: I see, but since I don't currently have a PREFERRED_VERSION in my conf file then there are defaults defined somewhere, no?
Jan 31 17:34:46 <likewise> spacecolonyone: not defined, they are found in the meta data
Jan 31 17:34:56 <likewise> spacecolonyone: by parsing through the directories with recipes
Jan 31 17:35:53 <likewise> spacecolonyone: I do not like this "undeterministic" feature, but at least I know how to treat it how it likes to be treated.
Jan 31 17:36:15 <spacecolonyone> well, e.g. in meta-ti there are recipes for linux, linux 3.0,  3.,  linux-omap, various versions there etc.
Jan 31 17:36:35 <bluelightning> likewise: it's entirely deterministic
Jan 31 17:38:33 <spacecolonyone> I imagine it is, but I still don't see how "linux" w/o a preferred version defined comes to be mapped to linux 3.0.17
Jan 31 17:39:09 <spacecolonyone> not to be fussy, I'm just confused because I'd like to finagle with it
Jan 31 17:42:08 <bluelightning> it picks the latest available version
Jan 31 17:42:26 <likewise> bluelightning: of what provider?
Jan 31 17:42:45 <bluelightning> likewise: I'm talking about in general
Jan 31 17:42:48 <likewise> linux-a 3 vs linux-b 2 will pick 3?
Jan 31 17:44:05 <spacecolonyone> bluelightning: that doesn't seem match to be the behavior I'm seeing. By default it builds 3.0.17 but there is a recipe for 3.1 in the meta-ti layer
Jan 31 17:44:06 <bluelightning> likewise: you have to choose the provider, that's not supposed to be undefined
Jan 31 17:44:37 <bluelightning> spacecolonyone: does that recipe specify DEFAULT_PREFERENCE = "-1" ?
Jan 31 17:44:49 <bluelightning> or perhaps it is marked with COMPATIBLE_MACHINE?
Jan 31 17:44:51 <likewise> bluelightning: yes, but it is, and it is freaking out every starting OE developer. I rather want it to say: you MUST choose a provider and FAIL.
Jan 31 17:44:57 * spacecolonyone looks
Jan 31 17:45:26 <bluelightning> likewise: feel free to propose that on the mailing list and we can discuss it
Jan 31 17:45:58 <bluelightning> it's been that way for some time now though, I was not aware it was a big problem
Jan 31 17:46:00 <likewise> bluelightning: a few years back my proposal was rejected.  I do not see the use case for a virtual/target to be totally undefined. 
Jan 31 17:46:22 <spacecolonyone> compatible machine is marked as "beagleboard", but the default preference is -99 !
Jan 31 17:46:32 <bluelightning> spacecolonyone: right, that's why it does not get picked
Jan 31 17:46:55 <likewise> bluelightning: like spacecolonyone says, he expects a default (fallback) which is defined.  In case it is undefined, the system really never picks the right provider.
Jan 31 17:46:56 * spacecolonyone wonders why -99
Jan 31 17:47:10 <bluelightning> spacecolonyone: perhaps that's because the author is not confident it is fully working
Jan 31 17:47:18 <likewise> bluelightning: I will bring it up on the mailing list again.
Jan 31 17:47:39 <bluelightning> likewise: yes... if it's a contentious issue there we have the TSC to resolve it
Jan 31 17:47:41 <spacecolonyone> yea, and I do recall about hearing mention of some regression for the beagleboard on 3.1
Jan 31 17:50:21 <CIA-21> 03Christopher Larson <chris_larson@mentor.com> 07master * rc9f58ef6b8 10bitbake.git/lib/bb/cooker.py: 
Jan 31 17:50:21 <CIA-21> cooker: add missing shutdowns to the exception handling
Jan 31 17:50:21 <CIA-21> Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Jan 31 17:52:21 <spacecolonyone> bluelightning I think I see how you are saying this gets picked. Correct me if I'm wrong. I'm assuming preferred provider is "linux" and preferred version is unset 1) all the .bb files are scanned that are named linux_{some version number}.bb  2) ones that do not have my machine in their compatible machine list are dropped 3) of those left the most recent is chosen, provided it's default preference is not lower than the next newest kernel
Jan 31 17:52:21 <spacecolonyone> determined by timestamps as automagically found using the SRCREV ?
Jan 31 17:53:17 <bluelightning> spacecolonyone: it's determined by PE, PV & PR
Jan 31 17:53:32 <bluelightning> where PV might contain SRCREV if the source is being fetched from git
Jan 31 17:53:46 <bluelightning> but yes, what you outlined is basically how it works
Jan 31 17:55:35 <bluelightning> (normally PV is determined from the recipe name... i.e. linux_3.1.bb -> PV = "3.1"
Jan 31 17:55:36 <bluelightning> )
Jan 31 17:55:43 <spacecolonyone> Cool. So how does it go about coming up with that list (e.g. linux-omap-psp, linux-kexecboot, linux-omap, linux-dummy, linux) 
Jan 31 17:56:45 <spacecolonyone> I guess it would harvest all the different kernel recipe file names dropping the PV, but how would it know the recipe is inface for a kernel
Jan 31 17:58:19 <bluelightning> spacecolonyone: when it says "multiple recipes PROVIDE xyz" it means that those recipes all say PROVIDES = "xyz"
Jan 31 17:59:19 * spacecolonyone looks
Jan 31 17:59:20 <bluelightning> kernel.bbclass sets PROVIDES += "virtual/kernel" and thus any recipe that does "inherit kernel" will PROVIDE virtual/kernel
Jan 31 17:59:32 <bluelightning> and all kernel recipes inherit kernel
Jan 31 18:00:41 <spacecolonyone> except for these... *digs deeper*
Jan 31 18:01:39 <spacecolonyone> found it in the linux.inc
Jan 31 18:03:45 <spacecolonyone> So essentially I need to create a recipe for 3.2.2 (since there doesn't appear to be one) scour the webs for any patches that are required, put them in my overlay and list them in my recipe, set preferred version, and cross my fingers?
Jan 31 18:04:37 <bluelightning> spacecolonyone: pretty much... you might wish to consult with the folks in #beagle if you haven't already :)
Jan 31 18:04:45 <bluelightning> re 3.2 readiness
Jan 31 18:05:48 <spacecolonyone> they are pretty quiet atm. :/. and the folks over in v4l have essentially said mainline is what i should use for new camera driver development
Jan 31 18:11:39 <bluelightning> spacecolonyone: ah right, fair enough
Jan 31 18:12:03 <bluelightning> spacecolonyone: it would be interesting to know if the regression is fixed in mainline, I haven't checked
Jan 31 18:14:19 <spacecolonyone> which regression?
Jan 31 18:14:43 <bluelightning> spacecolonyone: the 3.1 one you referred to above
Jan 31 18:16:39 <spacecolonyone> Ah, yea, I believe it is, I think I was reading that it just didn't make it intime for the 3.1 merge window or something similar
Jan 31 18:24:17 <bluelightning> ah ok, that's good news
Jan 31 18:25:03 <khem> hmmm so I see that cross module-init-tools is really not needed 
Jan 31 18:26:09 <spacecolonyone> bluelightning, likewise: Thanks, btw. that helped straighten me out
Jan 31 18:30:51 <bluelightning> spacecolonyone: no probs
Jan 31 19:07:44 <Crofton|work> khem, so continuing yesterdays conversation
Jan 31 19:07:56 <Crofton|work> the file in gnuradio uses #~/usr/bin/env python
Jan 31 19:08:18 <Crofton|work> but when it is installed in the install dir, the #1/path tio python in staging gets added
Jan 31 19:51:39 <ka6sox> khem ping?
Jan 31 20:08:39 <khem> ka6sox: hey
Jan 31 20:08:52 <ka6sox> khem, can you get into garnet?
Jan 31 20:09:12 <khem> yes I can
Jan 31 20:09:22 <ka6sox> kewl
Jan 31 20:09:30 <khem> seems to be fine I had issue which scoutcamper fixed
Jan 31 20:09:41 <ka6sox> good, thanks
Jan 31 21:37:51 <pb_> re
Jan 31 21:38:27 <pb_> all tax returns completed for another year, phew
Jan 31 21:40:30 <spacecolonyone> woohoo! I'll do mine sometime soon. I actually find it therapeutic. It is always fun to discover tax breaks. hmm if i buy 3.2 acres and ge 3 goats and a chicken then I'll be under this form and ... 
Jan 31 21:40:41 <spacecolonyone> s /ge /get
Jan 31 21:40:54 * Jin^eLD hates those tax things
Jan 31 21:41:12 <Jin^eLD> I usually have to force myself a week before the deadline
Jan 31 21:41:20 <pb_> hah, a week?
Jan 31 21:41:32 <Jin^eLD> yes, yes, I'm a chicken ;)
Jan 31 21:41:47 <pb_> our deadline is in 2 hours 19 minutes :-}
Jan 31 21:41:58 <Jin^eLD> lol
Jan 31 21:42:31 <Jin^eLD> well, I'm doing it on a hobby level, you seem to take it as pros ;)
Jan 31 21:42:32 <spacecolonyone> The annoying this is as a grad student I've got to send in checks throughout the year because of how I'm paid.
Jan 31 21:43:37 <Jin^eLD> the most annoying thing is to see how much they rob you each year
Jan 31 21:43:57 <pb_> yeah, I just got a bit of a nasty shock on that front.
Jan 31 21:44:01 <pb_> oh well
Jan 31 21:44:48 <Jin^eLD> well, I do not know where you are coming from, but in austria it's more then just "shock", it's so high here so I actually think of moving somewhere else
Jan 31 21:44:54 <spacecolonyone> I find it helps to overpay and then get a check. Weird, I know.
Jan 31 21:45:31 <fray> ha.. I try to over play slightly.. but us Federal I usually get back a decent amount, and I've so far not figured out how to not own the State of Minnesota.. :P
Jan 31 21:45:42 <fray> usually the check goes from one hand to the state.. :P
Jan 31 21:46:15 <Jin^eLD> in .at you get owned no matter what you do
Jan 31 21:46:37 <Jin^eLD> it's really frustrating here
Jan 31 21:46:59 <fray> I've only done a rough estimate of my taxes for 2011 so far..  but having to buy software to have any chance of doing it right is a real pain
Jan 31 21:47:19 <fray> and because I underpaid (throughout the year) my MN, I was close to owing an additional penalty  :P
Jan 31 21:49:28 <pb_> ah.  well, that's one thing we do have here: you can file your tax return on the web and (unless your tax affairs are very complicated) it works everything out for you.
Jan 31 21:50:02 <fray> I wish.. I can only file online if I don't account for deductions..
Jan 31 21:50:21 <fray> don't get me wrong, it's nice we're allowed to deduct Mortgage interest.. but you'd think they could make it easier to do so
Jan 31 21:51:26 <pb_> ah, my sympathy for you evaporates.  mortgage relief was abolished here more than a decade ago.
Jan 31 21:51:42 <spacecolonyone> that sucks
Jan 31 21:51:44 <fray> :)  Of course that, and local tax payments are the only thing I can deduct
Jan 31 21:52:09 <spacecolonyone> and then only if it is more than your std. deduction...
Jan 31 21:52:14 <fray> I'm just annoyed local tax payments which used to be 100%, are now closer to 75% deductible.. since the rules say it must be based on the "tax" amount, and just calling it a tax doesn't make it so..
Jan 31 21:52:29 <spacecolonyone> well, you could itemize but that would just be dumb
Jan 31 21:52:31 <fray> someone in the state of MN figured out only 75% of the "taxes" are really "taxes", the others are fees they call taxes..
Jan 31 21:52:37 <fray> (which just makes my head hurt)
Jan 31 21:53:07 <fray> mortgage interesting, vehicle taxes, and a few misc expenses means you have to itemize.. :(
Jan 31 21:57:09 <spacecolonyone> fray I didn't think you ever HAD to itemize deductions, you'd just be limiting yourself to the standard deduction?
Jan 31 21:57:21 <fray> well ya..
Jan 31 21:57:33 <fray> but generally mortgage interest makes it worth while
Jan 31 21:57:41 <fray> (or if you have kids)
Jan 31 21:58:59 <spacecolonyone> good heavens kids+phd! yikes.
Jan 31 22:27:03 <otwieracz> Hello.
Jan 31 22:27:33 <otwieracz> I'm writing bitbake rule for my application based on cmake.
Jan 31 22:28:20 <otwieracz> I want to put configuration files in /etc, but I don't know what destination directory I should provide in CMakeLists.txt
Jan 31 22:28:43 <otwieracz> When I install *.conf to "etc", configuration files go to /usr/etc.
Jan 31 22:29:17 <otwieracz> When I set /etc, bitbake tries to install them to my Linux /etc.
Jan 31 22:30:05 <otwieracz> So, how to install configuration files to /etc using bitbake and cmake?
Jan 31 22:36:55 <Jin^eLD> otwieracz: I think it's not really a bitbake problem; generally you'd "inherit cmake" in your recipe
Jan 31 22:37:23 <Jin^eLD> and your cmake scripts should be honoring whatever they support by default (like installation prefixes and so on)
Jan 31 22:39:05 <Jin^eLD> can't tell you anything specific regarding cmake though, besides that I have deep hate for it :) had to struggle with it when I was dealing with projects that were using this build system
Jan 31 22:39:47 <Jin^eLD> nevertheless, those do work in OE more or less "out of the box" with inherit cmake, if the cmake scripts themselves are ok
Jan 31 22:44:24 <otwieracz> Jin^eLD: Binaries are installed fine.
Jan 31 22:44:39 <otwieracz> Jin^eLD: Libraries also.
Jan 31 22:45:18 <otwieracz> But what I should pass to FILES_$PN to install /usr/etc/foo.conf to /etc?
Jan 31 22:45:23 <otwieracz> (or somethging)
Jan 31 22:45:33 <Jin^eLD> I thought that sysconfdir was in FILES_${PN} already
Jan 31 22:45:42 <Jin^eLD> check that with bitbake -e
Jan 31 22:46:04 <kergoth> his description is of an install problem, not a packaging problem
Jan 31 22:46:05 <Jin^eLD> if it's not there you can still do a FILES_${PN} += "${sysconfdir}/*" or something
Jan 31 22:46:06 <otwieracz> Im trygin with sysconfigdir.
Jan 31 22:46:17 <otwieracz> Hmm.
Jan 31 22:46:29 <kergoth> otwieracz's saying he can't get the files to get installed to ${D}/etc, not that they're going there and not being packaged
Jan 31 22:46:31 <kergoth> afaict
Jan 31 22:46:35 <Jin^eLD> indeed, actually, that's why I was pointing to a possible failure in the cmake scripts...
Jan 31 22:46:49 <otwieracz> Jin^eLD: It's possible
Jan 31 22:47:01 <nschle85> hello does anybody have an idea how to fix this ? http://norman-schleicher.de/jenkins/job/pandaboard-angstrom/29/console
Jan 31 22:47:03 <otwieracz> In cmake I'm only giving bin, lib and etc.
Jan 31 22:47:09 <kergoth> FILES isn't relevant given the nature of the issue. its either a problem in cmake.bbclass, or in the cmake scripts
Jan 31 22:47:13 * kergoth gets food
Jan 31 22:47:36 <otwieracz> And it looks like these names are expanded to /usr/bin, /usr/lib (fine) and that stupid /usr/etc.
Jan 31 22:48:48 <spacecolonyone> So where is the default kernel command line defined? I've found CMDLINE defined in recipes for things like the n900  but I've yet to find it for the beagleboard. I've never been confident in my uEnv.txt and I'd like to figure out how to make this happen as part of my image build.
Jan 31 22:49:35 <nschle85> spacecolonyone: i have panda not beagle
Jan 31 22:52:23 <spacecolonyone> :/
Jan 31 22:52:32 <spacecolonyone> :/
Jan 31 22:52:34 <spacecolonyone> grr
Jan 31 22:52:51 <spacecolonyone> :( 
Jan 31 22:53:47 <bluelightning> spacecolonyone: everything ok?
Jan 31 22:54:54 <spacecolonyone> lol. I was making the wrong face. But in other news, no. I can't get my display back and I haven't yet found the offending change in the diffs
Jan 31 22:57:01 <spacecolonyone> koen made a cryptic remark about "DSI PLL got fixed" right as I was talking about this over in #beagle then he vanished so I'm not sure if they are related
Jan 31 22:58:08 <otwieracz> So, anyone have idea?
Jan 31 23:01:02 <bluelightning> otwieracz: what's the problem?
Jan 31 23:01:16 <otwieracz> So, again… :)
Jan 31 23:01:27 <otwieracz> I'm writing bitbake recipe for my cmake based app.
Jan 31 23:01:34 <otwieracz> But I don't know how should I do:
Jan 31 23:01:53 <otwieracz> FILE(GLOB config "${CMAKE_CURRENT_SOURCE_DIR}/config/*.conf")
Jan 31 23:01:54 <otwieracz> INSTALL(FILES ${config} DESTINATION etc)
Jan 31 23:02:02 <otwieracz> To install it into OE's /etc.
Jan 31 23:02:13 <otwieracz> Beucase currently „etc” is expanded to „/usr/etc”
Jan 31 23:02:34 <otwieracz> (like bin and lib is expanded to /usr/bin and /usr/lib, but these are correct)
Jan 31 23:03:53 <Jin^eLD> otwieracz: I think you should ask someone who is familiar with cmake
Jan 31 23:04:21 <Jin^eLD> I would be able to help you if you were using autotools, but I have no clue about cmake, I had nothing but troubles with it
Jan 31 23:04:22 <bluelightning> I have a passing familiarity... have you looked at other examples?
Jan 31 23:04:25 <bluelightning> otwieracz: ^
Jan 31 23:05:02 <otwieracz> bluelightning: Seriously? I can not find in OE any cmake examples with configuration files in /etc.
Jan 31 23:05:32 <otwieracz> Jin^eLD: Last time I have to choose between autotools and cmake. And i choosen cmake :)
Jan 31 23:06:49 <Jin^eLD> otwieracz: my condolences ;)
Jan 31 23:07:01 <otwieracz> I heard that autotools are much harder to learn.
Jan 31 23:07:19 <Jin^eLD> otwieracz: I guess both can be a pain, depending on the use case
Jan 31 23:07:35 <otwieracz> Hmm.
Jan 31 23:07:37 <Jin^eLD> otwieracz: but I found them much more convenient, also in turms of user friendliness (i.e. users of your package)
Jan 31 23:07:42 <Jin^eLD> *terms
Jan 31 23:07:54 <Jin^eLD> I guess it comes down to taste (religion?) in the end :)
Jan 31 23:08:12 <otwieracz> Another question - is there any variable available in receipes pointing to this „virtual root” for package?
Jan 31 23:08:33 <Jin^eLD> ${D} is pointing to your virtual root of where your package stuff gets installed
Jan 31 23:08:59 <Jin^eLD> i.e. your recipe should install everything under ${D}/ - this stuff will get packaged
Jan 31 23:12:02 <otwieracz> Let's see...
Jan 31 23:16:06 <otwieracz> OK, another question.
Jan 31 23:16:12 <bluelightning> otwieracz: if it helps you can have a look in classes/cmake.bbclass to see how cmake gets called
Jan 31 23:16:14 <otwieracz> How to instlal files from /usr/share/xxxx/
Jan 31 23:16:15 <otwieracz> ?
Jan 31 23:16:25 <otwieracz> bluelightning: I've solved this mystery:
Jan 31 23:16:33 <otwieracz> EXTRA_OECMAKE += "-DPKGROOT=${D}"
Jan 31 23:16:41 <otwieracz> FILE(GLOB config "${CMAKE_CURRENT_SOURCE_DIR}/config/*.conf")
Jan 31 23:16:42 <otwieracz> INSTALL(FILES ${config} DESTINATION ${PKGROOT}/etc)
Jan 31 23:16:58 <bluelightning> ah right
Jan 31 23:17:05 <otwieracz> Now I have only to install files from /usr/share/myapp
Jan 31 23:17:15 <bluelightning>  /usr/share is represented by ${datadir}
Jan 31 23:17:21 <otwieracz> Thanks.
Feb 01 01:12:57 <XorA> ka6sox: worraworraworra
Feb 01 01:13:22 <ka6sox> orly!
Feb 01 01:14:10 <XorA> ka6sox: in bay area next week :-D
Feb 01 01:14:35 <ka6sox> okay I need to go there too...so lets try to connect for that Beer.
Feb 01 01:15:08 <XorA> will you be at ELC?
Feb 01 01:15:19 <ka6sox> yep
Feb 01 01:15:32 <XorA> think Im meeting koen sat before ELC for a beer
Feb 01 01:15:41 <XorA> at ELC venue
Feb 01 01:15:48 <ka6sox> okay, that sounds good
Feb 01 01:15:59 <XorA> my GF will be there also
Feb 01 01:17:04 * XorA is leaving on the Sunday :-(
Feb 01 01:17:28 <ka6sox> too bad you can't stay for ELC
Feb 01 01:17:45 <XorA> yeah, needs get back to work though
Feb 01 01:17:51 <ka6sox> know that one
Feb 01 01:18:01 <XorA> and I get to do round world flight for first time in lie
Feb 01 01:18:03 <XorA> life
Feb 01 01:32:14 <ka6sox> wow...not done that yet
Feb 01 01:32:28 <ka6sox> your GF must like that
Feb 01 01:41:01 <Russ> hooray elc
Feb 01 02:14:00 <XorA> ka6sox: GF is only joining me for bay area
Feb 01 02:14:06 <XorA> ka6sox: Im alone in Tokyo at moment :-D
Feb 01 02:14:16 <ka6sox> tokyo! oh my
Feb 01 02:14:43 <XorA> ka6sox: hence why I am awake and you are awake at same time :-D
Feb 01 02:14:52 <ka6sox> I was wondering
Feb 01 02:14:56 <ka6sox> we normally aren't
Feb 01 02:53:47 <otavio> gn people
Feb 01 02:53:49 <otavio> time to sleep
Feb 01 02:53:51 <otavio> ;-)
Feb 01 02:53:52 <otavio> cya
**** ENDING LOGGING AT Wed Feb 01 02:59:57 2012