Sunday, 2015-07-05

*** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC00:01
*** ][Sno][ <][Sno][!~sno@p578b540c.dip0.t-ipconnect.de> has joined #yocto00:17
*** [Sno] <[Sno]!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC00:17
*** ][Sno][ is now known as [Sno]00:17
*** LetoThe2nd <LetoThe2nd!~jd@s15387740.onlinehome-server.info> has quit IRC00:32
*** LetoThe2nd <LetoThe2nd!~jd@s15387740.onlinehome-server.info> has joined #yocto00:39
*** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has quit IRC01:03
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto01:16
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC01:20
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto03:16
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC03:21
*** ka6sox is now known as zz_ka6sox04:00
*** zz_ka6sox is now known as ka6sox04:01
*** staylor <staylor!~staylor@184.68.113.94> has joined #yocto04:33
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto05:17
*** bmcdorman <bmcdorman!~beta@c-67-186-1-18.hsd1.pa.comcast.net> has joined #yocto05:19
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC05:21
bmcdormanI have a question regarding PACKAGECONFIG usage. I’ve read the documentation in the manual, but the concept still doesn’t quite make sense to me. I’m trying to configure qt5 to build with support for directfb. Inside their recipe, they have a line that reads like this “PACKAGECONFIG[directfb] = ….” Is simply enabling directfb in my DISTRO_FEATURES enough to “pull in” this packageconfig directive? Or is there something else05:24
bmcdormanhave to do to enable this option? Am I missing the point entirely?? :P05:24
*** staylor <staylor!~staylor@184.68.113.94> has quit IRC05:25
*** Limo <Limo!d8503c84@gateway/web/freenode/ip.216.80.60.132> has joined #yocto06:33
*** Limo <Limo!d8503c84@gateway/web/freenode/ip.216.80.60.132> has quit IRC06:34
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto06:37
*** macbug <macbug!~macbug@c83-248-164-111.bredband.comhem.se> has joined #yocto07:01
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC07:03
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto07:06
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto07:18
*** ambrosius <ambrosius!~textual@c-76-21-79-185.hsd1.ca.comcast.net> has joined #yocto07:22
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC07:23
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC07:26
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto07:31
*** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has joined #yocto07:40
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC07:41
*** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has joined #yocto07:51
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto07:51
*** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has quit IRC08:21
*** ambrosius <ambrosius!~textual@c-76-21-79-185.hsd1.ca.comcast.net> has quit IRC08:34
*** ambrosius <ambrosius!~textual@c-76-21-79-185.hsd1.ca.comcast.net> has joined #yocto08:35
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC08:46
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:59
*** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has joined #yocto09:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:09
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto09:09
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC09:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:09
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto09:14
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto09:19
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC09:20
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto09:22
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC09:24
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC09:27
*** roric <roric!~roric@h196n19-vrr-a31.ias.bredband.telia.com> has quit IRC09:44
*** ambrosius <ambrosius!~textual@c-76-21-79-185.hsd1.ca.comcast.net> has quit IRC10:16
*** ffff_ <ffff_!56a35902@gateway/web/freenode/ip.86.163.89.2> has joined #yocto10:20
ffff_Hi all. I am new to Yocto and need some help building a new image.10:20
ffff_I started with fsl-image-multimedia-full and added multiple package groups to that such as X, SSH, build essentiola, etc. However I dont think it is possible for me to add all that I would need in future.10:21
ffff_Therefore I would like the built image to be able to use already available software repos such as the one from fedora/ubuntu.10:22
ffff_I need some advice on how I can do that.10:22
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto10:56
*** dshwang <dshwang!~dshwang@134.134.139.74> has quit IRC11:35
*** timsche <timsche!~quassel@port-92-192-17-30.dynamic.qsc.de> has joined #yocto11:44
*** dshwang <dshwang!~dshwang@192.55.54.40> has joined #yocto11:47
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:58
*** ddom <ddom!~ddom@ip-37-24-103-185.hsi14.unitymediagroup.de> has quit IRC13:17
*** ddom <ddom!~ddom@ip-37-24-103-185.hsi14.unitymediagroup.de> has joined #yocto13:18
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has joined #yocto13:30
*** kw01f <kw01f!~kw01f@x5d87531c.dyn.telefonica.de> has joined #yocto13:41
*** timsche <timsche!~quassel@port-92-192-17-30.dynamic.qsc.de> has quit IRC14:16
*** Crofton <Crofton!~balister@pool-71-171-12-54.nwrknj.east.verizon.net> has quit IRC14:29
*** Crofton <Crofton!~balister@pool-71-171-12-54.nwrknj.east.verizon.net> has joined #yocto14:43
*** kw01f <kw01f!~kw01f@x5d87531c.dyn.telefonica.de> has quit IRC15:02
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC15:04
bluelightningffff_: you can't really do that practically15:05
*** Aethenelle <Aethenelle!~Aethenell@107.138.98.226> has joined #yocto15:05
ffff_ns?bluelightning: Any suggesstio15:05
Croftonffff_, you need to make your own package feeds or look at an OE based distribution that provides package feeds such as Angstrom15:07
bluelightningffff_: we have a wealth of recipes for software now in additional layers - see http://layers.openembedded.org (click "Recipes" to search / browse)15:07
bmcdormanSince it’s a more reasonable hour now: I have a question regarding PACKAGECONFIG usage. I’ve read the documentation in the manual, but the concept still doesn’t quite make sense to me. I’m trying to configure qt5 to build with support for directfb. Inside their recipe, they have a line that reads like this “PACKAGECONFIG[directfb] = ….” Is simply enabling directfb in my DISTRO_FEATURES enough to “pull in” this packageconf15:08
bmcdormandirective? Or is there something else I have to do to enable this option? Am I missing the point entirely??15:08
ffff_Crofton: Thanks I will take a look. So these distributions have pre-built packages for ARM architecture I assume.15:10
ffff_bluelightning: Thanks. So if I need a new packge, I can just built the package using bitbake and install it?15:10
*** kw01f <kw01f!~kw01f@x5d87531c.dyn.telefonica.de> has joined #yocto15:18
kergothbmcdorman: read the value of the PACKAGECONFIG variable (not the flag, the value, see the = or ?= of PACKAGECONFIG itself). if it has logic to set itself default based on DISTRO_FEATURES, then you know eanbling the distro feature is enough, if not, it's not15:22
bmcdormankergoth: Cool. Does bitbake detect that the package needs to be rebuilt if the DISTRO_FEATURES change and the package has already been built?15:23
*** Aethenelle <Aethenelle!~Aethenell@107.138.98.226> has quit IRC15:25
bmcdormanI suppose it’s easy to test :-P Will try it out15:27
kergothbitbake checksums the metadata. any change to a variable used by a task will re-run that task and every task that depends on that task, recursively15:30
bmcdormankergoth: Cool. Thanks!15:34
kergothbmcdorman: it's worth noting, though, that in the past at times things got unhappy in an existing tmpdir when changing distro or distro features, i'm guessing not everything would get cleaned out that needed to be. if you run into weird build problems after changing distro features, you might want to wipe tmp and try again15:37
kergothnot sure if thats still the case, but just so you're aware15:37
bmcdormankergoth: Yeah, I used bitbake about 3.5 years ago and my experience taught me not to trust anything it does :-P. It seems like things have improved dramatically since then, though. I’ll be sure to check that.15:39
kergothyeah, it's rather more deterministic than it used to be, less likely to do something inexplicably, though that doesn't always mean it does what you want, just what you told it to do :)15:40
*** alimon <alimon!~alimon@134.134.139.74> has quit IRC16:25
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC16:32
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto16:39
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC16:40
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:40
*** kw01f <kw01f!~kw01f@x5d87531c.dyn.telefonica.de> has quit IRC17:24
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto17:31
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC17:37
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC17:46
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto17:47
*** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has joined #yocto17:56
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto18:06
*** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC18:30
*** ffff_ <ffff_!56a35902@gateway/web/freenode/ip.86.163.89.2> has quit IRC18:46
*** kw01f <kw01f!~kw01f@x5d87531c.dyn.telefonica.de> has joined #yocto18:52
*** dddddd <dddddd!56a35902@gateway/web/freenode/ip.86.163.89.2> has joined #yocto19:25
ddddddI used hob to add more packages to a minimul image19:26
ddddddAnd built it successfully with hob.19:26
-YoctoAutoBuilder- build #387 of eclipse-plugin-juno is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-juno/builds/38719:27
ddddddHowever it does not create the sdimage, so I guess I need to invoke bitbake again from the same terminal after closing hob.19:28
ddddddbut which image name should I use?19:28
-YoctoAutoBuilder- build #386 of eclipse-plugin-kepler is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-kepler/builds/38619:32
-YoctoAutoBuilder- build #372 of buildtools is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/buildtools/builds/37219:33
ddddddAlso, do the created RPM content included in the SD image?Or should they be installed seperately?19:35
-YoctoAutoBuilder- build #154 of eclipse-plugin-luna is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/eclipse-plugin-luna/builds/15419:36
-YoctoAutoBuilder- build #370 of nightly-intel-gpl is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-intel-gpl/builds/37019:36
-YoctoAutoBuilder- build #388 of poky-tiny is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/poky-tiny/builds/38819:37
-YoctoAutoBuilder- build #372 of nightly-qa-extras is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/37219:38
-YoctoAutoBuilder- build #382 of nightly-non-gpl3 is complete: Success [build successful CheckForGPLv3] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/38219:49
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC19:57
-YoctoAutoBuilder- build #377 of nightly-oecore is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-oecore/builds/37719:58
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC19:58
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-ktgvmnlhhlbxsbnv> has joined #yocto19:59
-YoctoAutoBuilder- build #375 of nightly-qa-logrotate is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/37519:59
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto20:02
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto20:03
-YoctoAutoBuilder- build #376 of nightly-qa-pam is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-pam/builds/37620:08
-YoctoAutoBuilder- build #31 of ptest-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/ptest-x86-64/builds/3120:09
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-ktgvmnlhhlbxsbnv> has left #yocto20:09
-YoctoAutoBuilder- build #376 of nightly-qa-skeleton is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/builds/37620:21
*** kw01f <kw01f!~kw01f@x5d87531c.dyn.telefonica.de> has quit IRC20:25
-YoctoAutoBuilder- build #376 of nightly-qa-systemd is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/37620:35
-YoctoAutoBuilder- build #31 of ptest-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/ptest-x86/builds/3120:43
-YoctoAutoBuilder- build #376 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/37620:52
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto21:12
*** Crofton|work <Crofton|work!~balister@pool-71-171-12-54.nwrknj.east.verizon.net> has quit IRC21:14
-YoctoAutoBuilder- build #380 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/builds/38021:15
*** Crofton <Crofton!~balister@pool-71-171-12-54.nwrknj.east.verizon.net> has quit IRC21:15
*** grma <grma!~gruberm@HSI-KBW-46-237-193-133.hsi.kabel-badenwuerttemberg.de> has quit IRC21:21
*** Crofton|work <Crofton|work!~balister@pool-108-44-116-228.ronkva.east.verizon.net> has joined #yocto21:28
*** Crofton <Crofton!~balister@pool-108-44-116-228.ronkva.east.verizon.net> has joined #yocto21:28
*** likewise_ <likewise_!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC21:37
-YoctoAutoBuilder- build #382 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/38221:37
-YoctoAutoBuilder- build #37 of nightly-rpm-non-rpm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm-non-rpm/builds/3721:41
*** dddddd <dddddd!56a35902@gateway/web/freenode/ip.86.163.89.2> has quit IRC21:43
-YoctoAutoBuilder- build #371 of nightly-fsl-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/37121:53
*** ambrosius <ambrosius!~textual@c-76-21-79-185.hsd1.ca.comcast.net> has joined #yocto21:56
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto22:01
-YoctoAutoBuilder- build #380 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/38022:01
-YoctoAutoBuilder- build #377 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/37722:04
*** vdehors <vdehors!~vincent@LAubervilliers-656-1-235-184.w193-248.abo.wanadoo.fr> has quit IRC22:05
*** vdehors <vdehors!~vincent@LAubervilliers-656-1-235-184.w193-248.abo.wanadoo.fr> has joined #yocto22:05
-YoctoAutoBuilder- build #381 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/38122:08
*** mago__ <mago__!~mago@88.131.56.168> has quit IRC22:12
-YoctoAutoBuilder- build #370 of nightly-ipk is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/37022:15
*** orzen <orzen!~orzen@h180n2-ld-c-a31.ias.bredband.telia.com> has quit IRC22:21
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC22:24
-YoctoAutoBuilder- build #379 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/37922:35
*** mago__ <mago__!~mago@88.131.56.168> has joined #yocto22:38
-YoctoAutoBuilder- build #365 of nightly-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/36522:50
-YoctoAutoBuilder- build #38 of nightly-deb-non-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/3822:50
-YoctoAutoBuilder- build #369 of nightly-rpm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/36922:52
*** zecke <zecke!~ich@ip5b41fb99.dynamic.kabel-deutschland.de> has quit IRC22:59
-YoctoAutoBuilder- build #382 of nightly-mips is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/38223:01
-YoctoAutoBuilder- build #380 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/38023:02
-YoctoAutoBuilder- build #374 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/37423:05
-YoctoAutoBuilder- build #366 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/36623:09
-YoctoAutoBuilder- build #372 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/37223:13
-YoctoAutoBuilder- build #379 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/37923:25
*** nighty-_ <nighty-_!~nighty@hokuriku.rural-networks.com> has quit IRC23:39
*** ambrosius <ambrosius!~textual@c-76-21-79-185.hsd1.ca.comcast.net> has quit IRC23:43
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC23:47
-YoctoAutoBuilder- build #381 of nightly-world is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/38123:48
-YoctoAutoBuilder- build #101 of nightly-world-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world-lsb/builds/10123:52

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!