Monday, 2020-04-13

*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@> has quit IRC00:41
*** fl0v0 <fl0v0!~fvo@2a01:c22:ac4d:2100:e8f6:4cc:4bb9:1052> has quit IRC00:56
*** Yocto_newb <Yocto_newb!47d6aece@> has quit IRC01:01
*** comptroller <comptroller!> has quit IRC01:05
*** fl0v0 <fl0v0!~fvo@2a01:c23:602e:f400:e8f6:4cc:4bb9:1052> has joined #yocto01:11
*** comptroller <comptroller!> has joined #yocto01:12
*** kaspter <kaspter!~Instantbi@> has quit IRC01:33
*** kaspter <kaspter!~Instantbi@> has joined #yocto01:33
*** robert_yang <robert_yang!~robert@> has quit IRC02:03
*** robert_yang <robert_yang!~robert@> has joined #yocto02:03
*** joeythesaint <joeythesaint!> has joined #yocto03:03
*** kovalevsky <kovalevsky!~kovalevsk@> has joined #yocto03:13
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has joined #yocto03:13
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has quit IRC03:28
yoctiNew news from stackoverflow: yocto: how do I install header files along with kernel module in sdk <>03:28
nameclashgood morning gents, is there any sleek way to have production and development builds?03:34
nameclashso for example, the devel build would have additional tools for testing and debugging, which I don't want to ship with the final product03:36
nameclashI was thinking of partitioning the packages in .inc files and then include either the one or the other from core-image-minimal03:39
nameclashdepending on an environment variable03:40
opellowould it be unreasonable to add an additional -devel package that included the extra tools (or just use the existing -dev package)?04:02
*** armpit <armpit!~armpit@2601:202:4180:a5c0:e49d:5859:161:36cd> has quit IRC04:04
nameclashno, not at all.. but I think that would suffer from the same problem I have with my clumsy .inc file solution, which is dynamic control over what gets in and what not04:05
nameclashoh, wait04:06
nameclashyeah that makes sense04:06
opelloas in when you choose to include the development helpers package?04:07
nameclashI coud just say: bitbake core-image-minimal for the production build and bitbake core-image-minimal core-image-minimal-dev for the devel build04:07
opelloyeah, then the image RDEPENDS covers including the additional helper package(s) in the -dev case04:08
nameclashyeah, since bitbake doesnt support conditions, I just injected variables that I used to include additional stuff04:10
nameclashlike in core-image-minimal I had a line in the bottom, saying require core-image-minimal${SUFFIX}.inc04:10
opellowithout knowing more about your workflow it seems like it could be nicer to pack stuff like that into a bbclass?04:11
nameclashwith an empty and, where the former was empty and the latter one kept all the devel stuff04:11
opelloor if it just covers packages some nicely named packagegroups?04:12
nameclashyeah, packagegroups or meta-packages seem to be a good fit for it04:12
*** goliath <goliath!> has quit IRC04:23
*** gtristan <gtristan!~tristanva@> has quit IRC04:30
*** risca <risca!~quassel@> has quit IRC04:34
*** risca <risca!~quassel@> has joined #yocto04:38
*** armpit <armpit!~armpit@2601:202:4180:a5c0:da6:804b:fd00:453b> has joined #yocto04:43
*** gtristan <gtristan!~tristanva@> has joined #yocto04:54
*** paulg <paulg!> has joined #yocto05:12
nameclashopello, you still around?05:41
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto07:17
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto07:34
*** paulg <paulg!> has quit IRC07:39
*** falk0n <falk0n!> has quit IRC07:55
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto07:57
*** amgedr <amgedr!~amgedr@> has joined #yocto08:05
*** m1ster_r0b0t <m1ster_r0b0t!> has quit IRC08:07
*** m1ster_r0b0t <m1ster_r0b0t!> has joined #yocto08:09
*** nameclash <nameclash!> has quit IRC08:10
*** vicale <vicale!> has quit IRC08:10
*** fl0v0 <fl0v0!~fvo@2a01:c23:602e:f400:e8f6:4cc:4bb9:1052> has quit IRC08:24
*** stew-dw <stew-dw!~stew-dw@> has quit IRC08:32
*** stew-dw <stew-dw!~stew-dw@> has joined #yocto08:33
*** amgedr_ <amgedr_!~amgedr@> has joined #yocto08:50
*** amgedr <amgedr!~amgedr@> has quit IRC08:52
*** amgedr_ <amgedr_!~amgedr@> has quit IRC08:54
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:05
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829> has joined #yocto09:12
*** dreyna <dreyna!> has joined #yocto09:15
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:23
*** dreyna <dreyna!> has quit IRC09:26
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto09:27
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC09:30
*** gtristan <gtristan!~tristanva@> has quit IRC10:02
*** locutus_ <locutus_!~LocutusOf@> has quit IRC10:38
*** pbb <pbb!> has quit IRC10:55
*** pbb <pbb!> has joined #yocto10:58
*** pbb <pbb!> has quit IRC11:14
*** kovalevsky <kovalevsky!~kovalevsk@> has joined #yocto11:19
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has joined #yocto11:19
*** pbb <pbb!> has joined #yocto11:25
*** NiksDev <NiksDev!~NiksDev@> has quit IRC11:26
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto11:27
*** gtristan <gtristan!~tristanva@> has joined #yocto11:30
*** berton <berton!~berton@> has joined #yocto11:32
*** fl0v0 <fl0v0!~fvo@2a01:c23:602e:f400:b0b8:42e5:92c6:8d9c> has joined #yocto11:32
*** pbb <pbb!> has quit IRC11:40
*** berton <berton!~berton@> has quit IRC11:41
*** berton <berton!~berton@> has joined #yocto11:42
*** pbb <pbb!> has joined #yocto11:54
*** pbb <pbb!> has quit IRC12:08
*** FrazerClews <FrazerClews!> has quit IRC12:10
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829> has quit IRC12:27
*** JaMa <JaMa!~martin@> has joined #yocto12:30
*** warpme_ <warpme_!uid391875@gateway/web/> has joined #yocto12:33
*** bradfa <bradfa!uid297668@gateway/web/> has joined #yocto12:36
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829> has joined #yocto13:09
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@> has joined #yocto13:10
*** rcw <rcw!~rcw@> has joined #yocto13:11
*** gtristan <gtristan!~tristanva@> has quit IRC13:18
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto13:31
*** ssajal <ssajal!> has joined #yocto13:38
*** goliath <goliath!> has joined #yocto13:39
*** ericch <ericch!> has joined #yocto13:41
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto13:41
*** piero <piero!> has joined #yocto13:48
*** stbenz <stbenz!> has joined #yocto14:03
*** JaMa <JaMa!~martin@> has quit IRC14:25
*** robert_yang <robert_yang!~robert@> has quit IRC14:29
*** robert_yang <robert_yang!~robert@> has joined #yocto14:30
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC14:34
*** bradfa <bradfa!uid297668@gateway/web/> has quit IRC14:46
*** gtristan <gtristan!~tristanva@> has joined #yocto14:46
*** compenguy <compenguy!> has joined #yocto14:49
*** paulg <paulg!> has joined #yocto14:55
*** flihp <flihp!~flihp@> has quit IRC14:57
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@> has joined #yocto14:58
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto14:58
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC15:02
*** stacktrust <stacktrust!> has quit IRC15:14
*** stacktrust <stacktrust!> has joined #yocto15:14
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has quit IRC15:30
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has joined #yocto15:30
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC15:33
*** matthewzmd <matthewzmd!~user@2607:fea8:e2c0:7080::221d> has joined #yocto15:48
matthewzmdfor anyone worked with meta-qt5 before, i have qt5everywheredemo in IMAGE_INSTALL_append, and the build succeeds, how to I trigger the demo after i boot into the image?15:50
*** amaury_d <amaury_d!> has quit IRC15:52
*** jwessel <jwessel!~jwessel@> has quit IRC15:54
*** matthewzmd <matthewzmd!~user@2607:fea8:e2c0:7080::221d> has quit IRC15:55
*** matthewzmd <matthewzmd!~user@> has joined #yocto15:56
*** matthewzmd <matthewzmd!~user@> has quit IRC15:58
*** matthewzmd <matthewzmd!~user@> has joined #yocto15:59
matthewzmdhave i missed anything, my wifi dropped immediately after i post my question16:00
yoctiNew news from stackoverflow: Multiple rootfs through .wks file fails in yocto <>16:00
*** behanw <behanw!uid110099@gateway/web/> has joined #yocto16:01
kergothAnyone played around with using debian multiarch's filesystem layout? ex ld-linux naming, libdir paths16:24
*** matthewzmd <matthewzmd!~user@> has quit IRC16:34
*** matthewzmd <matthewzmd!~user@2607:fea8:e2c0:7080::4c19> has joined #yocto16:35
kergothOn a not directly related note, has anyone looked into multiple target sysroots in a yocto sdk? Ex. use multiconfig to build for multiple target configurations and then build an sdk that populates sysroots for all of them, and then one nativesdk sysroot?16:46
*** nerdboy <nerdboy!~sarnold@> has joined #yocto16:46
*** nerdboy <nerdboy!~sarnold@> has quit IRC16:47
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:47
*** FrazerClews <FrazerClews!> has joined #yocto16:48
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:52
*** amaury_d <amaury_d!> has joined #yocto17:04
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC17:07
yoctiNew news from stackoverflow: How to use bitbake to add static web files? <>17:31
*** jwessel <jwessel!~jwessel@> has joined #yocto17:40
*** vineela <vineela!vtummala@nat/intel/x-jkuckfyyztodgesk> has joined #yocto17:43
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC17:48
*** flihp <flihp!~flihp@> has joined #yocto17:59
*** ball <ball!> has joined #yocto18:05
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC18:05
*** nameclash <nameclash!> has joined #yocto18:16
khemkergoth: mutliconfig sdk is on my wishlist18:23
kergothI basically want a toolchain built by bitbake with a variety of multilib configurations, but it's easier to just use separate machines to construct multiple sysroots, so a multiconfig sdk would be the next best thing to a multilib setup with sysroot suffixes18:25
khemkergoth: yeah I think gcc's notion of multilib doesn not match with OEs and neither with debian multiarch18:44
khemso its a bit sad18:45
*** matthewzmd <matthewzmd!~user@2607:fea8:e2c0:7080::4c19> has quit IRC18:47
jpuhlmankhem there really isn't a lot that needs to be done to bring the oe's idea of mutlilib inline with gcc's.18:54
fraythe worst part of gcc's multilib vs OE.. is that gcc 'defaults' have far far too many multilibs defined in a lot of configs..18:55
fraybut it's certainly possible to build and use the gcc multilibs w/in the YP environment -- assuming you defined all the multilibs on the YP side.18:55
fraydebian multiarch is broken by design IMHO, but again it can be done as well by adjusting paths..18:55
kergothbroken in what way?19:08
kergothare postinsts not run for nativesdk packages? particularly for update-alternatives?19:08
kergothnot looking like it, but not certain19:09
RPkergoth: no, they're not. There is an open bug :(19:19
kergothah, thanks19:21
kergothit makes sense that it'd be a bit of a pain, sdk_arch isn't necessarily build_arch, so we'd need to either postpone to install/relocation time or run qemu, but i don't know how hard it'd be to run qemu against SDKMACHINE rather than  MACHINE19:23
kergothif you assume compat a chroot would do, but lacking root we'd have to fake it anyway, might as well use qemu19:23
*** NiksDev <NiksDev!~NiksDev@> has quit IRC19:24
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@> has quit IRC19:25
RPkergoth: our qemu support is way better than it used to be FWIW and on the most part they're shell anyway. Just needs someone to figure it all out...19:25
* kergoth nods19:25
kergothI'll have to decide if I care enough. which is often the problem. what do i use my precious spare minutes on19:26
RPkergoth: would love your help!19:29
RPkergoth: oe-core feels a bit lonely these days at times :(19:29
kergothyeah, sorry, i haven't been able to contribute much, family is taking a lot of time nowadays, and work is hectic and often on tasks that don't directly contribute. even my backlog of meta-mentor submissions is piling up, and that's my bare minimum contributions usually..19:32
*** RP <RP!> has quit IRC19:41
*** RP <RP!> has joined #yocto19:41
*** RP <RP!> has joined #yocto19:44
*** dreyna <dreyna!> has joined #yocto19:48
*** GrimSleepless <GrimSleepless!~jflabonte@> has joined #yocto19:49
*** GrimSleepless <GrimSleepless!~jflabonte@> has quit IRC19:50
*** GrimSleepless <GrimSleepless!~jflabonte@> has joined #yocto19:50
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:51
*** paulg <paulg!> has quit IRC20:01
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has quit IRC20:12
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has joined #yocto20:12
*** vineela <vineela!vtummala@nat/intel/x-jkuckfyyztodgesk> has quit IRC20:26
*** pharaon2502 <pharaon2502!> has joined #yocto20:27
*** vineela <vineela!vtummala@nat/intel/x-yedmmjeesejdaplx> has joined #yocto20:30
*** nameclash <nameclash!> has quit IRC20:41
*** nameclash <nameclash!> has joined #yocto20:41
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829> has quit IRC20:53
*** berton <berton!~berton@> has quit IRC21:16
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829> has joined #yocto21:28
*** dev1990 <dev1990!> has joined #yocto21:34
*** paulg <paulg!> has joined #yocto21:37
*** gonkulator <gonkulator!~brandon@> has quit IRC21:40
*** gonkulator <gonkulator!~brandon@> has joined #yocto21:40
*** shauno is now known as Shaun21:49
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:ad0e:52f7:2635:5829> has quit IRC21:51
*** dev1990 <dev1990!> has quit IRC21:52
*** hirnschlag <hirnschlag!32ee8faa@> has joined #yocto21:55
hirnschlagHi all21:55
*** RP <RP!> has quit IRC21:55
*** pharaon2502 <pharaon2502!> has quit IRC21:56
*** leon-anavi <leon-anavi!~Leon@> has quit IRC21:56
hirnschlagI'm curious, is this a place where one can ask some stupid questions about yocto?21:56
nameclashhirnschlag, you're spot on dude21:57
hirnschlagOkay, I have to say I never feel so lost like on days I'm touching my yocto build21:57
hirnschlagSo please bear with me. I have functioning ZYNQ arm7 build, in zeus, using meta-xilinx, and my own layer that adds a bunch of kernel patches21:58
hirnschlagI sort of soldiered through that and got this to work. Now I like to add some packages, say openvpn21:59
hirnschlagI copied some .bb files for it from various sources, but nope. Would have been too easy21:59
hirnschlagIs there a tutorial or something on how to go about this?22:00
*** RP <RP!> has joined #yocto22:00
nameclashhirnschlag, when I'm adding packages I first check if the standard poky layers contain a recipe for the package I'm looking for22:01
hirnschlagI think22:02
hirnschlagI did that22:02
nameclashyou can either do this with a simple find statement, e.g. find -name "*openvpn*bb"22:02
nameclashor you just add the package to IMAGE_INSTALL in core-image-minimal.bbappend and run bitbake core-image-minimal22:03
nameclashit will complain if it finds no recipes that provide openvpn22:03
hirnschlagIt did22:03
nameclashin that case, just find the layer in the internet, here zeddii did it for you22:04
hirnschlagI downloaded that recipe22:04
nameclashyou should add that layer to your workspace22:04
hirnschlagthe very same zeddii found22:04
nameclashnot just the recipe22:04
zeddiiyup. you need to clone the layer, add it to your bblayers.conf and then add the packge to your image install.22:05
zeddiiIIRC the yocto-mega-manual should have some samples of how to do that.22:05
hirnschlagThis will require me to get the whole meta-openembedded shebang22:06
nameclasha good approach imo is to add the layer repo as submodule to your project22:06
hirnschlagwill that have other consequences besides me getting the openvpn package in my image?22:06
zeddiithey will be parsed, but not built, unless you have them in your install, or a dependency of something being installed.22:07
hirnschlagokay, ill try that22:07
zeddiiyocto compatible layers will not influence your build, simply by being in bblayers22:07
nameclashyeah, you will also pull every other package into your project, i.e. not that they get into your image but you will be able then to add more packages from that layer22:07
hirnschlagThis seems to be working22:17
hirnschlagSorry, I was just too nervous adding meta-openembedded before because its so huge22:17
nameclashactually, you'll find many of the stuff you're gonna need in future in that layer22:20
*** ssajal <ssajal!> has quit IRC22:21
*** ssajal <ssajal!> has joined #yocto22:25
hirnschlagThank you all22:26
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC22:29
*** mauz555 <mauz555!~mauz555@> has joined #yocto22:36
*** hirnschlag <hirnschlag!32ee8faa@> has quit IRC22:59
*** raijin <raijin!~raijin@unaffiliated/raijin> has joined #yocto23:13
*** mauz555 <mauz555!~mauz555@> has quit IRC23:22
*** creich_ <creich_!> has joined #yocto23:25
*** creich <creich!> has quit IRC23:26
*** ericch <ericch!> has quit IRC23:28
nameclashI have an SDK build that is baked via bitbake -c populate_sdk core-image-minimal23:49
nameclashnow I want to add meta-toolchain-qt5 to the SDK and, since this is a meta-package, I figured to just run bitbake -c populate_sdk core-image-minimal meta-toolchain-qt523:51
nameclashthis does however fail in the end because both core-image-minimal and meta-toolchain-qt5 try create "the same" installable artifacts, which obviously fails23:53
nameclashmeta-toolchain-qt5 does not do anything special than inheriting populate_sdk_qt5, which generates a qt.conf and adds some packagegroups to the appropriate TOOLCHAIN_* variables23:55
nameclashhow do I get both core-image-minimal and meta-toolchain-qt5 together in one sdk?23:56
nameclashshould I just inherit populate_sdk_qt5 from core-image-minimal.bbappend or is that a bad idea?23:57

Generated by 2.17.2 by Marius Gedminas - find it at!