Wednesday, 2016-03-16

aboseleyCan I use yocto recipes to build application software for my desktop linux distro, in addition to my embedded distro?00:06
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto00:08
*** jdanderson <jdanderson!~janderson@> has quit IRC00:10
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC00:12
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC00:13
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC00:18
*** bottazzini <bottazzini!realBigfoo@nat/intel/x-pqwcrvygtunqqdtl> has joined #yocto00:33
*** rtollert_ <rtollert_!~rtollert@> has joined #yocto00:36
*** rtollert <rtollert!~rtollert@> has quit IRC00:39
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC00:45
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto00:51
*** vmeson <vmeson!> has joined #yocto00:56
*** vmesons <vmesons!> has quit IRC00:57
*** paulg_ <paulg_!> has joined #yocto01:11
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto01:13
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto01:22
*** sjolley <sjolley!sjolley@nat/intel/x-ijwzmtkfazimjqfj> has quit IRC01:42
*** MWelchUK <MWelchUK!> has quit IRC01:49
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC01:50
*** vmesons <vmesons!> has joined #yocto01:51
*** vmeson <vmeson!> has quit IRC01:51
*** coolmouse <coolmouse!~coolmouse@> has joined #yocto01:54
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC01:54
*** sjolley <sjolley!sjolley@nat/intel/x-nrlcmjgklwriafht> has joined #yocto01:59
*** MWelchUK <MWelchUK!> has joined #yocto02:01
*** morphis_ <morphis_!> has joined #yocto02:03
*** morphis <morphis!> has quit IRC02:07
*** sjolley <sjolley!~sjolley@> has joined #yocto02:17
*** rdenis <rdenis!sid16562@gateway/web/> has quit IRC02:19
*** rdenis <rdenis!sid16562@gateway/web/> has joined #yocto02:20
*** alimon <alimon!> has joined #yocto02:28
*** ka6sox is now known as zz_ka6sox02:44
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto02:47
*** mbergek <mbergek!> has joined #yocto02:51
*** mbergek <mbergek!> has quit IRC02:53
*** sjolley <sjolley!~sjolley@> has quit IRC02:56
*** paulg_ <paulg_!> has quit IRC03:03
*** aboseley <aboseley!~aboseley@> has quit IRC03:08
*** sjolley <sjolley!sjolley@nat/intel/x-fcclvsapnjlgiesx> has joined #yocto03:09
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto03:12
*** redengin <redengin!> has quit IRC03:42
*** redengin <redengin!~redengin@2601:600:9200:181:4845:6258:b235:aa3f> has joined #yocto03:43
*** seebs <seebs!> has quit IRC03:49
*** coolmouse <coolmouse!~coolmouse@> has quit IRC03:53
*** seebs <seebs!> has joined #yocto03:54
*** simonl <simonl!uid6729@gateway/web/> has quit IRC03:56
*** alimon <alimon!> has quit IRC03:59
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC03:59
*** sa2ajj <sa2ajj!> has joined #yocto04:19
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC04:41
*** CharlesC <CharlesC!6031a5f3@gateway/web/freenode/ip.> has joined #yocto04:55
*** CharlesC <CharlesC!6031a5f3@gateway/web/freenode/ip.> has quit IRC04:58
*** sjolley <sjolley!sjolley@nat/intel/x-fcclvsapnjlgiesx> has quit IRC05:00
*** sjolley <sjolley!sjolley@nat/intel/x-bkyrlhnkwserscqz> has joined #yocto05:46
*** helio|afk is now known as heliocastro05:48
*** sjolley <sjolley!sjolley@nat/intel/x-bkyrlhnkwserscqz> has quit IRC05:49
*** sjolley <sjolley!~sjolley@> has joined #yocto05:50
*** sjolley <sjolley!~sjolley@> has joined #yocto05:52
*** sno <sno!> has quit IRC06:06
*** sno <sno!> has joined #yocto06:08
*** agust <agust!> has joined #yocto06:13
*** mattsm <mattsm!uid128834@gateway/web/> has quit IRC06:41
*** pohly <pohly!> has joined #yocto06:46
*** obsrwr <obsrwr!~otp-amois@> has quit IRC06:57
*** coolmouse <coolmouse!~coolmouse@> has joined #yocto06:59
*** marek_ <marek_!> has joined #yocto07:02
*** obsrwr <obsrwr!~otp-amois@> has joined #yocto07:03
*** obsrwr <obsrwr!~otp-amois@> has quit IRC07:08
*** obsrwr <obsrwr!~otp-amois@> has joined #yocto07:10
*** nico_ <nico_!> has joined #yocto07:13
*** nico_ <nico_!> has joined #yocto07:13
*** obsrwr <obsrwr!~otp-amois@> has quit IRC07:13
*** AndersD <AndersD!> has joined #yocto07:16
*** egavinc <egavinc!> has quit IRC07:19
*** obsrwr <obsrwr!~otp-amois@> has joined #yocto07:21
*** frsc <frsc!> has joined #yocto07:23
*** obsrwr <obsrwr!~otp-amois@> has quit IRC07:26
*** t0mmy <t0mmy!~tprrt@> has joined #yocto07:27
*** Ulfalizer <Ulfalizer!~ulf@> has quit IRC07:29
*** obsrwr <obsrwr!~otp-amois@> has joined #yocto07:30
*** jku <jku!jku@nat/intel/x-qnzanfqspqpdkuld> has joined #yocto07:31
*** obsrwr <obsrwr!~otp-amois@> has quit IRC07:34
*** egavinc <egavinc!> has joined #yocto07:34
*** Kakadu <Kakadu!4fad4e8c@gateway/web/freenode/ip.> has joined #yocto07:35
*** obsrwr <obsrwr!~otp-amois@> has joined #yocto07:36
*** yann|work <yann|work!> has quit IRC07:43
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto07:49
*** CTtpollard <CTtpollard!> has joined #yocto07:55
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto07:57
KakaduHey, folks07:59
*** CTtpollard <CTtpollard!> has joined #yocto07:59
KakaduI have some noobish kernel compilation issues. Who want to get some Stackoverflow points?
*** jbrianceau_away is now known as jbrianceau08:03
*** mihai <mihai!~mihai@> has joined #yocto08:06
LetoThe2ndKakadu: in short: the old kernelconfig isnt' compatible. you're forwarding over about 45 version,s you knwo?08:06
KakaduYeah, I agree that there were a lot of changes08:07
LetoThe2ndKakadu: my advice would be, manually make the kernel compile with your toolchain again, using oldconfig and then iterating.08:07
LetoThe2ndKakadu: the error message generally points into the arm machine config, which has changed massively during the 3.0-3.10 era (board files towards dt)08:08
LetoThe2ndso you're in for a real lot of work anyways.08:08
*** diego_r <diego_r!> has joined #yocto08:08
Kakadu> manually make the kernel compile with your toolchain again, using oldconfig and then iterating.08:09
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC08:09
KakaduCan you rephrase?08:09
KakaduDo you mean that I need to try to compiler kernel with old 2.6.39 config without bitbake and stuff?08:09
LetoThe2ndKakadu: explanation prior to DT, any board had an individual, unique number to identify it, which the bootloader passed to the kernel. then, based on that number, the kernel selected the appropriate board config file. this is strongly discouraged now, and probably also doesn't work anymore properly.08:09
*** diego_r <diego_r!> has quit IRC08:10
LetoThe2ndKakadu: so if you want to do things right, you need not only to come up with a new kernel, but also a fitting DTB08:10
LetoThe2ndKakadu: yes, basically i mean that. take your compiler, and try to manually, without bb and oe build a working configuration. then reintegrate that back08:11
KakaduDTB==Device tree block?08:11
LetoThe2nddevice tree blob08:11
Kakaduah, I mean t that08:11
KakaduOK, thanks!08:11
LetoThe2ndgood luck.08:12
*** toscalix <toscalix!~agustinbe@> has joined #yocto08:12
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:16
*** ziggo <ziggo!~ziggo@> has joined #yocto08:21
*** townxelliot <townxelliot!~ell@> has joined #yocto08:21
*** roccof <roccof!> has joined #yocto08:28
*** simonl <simonl!uid6729@gateway/web/> has joined #yocto08:32
*** leon-anavi <leon-anavi!~leon@> has joined #yocto08:37
*** sameo <sameo!samuel@nat/intel/x-xitfubkucactuopb> has joined #yocto08:37
*** boucman_work <boucman_work!~boucman@> has joined #yocto08:37
*** ant_work <ant_work!> has joined #yocto08:38
*** rburton <rburton!> has joined #yocto08:38
*** sameo <sameo!samuel@nat/intel/x-xitfubkucactuopb> has quit IRC08:41
*** sameo <sameo!samuel@nat/intel/x-guyetrjquwjxzukf> has joined #yocto08:41
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto08:42
*** sameo <sameo!samuel@nat/intel/x-guyetrjquwjxzukf> has quit IRC08:48
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC08:50
*** CTtpollard <CTtpollard!> has quit IRC08:56
*** CTtpollard <CTtpollard!> has joined #yocto08:56
*** AndersD <AndersD!> has quit IRC09:05
*** sameo <sameo!~samuel@> has joined #yocto09:05
*** morphis_ <morphis_!> has quit IRC09:08
*** ziggo <ziggo!~ziggo@> has quit IRC09:10
*** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto09:10
*** morphis <morphis!> has joined #yocto09:12
*** matteo <matteo!~matteo@openwrt/developer/matteo> has quit IRC09:14
*** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto09:16
*** AndersD <AndersD!> has joined #yocto09:21
*** ziggo <ziggo!~ziggo@> has joined #yocto09:25
*** psnsilva_ <psnsilva_!> has joined #yocto09:28
*** Kakadu <Kakadu!4fad4e8c@gateway/web/freenode/ip.> has quit IRC09:29
*** belen <belen!~Adium@> has joined #yocto09:31
*** grma <grma!~gruberm@> has joined #yocto09:33
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-rclmebcowxnvtjex> has joined #yocto09:33
*** NMI <NMI!~Nicolas@> has joined #yocto09:33
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-rclmebcowxnvtjex> has left #yocto09:33
*** NMI <NMI!~Nicolas@> has quit IRC09:38
*** NMI <NMI!~Nicolas@> has joined #yocto09:39
*** Snert <Snert!> has quit IRC09:42
*** NMI <NMI!~Nicolas@> has quit IRC09:44
*** nicolas_m <nicolas_m!~Nicolas@> has joined #yocto09:45
*** jonathanmaw <jonathanmaw!> has joined #yocto09:45
*** coolmouse <coolmouse!~coolmouse@> has quit IRC09:47
*** JaMa <JaMa!> has quit IRC09:50
nicolas_mHi, do you know if there is a channel dedicated to meta-raspberry ? I see that 6 days ago, the rpi3 support has been added into the master branch but the generated image failed to start on a rpi3 (stucked on the screen displaying 3 raspberrys).09:52
*** zero_note <zero_note!~zero_note@> has joined #yocto09:53
*** ziggo <ziggo!~ziggo@> has quit IRC10:01
*** coolmouse <coolmouse!~coolmouse@> has joined #yocto10:11
*** ziggo <ziggo!~ziggo@> has joined #yocto10:13
*** Noor <Noor!~quassel@> has quit IRC10:17
*** awaisb <awaisb!~quassel@> has quit IRC10:19
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC10:23
*** belen <belen!~Adium@> has quit IRC10:25
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto10:26
*** clement__ <clement__!~clement@> has joined #yocto10:30
*** Noor <Noor!~quassel@> has joined #yocto10:32
*** abelal <abelal!~quassel@> has joined #yocto10:37
*** AndersD <AndersD!> has quit IRC10:50
*** AndersD <AndersD!~anders@> has joined #yocto10:51
*** yann|work <yann|work!> has joined #yocto11:00
*** JaMa <JaMa!> has joined #yocto11:03
*** sameo <sameo!~samuel@> has quit IRC11:09
*** edbart <edbart!~ebartosh@> has joined #yocto11:18
*** sameo <sameo!samuel@nat/intel/x-zzlltjpmtoqfkler> has joined #yocto11:28
*** ziggo <ziggo!~ziggo@> has quit IRC11:28
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hwtktteoqpexosap> has joined #yocto11:29
*** boucman_work <boucman_work!~boucman@> has quit IRC11:33
*** jonathanmaw_ <jonathanmaw_!> has joined #yocto11:33
*** berton <berton!~fabio@> has joined #yocto11:36
*** jonathanmaw <jonathanmaw!> has quit IRC11:37
*** jonathanmaw <jonathanmaw!> has joined #yocto11:37
*** Snert <Snert!> has joined #yocto11:37
*** jonathanmaw_ <jonathanmaw_!> has quit IRC11:40
*** maxin <maxin!~maxin@2001:998:22:0:448e:c743:de24:2153> has quit IRC11:49
*** AndersD <AndersD!~anders@> has quit IRC11:52
*** ant_work <ant_work!> has quit IRC11:55
*** ant_work <ant_work!> has joined #yocto11:58
*** maxin <maxin!~maxin@> has joined #yocto12:02
zero_notehi folks, on the same build machine (ubuntu 14.04.4, gcc 4.8.4) I've cloned 2 git repos: one for my yocto project and the latter is the u-boot repo, so I bitbake the sdk, install it and source it, but I can't compile u-boot due to an error related to a missing tool12:03
zero_notearm-poky-linux-gnueabi-ld: cannot find -lgcc12:03
zero_notebut I can't understand why the same u-boot source code compile with no problems using yocto recipes, while when I try to compile "manually" u-boot I get this error12:03
zero_noteanyone have any clue about this?12:03
*** ziggo <ziggo!~ziggo@> has joined #yocto12:06
*** AndersD <AndersD!> has joined #yocto12:08
*** maxin <maxin!~maxin@> has quit IRC12:09
*** ftonello <ftonello!> has joined #yocto12:10
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto12:13
Anticomzero_note: maybe it's missing in your sdk?12:16
*** grma <grma!~gruberm@> has quit IRC12:18
Anticomzero_note: also try installing gcc-multilib on your host12:18
*** Ulfalizer <Ulfalizer!~ulf@> has joined #yocto12:21
*** belen <belen!~Adium@> has joined #yocto12:22
*** frsc <frsc!> has quit IRC12:25
*** jchonig <jchonig!> has quit IRC12:32
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC12:32
*** caiortp <caiortp!~inatel@> has joined #yocto12:34
*** maxin <maxin!~maxin@> has joined #yocto12:39
Ulfalizeri have a recipe that dynamically extends PACKAGES in do_package_prepend() with d.prependVar("PACKAGES", "{} ".format(pkg)) inside a loop. i tried disabling the 'build-deps' QA check for each new package by adding d.appendVar("INSANE_SKIP_{}".format(pkg), "build-deps"), but it seems to have no effect. any idea why?12:39
*** dv_ <dv_!> has quit IRC12:40
*** dv_ <dv_!> has joined #yocto12:41
Ulfalizerputting  INSANE_SKIP_<pkg> = "build-deps"  for each package at the top level works, but is no longer dynamic12:41
Ulfalizermaybe there could be sstate-related issues later too, but i want to figure out this step first12:41
*** boucman_work <boucman_work!~boucman@> has joined #yocto12:43
*** jchonig <jchonig!> has joined #yocto12:48
*** frsc <frsc!> has joined #yocto12:51
*** AndersD <AndersD!> has quit IRC12:51
*** AndersD <AndersD!~anders@> has joined #yocto12:52
*** marek_ <marek_!> has quit IRC12:53
*** Marex <Marex!~Marex@> has quit IRC12:53
*** marek_ <marek_!> has joined #yocto12:55
*** AndersD <AndersD!~anders@> has quit IRC12:56
*** vmesons <vmesons!> has quit IRC13:01
*** Marex <Marex!~Marex@> has joined #yocto13:02
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto13:03
AnticomUlfalizer: have you set ?13:06
*** AndersD <AndersD!> has joined #yocto13:13
*** paulg_ <paulg_!~paulg@> has joined #yocto13:14
UlfalizerAnticom: yup, it's set13:16
*** maxin <maxin!~maxin@> has quit IRC13:17
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hwtktteoqpexosap> has left #yocto13:21
*** maxin <maxin!~maxin@> has joined #yocto13:21
zero_noteAnticom: my sdk is ok, I use it to compile the kernel with no problems, why are you think about gcc-multilib?13:22
Anticomzero_note: just read it somewhere on SO13:22
*** grma <grma!~gruberm@> has joined #yocto13:22
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC13:24
Anticomzero_note: 1st comment13:24
*** vmesons <vmesons!~rmacleod@> has joined #yocto13:26
*** fledermaus <fledermaus!~vivek@> has joined #yocto13:26
zero_noteAnticom: thanks, I'll try (actually I can't apt-get install on my build-machine due to restricted permissions), next time I'll googling more deeply ;-)13:28
*** vmeson <vmeson!~rmacleod@> has joined #yocto13:39
*** vmesons <vmesons!~rmacleod@> has quit IRC13:39
*** dmoseley <dmoseley!> has quit IRC13:43
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:45
*** vmesons <vmesons!~rmacleod@> has joined #yocto13:48
*** grma_ <grma_!~gruberm@> has joined #yocto13:48
*** grma <grma!~gruberm@> has quit IRC13:48
*** ziggo <ziggo!~ziggo@> has quit IRC13:49
*** lamego <lamego!~jose@> has joined #yocto13:50
*** vmeson <vmeson!~rmacleod@> has quit IRC13:51
*** lamego <lamego!~jose@> has quit IRC13:52
*** lamego <lamego!~jose@> has joined #yocto13:53
zero_noteAnticom: gcc-multilib does not seems to fix the problem, I suppose that is not a so much unexpected thing, because as I said before, the same source compile with no problem using yocto recipes13:54
Anticomzero_note: maybe checking, what 'bitbake -e <target> | less' yields might give you any clues on some environment stuff you're missing in your build13:55
zero_noteAnticom: LD and LDFLAGS seem quite different in u-boot run.do_compile and in my build env14:07
Anticomzero_note: there you go :)14:08
zero_noteAnticom: I expected that sourcing the sdk would give me the same env14:08
Anticomdunno. never used a bb populated sdk yet. I'm fairly new to yocto myself14:09
zero_noteme too :)14:09
*** madisox <madisox!~madison@> has joined #yocto14:12
*** edbart1 <edbart1!~ebartosh@> has joined #yocto14:13
*** edbart <edbart!~ebartosh@> has quit IRC14:14
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto14:21
*** ftonello <ftonello!> has quit IRC14:33
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC14:36
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:46
*** ftonello <ftonello!> has joined #yocto14:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto14:55
*** AndersD <AndersD!> has quit IRC14:58
*** belen1 <belen1!Adium@nat/intel/x-vvvnvsuqpmsoioea> has joined #yocto15:02
*** belen <belen!~Adium@> has quit IRC15:03
*** janderson <janderson!~janderson@> has joined #yocto15:03
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC15:07
*** nico_ <nico_!> has quit IRC15:13
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto15:17
*** frsc <frsc!> has quit IRC15:18
*** marek_ <marek_!> has quit IRC15:23
*** jku <jku!jku@nat/intel/x-qnzanfqspqpdkuld> has quit IRC15:23
*** riz__ <riz__!4a69aefe@gateway/web/freenode/ip.> has joined #yocto15:25
riz__Hello. I am new to Yocto and see great value in its use. I have read all of the documentation over and over but have a few beginner questions and I was wondering if this is the place I can maybe get some help.15:27
rburtonit sure is15:28
boucman_workriz__: yes, that's probably the place, but this is IRC so the answer might take some time to come15:28
riz__Not a problem. I understand15:28
riz__To begin, I am having trouble understanding the process of getting started. I am using the minnowboard and would like to get my feet wet by building a yocto image to load on the board. I have done it successfully with both core-image minimal and sato, but the process was not fully understood. I just followed documentation and it worked. Now I am trying to understand it.15:30
*** wenzong <wenzong!~wfan@> has quit IRC15:30
Anticomriz__: so what steps exactly don't you understand? the concepts & terms like layers or recipes take some time to really settle. Took me like 3 weeks or so :>15:31
*** wenzong <wenzong!~wfan@> has joined #yocto15:31
riz__My question is the following. Is Poky build system (located at git://, poky-jethro-14.0.1.tar.bz2) going to be thwe base to every project?15:31
rburtonpoky is an example, and what we use for QA purposes15:31
riz__This is where I get really confused.15:32
rburtonyou can use poky as a base, or just use bitbake + oe-core + meta-intel15:32
*** bottazzini <bottazzini!realBigfoo@nat/intel/x-pqwcrvygtunqqdtl> has quit IRC15:32
Anticompoky basically is a refference distro to get you jump started15:32
rburtonpoky is just bitbake + oe-core + meta-yocto, squashed into a single repo15:32
Anticomif i'm not mistaken :P15:32
Anticomrburton: am i?15:33
rburtonyou can use it to get jump started if you wish15:33
belen1riz__: using Toaster, the web UI, might help understanding the bits that come into play. Might… not guaranteed ;)15:33
riz__So, you are saying that bitbake + oe-core + meta-intel is the bare minimum needed for any x86 build?15:33
rburtonno, toaster is a UI15:33
rburtonentirely optional15:33
rburtonoe-core + bitbake is the core you'll always use15:34
rburtonif you're using minnowboard you'll need meta-intel too15:34
riz__yes, and meta-intel is for my specific platform15:34
riz__Now, what are those considered? layers?15:34
Anticomthat's where the understanding of layers is important15:34
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC15:34
Anticomso the layers just encapsulate certain abstraction levels15:34
Anticomat the core there are the bsp (board support layers) layers, basically defining the hardware you're compiling for15:35
Anticomand then you start 'layering' functionality / abstractions on top15:35
riz__Is the combination of bitbake + oe-core + meta-intel called my "build system"?15:35
Anticombitbake is the build system. It parses the recipes and figures out what has to be build how and in what order15:36
Anticomoe-core is just a big collection of recipes that are commonly used15:36
riz__Ahhh, BSP's. That is my next point of confusion.15:36
Anticome.g. the recipe base-files is (more or less) just creating folders like for example /tmp in your rootfs15:37
riz__I am seeing Intel-corei7-64. Does that have to be included in the build?15:37
Anticomdunno about x86 recipes. we're using arm :)15:37
riz__referring to intel-corei7-64-4.0-jethro-2.0.tar.bz215:37
riz__Well, ingeneral, do I have to include some sort of BSP?15:38
Anticomwell if you're buid successfuly runs on your target then it's included somewhere on the way. You can run 'bitbake -e <target> | less' and inspect what's going on there. Also 'bitbake -u depexp -g <target>' is useful to find out what depends on what15:39
AnticomMoreover one of the most valuable tools to me, to figuring stuff out is
riz__Well, now I am going to start from scratch and build a light image for my specific use15:40
Anticomthere you can search for layers, recipes and machines15:40
Anticomand get useful information about things15:40
riz__So, I am wondering if I need to download one of the BSPs on yocto's site15:40
riz__OK. Ill check that out too15:40
Anticomriz__: You could start with core-image-minimal, add your own layer and start adding the stuff you need in your image15:41
riz__OK. Sounds like a good plan. Is core-image-minimal included in bitbake?15:41
riz__OR do I need to download the poky reference buyild system?15:42
rburtoncore-image-minimal is part of oe-core15:42
Anticomnot entirely sure but i think it's part of poky15:42
riz__OK great15:42
rburtontherefore its in poky15:42
riz__So I will start bith just building  bitbake + oe-core + meta-intel and seeing if I can boot that.15:43
*** dmoseley <dmoseley!> has joined #yocto15:43
*** benjamirc <benjamirc!besquive@nat/intel/x-aqrefxwrmsierxqu> has joined #yocto15:43
riz__core-image-minimal provides just a command line, correct? No GUI?15:44
Anticomrburton: different topic: I've removed alsa from DISTRO_FEATURES but i still see alsa-utils being build. bitbake -e <image> however didn't mention alsa-utils **anywhere**. Also i can't find it in the final running system. I suppose it's still being build but not installed in the rootfs. Any clues why it's still being build then?15:44
rburtonAnticom: spurious dependency somewhere.  if you use distro_features_check you can make it forcibly refuse to build without the alsa feature and that will give you a dependency chain15:45
Anticomokay thanks15:46
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto15:46
Anticomriz__: yes15:47
Anticomat least i can't see any graphical stuff there15:47
boucman_workAnticom: bitbake -g -u depexp <your image> might help15:47
riz__Now that I will not use Poky, do I just creat a folder called "MinnowboardTest" for example and include  bitbake + oe-core + meta-intel in there?15:48
Anticomalsa-utils shows up in depexp. However i can't dig straight down from our image target. -g does populate 'regular' dot-files right? Which one do i need to render an image that contains the alsa-utils package?15:51
Anticomis it
kergothi woudln't advise rendering them at all15:52
kergoththey end up so massive you can't find anything15:52
kergothgrep them15:52
kergothor as boucman_work says, use depexp15:52
Anticomkergoth: directly went to grepping15:53
boucman_workyeah, I use them as text files, never as images :P15:53
boucman_work(I think there is another deps explorer called goggle, but i'm not sure. havn't tested it)15:54
AnticomI like pretty drawings tho ;)15:54
Anticomboucman_work: nah, goggle is for building15:54
boucman_workyou'd better like heavy zooming and following very long lines :P15:54
Anticom"enlarge, enhance... enlarge, enhance... enlarge, enhance" :D15:54
riz__Or does the file structure of my project not matter?15:55
Anticomriz__: somewhat15:55
Anticome.g. having the layer folders being named meta-* is just a convention afaik15:55
Anticomhowever even conventions are made for sticking to them15:55
*** belen1 <belen1!Adium@nat/intel/x-vvvnvsuqpmsoioea> has quit IRC15:55
riz__so I just make a project folder and all the layers go inside that?15:56
Anticomriz__: we just have our layer in a repo15:56
Anticomdunno whether that's the usual way of doing it15:57
*** belen <belen!~Adium@> has joined #yocto15:57
riz__So where does the build folder go?15:57
riz__And where does the final image end up?15:58
Anticomwe got a little shell script, that clones oe-core and adds our layer to set up the development environment. I'm fairly new to yocto aswell and as i said i'm not really sure what the best way of doing things actually is15:58
rburtonriz__: if you're just starting out i'd recommend poky + meta-intel tarball releases, then you save some of the hassle of setup15:58
*** frsc <frsc!> has joined #yocto15:58
Anticomriz__: it's all in the manual ;)15:59
Anticomyou said you've read it :p15:59
riz__Yeah, I see it for poky, but i'm wondering if the structure remains the same for a custom system15:59
Anticomrburton: hm, strange... cat | grep -F -- '-> "alsa-utils"' is only giving me "alsa-utils" -> "alsa-utils" [style=dashed]15:59
riz__Again, the manuals are quite large and remembering everything is a challeng15:59
Anticomor am i looking the wrong way arround?16:00
Anticomriz__: correct16:00
Anticomit's in tmp/deploy/image/[MACHINE]/16:00
*** alimon1 <alimon1!alimon@nat/intel/x-smovjvormgxbuyvw> has quit IRC16:01
*** ant_work <ant_work!> has quit IRC16:01
*** lamego <lamego!~jose@> has quit IRC16:01
*** lamego <lamego!~jose@> has joined #yocto16:02
*** belen <belen!~Adium@> has quit IRC16:02
*** belen <belen!~Adium@> has joined #yocto16:02
AnticomAlso that's a question i've asked myself a couple of times now... Why do packages depend on themselves?16:03
rburtonAnticom: make it break and see what happens16:03
rburtonthat's possibly it showing the relationship between binary and source?16:03
*** sjolley <sjolley!~sjolley@> has quit IRC16:03
AnticomI've seen that for quite some packages now16:03
*** boucman_work <boucman_work!~boucman@> has quit IRC16:04
riz__My next concern is I want to be able to devlop a Qt GUI to use on my board. Is this done by simply including meta-q5 as a layer as I did with meta-intel?16:04
kergothafaik pn-depends is pretty naive. if it's going by packages, then packages within a recipe dep on one another, and if it's going by task, the same is true16:04
*** sjolley <sjolley!~sjolley@> has joined #yocto16:04
kergothshould probably clean it up16:04
*** ziggo <ziggo!> has joined #yocto16:04
kergothseebs: do you happen to know of a good way to process input linewise in shell without using 'read', since it tends to mangle the spaces?16:08
kergothmaybe i should just use python for this script :)16:08
Anticomkergoth: #bash :p16:08
kergothyeah, i'm pestering seebs shamelessly cause he wrote a book on portable shell scripting :P16:08
Anticomi just know about while read -r line...done < <(xyz)16:09
kergothyeah, thats what i usually do too. -r fixes the line continuation stuff, but it can still swallow leading/trailing spaces and whatnot16:09
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC16:10
Anticomkergoth: maybe ... done < <(xyz | ack my.ack) to sanatize what xyz is spitting out?16:10
kergothoh, i'll just avoid being portable, use bash, and set IFS to newline with a for loop16:10
kergothaside: is quite interesting and cringe-worthy16:11
Anticomor rewrite your script in brainfuck to really annoy some people would be another nice alternative lol16:11
*** sjolley <sjolley!~sjolley@> has quit IRC16:13
riz__I see that meta-intel layer says it is compatible with yocto version 1.5 on the website. What are they referring to when saying yocto version 1.5?16:13
*** mattsm <mattsm!uid128834@gateway/web/> has joined #yocto16:13
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto16:14
Anticomthey're probably refering to bb,
rburtonno, not bitbake at all16:15
Anticomoh, never knew that16:15
rburtonbitbake is 1.29 or something now16:15
rburtonjust for extra confusion, poky has different release numbers to oe-core16:15
Anticomso yocto version is just a combo of poky and bb versions?16:15
rburton(what with poky predating oe-core)16:15
rburtonpoky is a combination of oe-core and bitbake, and gets its own version16:15
rburtoncurrent oe-core release is 2.0 aka jethro16:16
*** Ulfalizer <Ulfalizer!~ulf@> has quit IRC16:16
*** nicolas_m <nicolas_m!~Nicolas@> has quit IRC16:16
rburton1.5 would be aka dora, and is pretty old now16:16
rburton(one release every six months)16:16
Anticomwe're on jethro16:17
* Anticom proud16:17
* rburton ignores that 1.9 was skipped16:17
Anticomhow come i never notice such things16:17
riz__IF I am not using poky then what does that matter?16:17
riz__I am confused16:17
rburtonit doesn't :)16:17
riz__so which meta-intel do I use?16:18
rburtonliterally nobody really cares about the poky release number16:18
riz__Just the latest release?16:18
riz__What about meta-qt5? Is that all I need to develop Qt applications on yocto?16:19
riz__So, I then just take my Qt5 application that is developed on my host and install it in the root of the target bosrd and it should run?16:19
rburton should be the right bsp release for minnowboard16:20
* rburton just uses git clones and finds it a lot easier16:20
riz__Or do I still need to include all the Qt libraries?16:20
rburtonriz__: you'll need to include the libraries - adding a layer doesn't magically make the image contain the binaries16:20
riz__Thanks. That is the one I was going to use16:20
rburtonwrite a recipe for your application to build it, and then put the resulting package in your image16:20
rburtonthat will pull in the right libraries automatically16:21
riz__So where does the mata-toolchain-qt5 come into play?16:22
rburtonignore that16:22
riz__That confused the hell out of me16:22
riz__'So then what is that?16:22
rburtonanything that says meta-toolchain is obsolete16:22
rburtonif you want to develop for the target on your host, then you can build a custom SDK16:22
rburtonmeta-toolchain was the precursor to that16:22
rburtonby develop i mean build binaries and so on but without using bitbake or oe directly16:23
riz__So onvce I inculude the meta-q5 layer and build yocto I should be able to use QtCreator to setup a kit to point to the required compilers and debuggers that were made from my yocto build?16:23
riz__I do want to develop on my host. Then I just want to deploy it on the board with my yocto image16:24
riz__I feel that is easiest16:24
*** coolmouse <coolmouse!~coolmouse@> has quit IRC16:27
rburtonyou want to write a recipe so you can build from your sources inside bitbake16:28
rburtonits certainly easy to do development inside an ide but you want to have a recipe too16:28
riz__That is the part I dont understand.16:28
riz__If I am developing in Qt Creator, how to UI build from the source inside of bitbake?16:28
riz__how do I build*16:29
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC16:30
*** ant_work <ant_work!> has joined #yocto16:31
rburtonyou point your recipe at the sources, wherever they are16:31
riz__And if I build my GUI from QtCreator, is it still necessary to inslude meta-qt5 in by yocto build?16:31
Anticomriz__: to put it into a simple perspective: Image consists of layers. Layers contain recipes. A recipe usually pulls from  a source repository and builds/provides 1 or more packages that then get installed to your image when you add them to IMAGE_INSTALL of your image16:31
rburtonif you're doing serious development then you might find it easier to start by adding all the qt libraries to your image, and then using qtcreator to build stuff and copy it over.16:31
Anticomor did i get something fataly wrong there ross?16:31
rburtonwhen you're a bit more stable you can have a recipe that pulls from your git repo or whatever and builds it to make proper packages16:32
riz__I see16:32
riz__For some reason I assumed meta-qt5 included the libraries16:32
*** sjolley <sjolley!sjolley@nat/intel/x-ufznxsikrdrkpgke> has joined #yocto16:32
riz__And that was its purpose16:33
riz__So regardless of my method, I need meta-q5 recipe in my yocto build, correct?16:33
rburtona layer just provides a source of packages, it doesn't build anything simply by adding it16:34
Anticomnot quite. You need your own layer and recipes inside them16:34
seebskergoth: I don't really know of anything. read is the closest there is, and yeah, it has issues.16:34
*** frsc <frsc!> has quit IRC16:34
*** amcgee7 <amcgee7!~amcgee7@> has joined #yocto16:35
kergothseebs: k, figured that might be the case, just wanted to see if you knew of anything obvious off the top of your head :)16:35
riz__And the most basic recipe is just a local.conf and bblayers.conf file correct?16:36
riz__Basically, is that what is meant by a recipe?16:36
kergothlocal.conf and bblayers.conf are configuration for your build directory, that's not a recipe in any way shape or form16:36
kergothrecipes are .bb files in layers16:36
Anticomriz__: no, .conf are configuration files16:36
riz__Oh yes, sorry16:37
*** alimon1 <alimon1!~alimon@> has joined #yocto16:38
Anticommkdir meta-mylayer; cd poky; source oe-init-build-env; bitbake-layers add-layer "path/to/meta-mylayer"16:38
Anticom^^^ riz__16:38
riz__So to develop in QtCreator, I need to make an SDK in my yocto build?16:38
Anticomdunno about graphical stuff but i guess it's best to test the visual stuff in quemu hence i'd build it using bitbake and do the qemu thing16:39
riz__When I built core-image-sato-sdk I saw a folder in my host root directory "opt/poky". I was wondering what that was.16:40
riz__opt/poky/1.6.3 to be more specific16:41
rburtonthats where the sdk ends up, /opt/poky/1.6.3/16:42
Anticomwell you COULD use the sdk but IMHO it's easier to let bitbake handle the environment setup and stuff. Moreover you should be able to simply run runquemu quemux86 after building and get your development in an emulator16:42
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto16:42
Anticomusing emulators only gets impractical if you need to interface with some hardware16:43
rburton1.6.3 is pretty old, please use 2.0 if you can16:43
Anticomat least i wasn't able to find a proper solution to that yet16:43
riz__What do you mean by "let bitbake handle the environment"? That is where I get really confused.16:44
Anticomriz__: after all you're cross-compiling. This requires a lot of environment setup if you're doing anything more complex than a hello world16:45
riz__The SDK allows me to point to the required compilers and debuggers in opt/poky. HJow else would you do it?16:45
Anticomlet bitbake compile your source16:46
Anticomfrom how i understood it the SDK is meant to be shipped to 3rd party devs but not for your actual development16:47
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto16:47
riz__Is the SDK built from meta-qt5 being included?16:48
Anticomagain: meta-qt5 is just a layer16:48
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC16:49
riz__So what do I need for the sdk?16:50
*** ant_work <ant_work!> has quit IRC16:51
*** belen <belen!~Adium@> has quit IRC16:51
Anticomriz__: you can populate an sdk using bitbake -c populate_sdk <image>16:54
Anticombut YOU don't neccesarily need it for development.16:55
*** grma_ <grma_!~gruberm@> has quit IRC16:55
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has joined #yocto16:56
riz__So how would I develop in QtCreator without the SDK?16:56
*** yann|work <yann|work!> has quit IRC16:57
riz__Just develop for gereric linux using the default kit?16:57
Anticomriz__: use QTCreator as source file editor and bitbake as compiler16:58
Anticomto put it this way16:58
Anticomas i said, i never did graphics stuff with yocto. that's just how i would do it. dunno whether there's a better way16:59
*** belen <belen!~Adium@> has joined #yocto16:59
riz__So I cna bitbake individual components without bitbaking the entire yocto build?17:00
CTtpollardbitbake -e $Package17:00
Anticomusually bitbake is smart enough to figure out, what has changed and only rebuild the neccessary stuff17:00
Anticomso you don't have to wait hours and hours every time17:01
riz__And this way the application is built into my image, correct?17:01
riz__In other words, I would not have to transfer the application over to my board?17:01
Anticomas long as you're having a recipe that tells bitbake how to actually build your source and tell it to install it into your image, then yes17:02
Anticomatm i'm just copying the final image bitbake spits out to an sd card, put that into my target and boot it17:02
riz__OK. Are there any examples of this I can study?17:02
riz__OK great17:03
riz__Thanks. I have a lot of work to do. I will go play around and try to wrap my head around everything I learned today. Thanks guys. This was gold!17:03
*** bzb <bzb!> has joined #yocto17:03
*** bzb <bzb!> has quit IRC17:05
Anticomriz__: after getting some information about the basics from my personal experience it's best to tinker arround. Nothing teaches you more. If you've got some specific questions on some topic, you can always come back here17:05
riz__I have read all those, but there are many components and different ways of doing the same thing so I wasnt sure the proper direction17:05
riz__This helped clear things up17:05
riz__Thanks Anticom!17:05
Anticomyou're welcome riz__17:06
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6853:f279:59ff:fe64:3a8> has quit IRC17:10
*** paulg_ <paulg_!~paulg@> has quit IRC17:14
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC17:16
*** jbrianceau is now known as jbrianceau_away17:17
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto17:18
*** jonathanmaw <jonathanmaw!> has quit IRC17:20
Anticomgrrrr i don't get it. I've explicitly installed connman (with plugin-loopback and plugin-ethernet) and put a config to /etc/systemd/network/foo.network17:22
AnticomBut still systemd won't automatically start sshd.service (- sshd.socket is fine -) and my interface won't configure17:22
AnticomAny ideas how to track down the problem?17:22
kergothadding won't do anything unless you enable systemd-networkd, afaik17:23
kergothconnman doesn't use that at all, you configure that with connmanctl17:23
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has joined #yocto17:23
Anticomkergoth: i thought i either needed connman **or** networkd17:24
kergothyou do17:24
kergoth but you installed connman and then added a config file for networkd :P17:24
*** maxin <maxin!~maxin@> has quit IRC17:24
Anticomkergoth: so is there a way to live with connman alone?17:24
kergothyes, configure connman17:24
kergothgoogle how to do so17:24
Anticomkergoth: i'm always just getting main.conf when i google for how to configure connman17:25
rburtonconfigure connman is almost an oxymoron17:25
rburtonif it finds wired ethernet it brings it up17:25
Anticommy current connman settings just got  [global]OfflineMode=false and [Wired] Enable=true and Tethering=false17:25
*** psnsilva_ <psnsilva_!> has quit IRC17:25
rburtonwifi you need to configure once to associate, obviously17:25
Anticomkergoth: wiki says about wired connections: "ConnMan will automatically handle wired connections."17:26
kergothindeed. or if you want to use static rather than dhcp, or presumably if you want to use usb cdc networking17:26
Anticomkergoth: and this can only be achived via connmanctl? like how would i incorporate this in my build process17:27
kergothi had to configure connman with connmanctl when i wanted to use usb networking with my boneblack17:27
Anticomit's the same static ip for every device shipped17:27
kergothAnticom: as the wiki says, the settings end up in /var/lib/connman17:27
Anticomkergoth: I've got a 'settings' file laying arround there with the content i've mentioned17:27
Anticomi wasn't able to find a synopsis of how to configure a static ip for connman in that file17:28
Anticomthey're all just talking about connmanctl17:28
Anticomeven this doesn't tell it:
*** riz__ <riz__!4a69aefe@gateway/web/freenode/ip.> has quit IRC17:28
kergothyes, you'd use connmanctl to configure a static ip as well, and it writes files into /var/lib/connman17:28
kergothso presumably you'd just ship those17:28
kergothnot that difficult, just very different from how you configure other networking tools17:29
kergothmight be easier to just enable networkd ;)17:29
* kergoth isn't a big fan of connman, really.. sometimes useful, but a pain to set up for non-common-cases17:29
Anticomkergoth: could you paste a valid config file configuring a static ip please?17:29
kergothyou can't take 5 minutes to run connmanctl yourself and look?17:29
kergothi don't havea  board handy17:29
Anticomand i just took connman-client out of my bulid again haha17:29
Anticomcheers anyway17:29
kergothah. haha17:30
Anticomso are there any drawbacks of using networkd?17:30
*** mihai <mihai!~mihai@> has quit IRC17:30
kergothnot sure, i haven't used it enough to say, maybe someone else in here knows17:30
Anticomand networkd replaces connman right?17:30
kergothit's its own thing, yeah. no need for both, afaik17:31
Anticomwhere is that damn networkd recipe again?17:33
Anticomi just can't find it17:33
kergoththere is no recipe, it's part of systemd17:34
kergothjust enable the packageconfig for it17:35
kergoth106:PACKAGECONFIG[networkd] = "--enable-networkd,--disable-networkd"17:35
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has quit IRC17:37
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC17:37
Anticomkergoth: would i do that in a systemd_%.bbappend?17:37
Anticomor would i write a custom ?17:38
kergotheasier to do it from your distro .conf or local.conf if temporary17:38
kergothPACKAGECONFIG_append_pn-systemd = " networkd"17:38
Anticombtw why do i need the _pn there?17:38
kergothbecause thats what the override is17:38
kergothsystemd is the PN of the recipe17:38
Anticomso tl;dr; is 'because'17:38
kergothsee the OVERRIDES variable17:38
kergothpn-${PN} is in there17:38
*** t0mmy <t0mmy!~tprrt@> has quit IRC17:39
kergothno, it's because that's what's in OVERRIDES. _append_<some override> is applied when <some override> is in OVERRIDES17:39
Anticomkergoth: And where would i put a config to /etc/systemd/network/ then if i only enable it in my local.conf?17:39
kergothin this case we prepend pn- to avoid conflicts in the namespace17:39
kergothi.e. 'linux' can be both a recipe and a target os17:39
Anticomah, i see17:39
kergoththis *did* bite us in the past :)17:39
kergothyou'd need to add it to a recipe, either to systemd itself or create a new recipe to ship the configuration17:40
kergoththe latter being cleaner17:40
Anticomkergoth: and if i had a new recipe anyway i could also do the packageconfig there i guess17:40
kergothone recipe can't change another17:41
kergothyour new recipe cant' change how systemd builds17:41
kergothcreate a distro, optionally including another, in the distro you add your configuration to your images by adding it to DISTRO_EXTRA_RRECOMMENDS and change the systemd config17:42
kergothIMO that's the best approach, but as with everything else in yocto, there are many ways to do it17:42
Anticomkergoth: btw wouldn't += be more appropriate even for PACKAGECONFIG_append ?17:43
*** ftonello <ftonello!> has quit IRC17:43
*** ulf` <ulf`!~ulf@> has quit IRC17:43
Anticomwhat if someone want's to append some other config?17:44
kergothi don't understand the question17:44
Anticomwouldn't that discard the first one17:44
kergoth_append is an operator17:44
kergothlike += and .=, only lazy17:44
kergothit's cumulative17:44
AnticomPACKAGECONFIG_append_pn-systemd = " networkd" >>>>>> PACKAGECONFIG_append_pn-systemd += " networkd"17:44
kergothevery _append is applied17:44
*** leon-anavi <leon-anavi!~leon@> has quit IRC17:44
Anticomare you sure?17:44
kergoththe only difference between those two lines is the += added your space for you17:44
kergothGiven I wrote bitbake's recipe parser when we started the project, yes, i'm pretty sure17:45
Anticomi thought PACKAGECONFIG_append_pn-systemd was a "regular" variable17:45
Anticomrburton: can you please confirm this?17:45
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC17:45
kergothare you kidding?17:45
Anticomkergoth: someone just told me the other way arround17:45
Anticomnot that i wouldn't trust you, sorry17:45
kergothagain, i was one of the founders of the project, and co-wrote the bitbake user manual17:45
Anticomkergoth: is this maybe different for other _append vars?17:46
kergothno, it's not17:46
Anticomdunno who told me += was better. I'd have to check the irc logs17:46
kergothusing += and _append together is pointless and redundant.17:46
Anticombut thank's for pointing that out17:46
kergothusing += *instead* of _append when appropriate makes a lot of sense, as there's no point using the lazy operation if you don't need it17:47
kergothbut it's the only way to use an override to append conditionally, so it's your only option in this case17:47
Anticomkergoth: i thought the XYZ_append vars where regular vars untill the point XYZ was actually evaluated17:47
kergothnope, when it's parsed they're added to a list of appends17:47
*** ftonello <ftonello!> has joined #yocto17:47
kergoththen when expanded in recent bitbake, or at the end of parsing in old bitbake, they're all appended17:47
Anticomto what list?17:47
Anticomnow i'm confused again17:47
kergothFOO_append = "bar"; FOO_append = "baz" -> FOO now has a list of appends including bar and baz17:48
kergothwhicha re then applied when you get the value of FOO17:48
kergothhence, lazy, postponed operation, not immediate at prse time like .= and +=17:48
Anticomokay got it17:48
Anticomthanks again for pointing that out17:49
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto17:49
Anticomhad a wrong assumption from back when i was told differently17:49
kergothsorry if i came off a bit harsh, but this is in the bitbake manual as an operator, part of the syntax :)17:50
Anticomkergoth: stating that it was a "regular" variable made kind of sense to me17:50
kergothoverride versions of a variable are a regular variable until the override is applied17:51
kergothperhaps thats where teh confusion set in17:51
kergothoverrides, not append/prepend17:51
Anticomwasn't there _remove too?17:52
kergothi.e. do_install and do_install_arm. the latter is just a variable named do_install_arm unless arm is in OVERRIDES, at which point it replaces do_install and do_install_arm goes away17:52
Anticomi guess that one is immediate too17:52
kergoththere is, yes17:52
Anticomokay got it17:52
kergothit's like append and prepend, cumulative and postponed17:52
Anticomso do_install_arm_append just applies to do_install_arm (and that immediatley) and afterwards becomes do_install?17:53
kergoth_append is never immediate, but other than that, yes, that's correct17:53
kergothwhich is why _<override>_append and _append_<override> are very different things17:53
Anticomjesus christ17:53
Anticomkergoth: could you in theory expand this indefinetly? like _append_append ?17:54
kergothFOO_append_override conditionally appends to FOO. FOO_override_append will append to FOO_override, which then *replaces* FOO, so the latter replaces existing values in FOO if FOO_override is undefined17:54
kergoththat woudln't do anything, no. _append_append would append when 'append' is in OVERRIDES17:54
Anticomso it becomes an OVERRIDE automatically?17:54
Anticomlike one override and one _append/_remove is all you can have17:54
*** pedraza <pedraza!86868b4a@gateway/web/freenode/ip.> has joined #yocto17:55
kergothmultiple overrides are handled specifically17:55
kergothbut again, append/prepend/remove is an *operator*17:55
kergothit's handled at parse time17:55
*** zero_note <zero_note!~zero_note@> has quit IRC17:55
Anticomlearned quite a lot in the past few minutes17:55
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto17:55
Anticomfeel like i've got a master degree in bitbakery now lol17:56
kergoththink of append/prepend/remove as just a bad syntax for a similar operation to +=/.=/=+/=., just lazy and their syntax allows for the override. we shouldn't have used _ as the separator for overrides, as it's also allowed in variable names, and we shouldnt' have used _append/_prepend/_remove as operators when the syntax differs so much from the other operators17:57
kergothbut it's a tad too late tod o much about it now unless we add a new recipe format :)17:57
Anticomkergoth: is there a common policy with breaking changes in major releases?17:58
Anticomeven if it's just on the schedule for the long run, it still might make sense to change if breaking changes are allowed for majors17:58
*** belen <belen!~Adium@> has quit IRC17:58
Anticomhm but that would make it impossible to have _append_override17:59
kergothsome breaking changes do go in at major releases, at times with a deprecation for one release cycle. richard has done so before18:00
kergothi.e. the syntax of getVar() and getVarFlag(), the expand parameter was optional, now it's mandatory, so in a future major release we can change the default to be expanded rather than unexpanded18:00
kergothwe haven't done much with the file format yet, though. we'd need to either be fully backwards compatible, or add a file format version to the format, or use a new extension, mos tlikely18:01
Anticomoh before i forget: I was wondering just the other day, whether there's a "nice" nfs server solution in yocto. Do you know anything on that topic?18:01
kergothnot sure on that one, sorry. about the only time i use nfs is an occasional nfsroot with a server already running nfs and tftp servers, or once a blue moon with qemu18:02
Anticomkergoth: i just gave it a quick google and saw, that there's a userspace implementation of a nfs server in py. Made me wonder, whether it would be possible to implement some convenience stuff like runquemu18:03
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC18:03
kergothnote that richard is the architect, breaking changes are his forte, i haven't done much with the core in many years, he'd make the call on any chnages to the file format or behavior over time18:03
kergothit would be nice if runqemu ran the nfsroot server on its own, if it doesn't now18:03
Anticomkergoth: so he's the brain behind bitbake?18:03
kergoththere are a few folks with deep bitbake knowledge nowadays, paul, richard, etc, but he's the project lead and architect, yes. he took over as maintainer after i left and made massive improvements, it's his baby now :)18:04
kergothi'd really like to see runqemu arrange for automatic package feed configuration, pointing at the tmp/deploy/ feeds18:04
kergothso you could runqemu, then drop in and install new packages with opkg or smart or whatever directly18:04
Anticomkergoth: i know literally nothing about virtualization with quemu18:04
AnticomI really need to take a closer look at this to understand what's going on. Maybe i might be able to contribute then one day18:05
*** toscalix <toscalix!~agustinbe@> has quit IRC18:06
*** matteo <matteo!~matteo@openwrt/developer/matteo> has quit IRC18:11
*** ftonello <ftonello!> has quit IRC18:15
*** raykinsella78 <raykinsella78!~rkinsell@> has joined #yocto18:17
*** ziggo <ziggo!> has quit IRC18:17
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto18:21
*** ftonello <ftonello!> has joined #yocto18:24
*** roccof <roccof!> has quit IRC18:26
*** dv_ <dv_!> has quit IRC18:27
*** dv_ <dv_!> has joined #yocto18:29
*** JaMa <JaMa!> has quit IRC18:29
*** pohly <pohly!> has quit IRC18:33
*** townxelliot <townxelliot!~ell@> has quit IRC18:34
*** Anticom <Anticom!~timo.m@> has quit IRC18:35
*** berton <berton!~fabio@> has quit IRC18:35
*** bluelightning <bluelightning!> has joined #yocto18:39
*** bluelightning <bluelightning!> has quit IRC18:39
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:39
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has joined #yocto18:42
*** raykinsella78 <raykinsella78!~rkinsell@> has left #yocto18:42
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC18:42
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto18:42
*** edbart1 <edbart1!~ebartosh@> has quit IRC18:43
*** edbart <edbart!~ebartosh@> has joined #yocto18:44
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC18:44
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has quit IRC18:49
*** ftonello <ftonello!> has quit IRC18:49
*** Capso <Capso!~closed@about/networking/> has joined #yocto18:51
CapsoI have a gumstix overo fire with tobi board running yocto. I've tried to attach a multiple port powered USB hub to the USB port on the tobi board and a SATA USB drive to the USB hub, but the yocto image on the gumstix only picks up the USB hub and not the devices - how can I mount the USB drive on the gumstix so I can use it?18:53
kergothRP: should i re-submit shallow git mirror tarball support as an rfc or patch series? it will need careful review. shouldn't impact anything when it's not enabled, afaik18:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has joined #yocto19:01
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto19:04
*** ftonello <ftonello!> has joined #yocto19:10
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has quit IRC19:17
*** ftonello <ftonello!> has quit IRC19:18
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC19:18
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has joined #yocto19:21
*** benjamirc <benjamirc!besquive@nat/intel/x-aqrefxwrmsierxqu> has quit IRC19:24
*** benjamirc1 <benjamirc1!besquive@nat/intel/x-obonflldhdgsiidk> has joined #yocto19:24
*** yann|work <yann|work!> has joined #yocto19:26
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC19:32
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has quit IRC19:32
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto19:37
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has joined #yocto19:44
*** dreyna4529 <dreyna4529!> has joined #yocto19:47
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has quit IRC19:49
*** pedraza <pedraza!86868b4a@gateway/web/freenode/ip.> has quit IRC19:58
*** dreyna4529 <dreyna4529!> has quit IRC20:03
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has joined #yocto20:04
*** zbz <zbz!5ed11fd1@gateway/web/freenode/ip.> has joined #yocto20:04
*** zebaz <zebaz!> has joined #yocto20:07
*** zbz <zbz!5ed11fd1@gateway/web/freenode/ip.> has quit IRC20:08
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:6981:f279:59ff:fe64:3a8> has quit IRC20:19
*** joshuagl <joshuagl!~joshuagl@> has quit IRC20:20
*** berton <berton!~fabio@> has joined #yocto20:36
*** morphis <morphis!> has quit IRC20:42
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC20:43
*** riz__ <riz__!4a69aefe@gateway/web/freenode/ip.> has joined #yocto20:43
riz__After runnning oe-init-build-env I got an error "can't open /poky/.templateconf". Never happened to me before. Any idea what the problem is?20:44
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@> has joined #yocto20:45
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto20:45
riz__Furthermore I noticed that the bblayers.cong and local.conf files were not created in /build/conf20:46
bluelightningRP: rburton: there seems to be something wrong here ^20:50
kergothriz__: 'running'?20:50
kergothyou don't run that script, you source it20:51
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC20:51
riz__I did source it. Sorry20:52
riz__I got that error right after sourcing20:52
kergothguessing it must be related to the recent changes to let oedir be overridden? not sure20:52
riz__The only thing I did different from previous times was that I placed the build folder in the same directory as the poky folder20:53
riz__I don;t know if it is related but that is all I can think of20:53
riz__I don't even see a .templateconf in poky20:54
riz__What is that anyway?20:54
*** kscherer <kscherer!~kscherer@> has quit IRC20:55
rburtonriz__: with the poky tarball release?20:56
riz__yes. Jethro20:56
Capsowhat is the use of the CONFIG_MASS_STORAGE option in the yocto kernel?20:56
riz__It is just odd because I have done this many times already20:58
*** vmesons <vmesons!~rmacleod@> has quit IRC20:58
riz__And I am not sure what .templateconf is or where it is to even investigate the issue20:58
rburtonCapso: to build the mass storage gadget driver i guess20:59
*** benjamirc1 <benjamirc1!besquive@nat/intel/x-obonflldhdgsiidk> has quit IRC20:59
rburtonriz__: there's a file at the top of the poky dir called .templateconf20:59
rburtonriz__: sounds like you've either broken your poky tree, or running the oe-init-buildenv script wrong21:00
rburton(another reason why i like working in clones of the git repo)21:00
riz__I just typed "source poky/oe-init-build-env"21:01
Capsorburton, is that needed to be able to use a SATA USB drive from gumstix?21:01
Capsorburton, because currently the yocto image does not give me a mountable device when I plug in the drive on the USB port21:02
riz__I just doublechecked the tar I downloaded "poky-jethro-14.0.1.tar.bz2", and it still doesnt have that file21:02
*** zedd_ is now known as zeddii21:02
riz__I just downloaded it and extracted it21:02
riz__no .templateconf21:03
riz__unless it is hidden21:03
rburtonyes, a dot file is hidden21:03
riz__so it just cant open it21:04
rburtoncan you pastebin a log of you trying to do . oe-init-buidlenv?21:05
rburton$ tar jtvf poky-jethro-14.0.1.tar.bz2|grep templateconf21:05
rburton-rw-r--r--  0 pokybuild users      66 24 Feb 09:04 poky-jethro-14.0.1/.templateconf21:05
rburtondefinitely in the tarball ^^21:05
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto21:05
Capsois it possible to build yocto on Mac OS X?21:05
rburtonCapso: no21:07
Capsobah my linux machine has an encrypted drive, so I can't do it there (long filenames not available)21:07
rburtonuse a proper crypted drive not that piece of **** that ubuntu use :)21:07
Capsowell, kinda too late to change that up now21:08
rburtondm-crypt instead of i-cant-believe-this-works-at-all21:08
rburtonmake a giant file inside the crypted drive, put a ext4 file system inside it, mount it21:08
Capsoah nice21:08
Capsoknow what's a good size for it?21:09
rburtonmany many gig21:09
rburton /dev/sdb1       1.8T  1.5T  354G  81% /data21:09
rburtonthats my build disk21:09
RPkergoth: to be honest I'd really prefer to do that post 2.121:09
Capsorburton, *terrabytes*?21:09
RPkergoth: sending a patch series would good for 2.2 though21:09
rburtonCapso: hell yeah21:09
rburtonCapso: i admit this may not be normal usage21:10
Capsorburton, just to build yocto? I only need to build for gumstix overo21:10
CapsoI mean the images fit on 2G SD card21:10
rburtona built kernel tree is several gig21:10
rburtonwell how much space do you have21:10
Capsoand actually, I just want USB disks to be mountable :-(21:10
riz__found my problem21:10
riz__I missed the file when copying because it was hidden21:11
CapsoI'm currently using hackgnar's prebuilt yocto image, but I'm guessing it doesn't have CONFIG_MASS_USB_STORAGE enabled - if even that's the right thing to look at21:11
Capsorburton, 80G or so21:11
rburtonCapso: give it 40gb21:11
*** berton <berton!~fabio@> has quit IRC21:11
rburtonfrom google that's the option to make your image behave like a usb storage device21:11
*** riz__ <riz__!4a69aefe@gateway/web/freenode/ip.> has quit IRC21:13
Capsooh no that's not what I want21:14
*** zz_ka6sox is now known as ka6sox21:14
CapsoI want to be able to read/write my USB attached storage devices21:14
*** caiortp <caiortp!~inatel@> has quit IRC21:23
kergothRP: k, that works, thanks21:24
RPkergoth: I was also being pointed at using git bundle instead of our roll our own tarballs21:25
kergothhmm, interesting idea21:25
* RP suspects we're not quite at the right minimum git versions for that yet 21:25
RPbut worth thinking about21:25
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC21:28
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto21:28
kergothI wonder how the performance of bundle is, particularly with many branches21:30
RPkergoth: I had a lot of questions and no real answers...21:31
*** amcgee7 <amcgee7!~amcgee7@> has quit IRC21:32
RPCrofton|work: its looking increasingly unlikely I'll make ELC btw, don't have any travel budget/approval. Add in some health related stuff and its not looking good :(21:32
Capsorburton, the yocto kernels for gumstix overo do have USB filesystem device drivers, yeah?21:45
rburtonCapso: no idea21:52
rburtoni'd be surprised if they didn't and you needed to more than just load modules21:52
bluelightningCrofton|work: FWIW, I probably won't be able to make it to ELC either21:53
bluelightninghopefully our electronic arrangements will be slightly better than last year...21:53
*** rburton1 <rburton1!> has joined #yocto21:54
*** fledermaus <fledermaus!~vivek@> has quit IRC21:56
*** rburton <rburton!> has quit IRC21:57
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:58
*** afxez0r <afxez0r!~afxez0r@> has quit IRC22:01
*** afxez0r <afxez0r!~afxez0r@> has joined #yocto22:03
*** sjolley <sjolley!sjolley@nat/intel/x-ufznxsikrdrkpgke> has quit IRC22:03
*** clopez <clopez!> has quit IRC22:05
*** sjolley <sjolley!sjolley@nat/intel/x-vogifthlruehgelm> has joined #yocto22:05
*** lamego <lamego!~jose@> has quit IRC22:06
*** lamego <lamego!~jose@> has joined #yocto22:06
*** sjolley <sjolley!sjolley@nat/intel/x-vogifthlruehgelm> has quit IRC22:10
*** clopez <clopez!> has joined #yocto22:13
CapsoI moved my yocto directory and now bitbake can't find the layer.conf file because the paths were hardcoded somehow - how can I fix it without having to re-download the entire repo?22:13
*** void-dev_ <void-dev_!> has joined #yocto22:14
*** void-dev <void-dev!> has quit IRC22:16
Capsorburton1, and where can I change the expected location of the tmpdir?22:22
*** fledermaus <fledermaus!~vivek@> has joined #yocto22:22
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto22:23
rburton1Capso: conf/local.conf22:23
Capsoactually, tmp/saved_tmpdir cause it saved the hard-coded path22:26
rburton1yeah you need to delete the old tmpdir22:27
rburton1as it has hard-coded paths all over it22:27
rburton1it can rebuild from sstate in seconds though22:27
Capsoah nice. thanks22:27
*** sjolley <sjolley!~sjolley@> has joined #yocto22:35
Capsorburton1, thanks for the hint about the loop device :-)22:43
Capsomy "build configuration" during bitbake gumstix-console-image shows no hash for meta-networking, meaning to me that it won't be built - is thar gith?22:45
Capsothat right*22:45
Capsois it needed for wpa_supplicant and wlan0 to work?22:46
Capsoor is it some other utilities?22:46
rburton1wpa-supplicant is part of oe-core22:50
rburton1meta-networking contains, if you look at the recipes, more advanced networking stuff22:50
CapsoI see, ok22:51
*** khem <khem!~khem@unaffiliated/khem> has quit IRC22:53
*** sameo <sameo!samuel@nat/intel/x-zzlltjpmtoqfkler> has quit IRC22:55
*** edbart <edbart!~ebartosh@> has quit IRC22:58
*** bfederau <bfederau!> has quit IRC23:01
*** fmeerkoetter <fmeerkoetter!> has quit IRC23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto23:01
*** rburton1 <rburton1!> has quit IRC23:02
*** evanmeagher <evanmeagher!> has joined #yocto23:03
*** evanmeagher <evanmeagher!> has quit IRC23:04
*** evanmeagher <evanmeagher!> has joined #yocto23:05
*** alimon1 <alimon1!~alimon@> has quit IRC23:05
*** alimon <alimon!> has joined #yocto23:06
*** evanmeag_ <evanmeag_!> has joined #yocto23:07
*** lamego <lamego!~jose@> has quit IRC23:08
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto23:09
*** evanmeagher <evanmeagher!> has quit IRC23:10
*** evanmeagher <evanmeagher!> has joined #yocto23:10
*** evanmea__ <evanmea__!~MongooseW@> has joined #yocto23:11
*** evanmeag_ <evanmeag_!> has quit IRC23:12
*** evanmeagher <evanmeagher!> has quit IRC23:14
*** agust <agust!> has quit IRC23:30
*** evanmea__ <evanmea__!~MongooseW@> has quit IRC23:32
*** janderson <janderson!~janderson@> has quit IRC23:35
*** mattsm <mattsm!uid128834@gateway/web/> has quit IRC23:51
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC23:52
*** nighty-_ <nighty-_!> has quit IRC23:54

Generated by 2.11.0 by Marius Gedminas - find it at!