IRC log for #oe on 20160710

01:46.38*** join/#oe DJW|Home (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net)
03:20.17*** join/#oe Nilesh_ (uid116340@gateway/web/irccloud.com/x-oflaqwrfeaokwsot)
05:55.06*** join/#oe evanmeagher (~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net)
06:12.15*** join/#oe evanmeagher (~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net)
06:15.13*** join/#oe dv__ (~quassel@62.178.118.86)
06:16.34*** join/#oe wenzong (~wfan@106.120.101.38)
08:05.07*** join/#oe ao2 (~ao2@cl-35.trn-01.it.sixxs.net)
08:41.20*** join/#oe phdeswer_ (~phdeswer@91-159-55-220.elisa-laajakaista.fi)
08:43.52*** join/#oe florian (~fuchs@Maemo/community/contributor/florian)
08:54.11*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
08:54.11*** join/#oe moto-timo (~ttorling@fsf/member/moto-timo)
08:54.11*** join/#oe armpit (~akuster@2601:202:4001:9ea0:d936:bf98:12e5:c256)
08:54.11*** join/#oe NightMonkey (~NightMonk@pdpc/supporter/professional/nightmonkey)
08:54.11*** join/#oe cjp256 (~cjp256@chrispatterson.net)
08:54.11*** join/#oe otavio (~otavio@debian/developer/otavio)
08:54.11*** join/#oe johang (~johan@188.166.67.59)
08:54.11*** join/#oe muep__ (twingo@otitsun.oulu.fi)
08:54.11*** join/#oe marex-cloud (sid137234@gateway/web/irccloud.com/x-pasaylrqctysbkvg)
08:54.11*** join/#oe gus (~quassel@2401:1801:7800:101:be76:4eff:fe18:1911)
08:54.11*** join/#oe georgem (~georgem@216-21-169-52.slc.googlefiber.net)
08:54.12*** join/#oe fabo (~fabo@linaro/fabo)
08:54.12*** join/#oe gabrbedd (~beddingfi@li680-65.members.linode.com)
08:54.12*** join/#oe KNERD (~KNERD@2604:a880:1:20::9b:4001)
08:54.12*** join/#oe heeen (heeen@endboss.org)
08:54.12*** join/#oe dos1 (~dos1@unaffiliated/dos1)
08:54.12*** join/#oe flynn378 (sid63564@gateway/web/irccloud.com/x-swwirupczlrsiclz)
08:54.13*** join/#oe Crofton (~balister@pool-71-171-10-138.ronkva.east.verizon.net)
08:54.13*** join/#oe vdehors (~vdehors@bob75-2-81-56-46-209.fbx.proxad.net)
08:54.13*** join/#oe RP (~richard@5751f4a1.skybroadband.com)
08:54.13*** join/#oe sgw_ (~sgw_@134.134.139.77)
08:54.13*** join/#oe koen (~koen@ip4da29576.direct-adsl.nl)
08:54.13*** join/#oe fischerm (~mfischer@207-114-172-147.static.twtelecom.net)
08:54.13*** join/#oe ndec_ (~ndec@linaro/ndec)
08:54.13*** join/#oe pidge (~pidge@ns367664.ip-188-165-216.eu)
08:54.13*** join/#oe zoli_ (zoli_@gateway/shell/linaro/x-gfbrqejwmeobomys)
09:31.21*** join/#oe hrw (~hrw@redhat/hrw)
09:32.02*** join/#oe bottazzini__ (~realBigfo@192.55.54.45)
10:00.21*** join/#oe realBigFoot (~realBigfo@192.55.54.45)
13:04.28*** join/#oe ao2 (~ao2@cl-35.trn-01.it.sixxs.net)
13:25.09*** join/#oe phdeswer_ (~phdeswer@91-159-55-220.elisa-laajakaista.fi)
14:11.11*** join/#oe snowkidind (~textual@pool-96-255-207-158.washdc.fios.verizon.net)
14:13.17snowkidindgreetings
14:14.29*** join/#oe jbrianceau_away (uid10952@gateway/web/irccloud.com/x-jhoaupbprmtrizxs)
14:14.46snowkidindI am working on a project using c++ and a graphics library called opencv. My end product is an embedded system that processes video streams. Is there a recommended GUI library that I should be using?
14:15.59snowkidindit would be nice if I could develop for the gui on my computer first before going to embedded, it would also be nice to build for something that is compatible from the get go.
15:51.08*** join/#oe snowkidind (~textual@pool-96-255-207-158.washdc.fios.verizon.net)
16:05.21*** join/#oe josep (~josep@c-3b1ae455.010-118-73746f7.cust.bredbandsbolaget.se)
16:58.15*** join/#oe armpit (~akuster@2601:202:4001:9ea0:6ce8:588a:7616:ca9)
17:06.01*** join/#oe JaMa (~martin@ip-89-176-104-169.net.upcbroadband.cz)
17:23.46*** join/#oe snowkidind (~textual@pool-96-255-207-158.washdc.fios.verizon.net)
17:53.50*** join/#oe jku (~jku@dyj170ycrv18---3wlh9y-3.rev.dnainternet.fi)
18:13.50*** join/#oe evanmeagher (~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net)
18:42.10*** join/#oe sgw_ (~sgw_@134.134.139.77)
19:04.42*** join/#oe paulg (~paulg@70.52.193.89)
19:10.59*** join/#oe jeroen (~jeroen@5ED6B7F1.cm-7-7c.dynamic.ziggo.nl)
19:13.07jeroenhi, today I tried to speed up our ci server a bit by copying the sstate directory to the freshly checkout one.. but it does rebuild glibc-initial and as a consequence almost everything....
19:14.04jeroenis there a) some way to get info why bitbake thinks it needs to be rebuild?
19:14.19jeroenb) a better way to move sstate instead of copying it?
19:33.34*** join/#oe flo_lap (~fuchs@Maemo/community/contributor/florian)
19:44.22kergothjeroen: you don't need to copy sstate at all, just point at it with SSTATE_MIRRORS
19:44.42kergothand if it's rebuilding, use bitbake -S printdiff <target> to see why, if the info is available
19:50.09jeroenkergoth: thanks
19:50.27jeroenkergoth: this doesn't work export SSTATE_MIRRORS=/media/data/autobuild/venus-jethro-cortexa8hf/build/sstate-cache/
19:50.42kergoththat's not how SSTATE_MIRRORS works, read the yocto project documentation
19:50.49kergoth1. that var is set in local.conf, nto the env
19:50.50jeroenkergoth: better to put it in local.conf?
19:50.53kergoth2. that's the wrong sytnax for that variable entirely
19:53.00jeroenkergoth: should it error if the syntax is incorrect? anyway, trying again..
19:53.23kergothagain, read the docs if you want to use the variable, what you just showed will fail, because the syntax is wrong
19:59.18jeroenkergoth: the main sstate will rebuild occasionally so I guess I do want to have a copy..
20:04.50kergoth?
20:05.35kergoththe first thing worth noting is sstate is cumulative. if you aren't clearing it out or wiping it periodically, it'll just keep adding more sstate to the sstate dir. it's completely harmless to share a single sstate dir amongst a ton of product versions, machines, distros, etc
20:09.47jeroenkergoth: pfffff I give up for now, can't get this to work, can't get toaster working ..... :(
20:16.27jeroenkergoth: I know you trust sstate, I don't, more then I would like cleanall "fixes" things...
20:17.33kergothmost likely you're misdiagnosing the problem, and it was the clean, not the sstate removal, that was the factor
20:17.47kergothtons of us runs 10s of builds a day across 4 different yocto releases and never hit such a problem
20:17.51jeroenwhat i would like to have is a (weekly?) rebuild of all, and incremental builds on a copy of its sstate
20:18.20kergoththat's a common way to do it, yes
20:20.59jeroenkergoth: well as said, I am going to give up for now, the problem is the incremental build rebuilds everything again ... :(
20:52.29*** join/#oe yann (~yann@nan92-1-81-57-214-146.fbx.proxad.net)
21:04.22*** join/#oe khem (~khem@unaffiliated/khem)
21:32.56*** join/#oe snowkidind (~textual@pool-96-255-207-158.washdc.fios.verizon.net)
22:06.39*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
23:13.32*** join/#oe paulg (~paulg@209.226.41.163)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.