| *** olani <olani!user@nat/axis/x-xoazssvtrfphusdt> has left #yocto | 00:00 | |
| *** joeythesaint <joeythesaint!~joe@209.141.56.162> has quit IRC | 00:03 | |
| *** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC | 00:38 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 00:40 | |
| *** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto | 00:41 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 00:42 | |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 00:56 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 00:59 | |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has quit IRC | 01:03 | |
| *** lumag <lumag!~lumag@nat-min.mentorg.com> has quit IRC | 01:55 | |
| *** lumag <lumag!~lumag@nat-min.mentorg.com> has joined #yocto | 01:56 | |
| *** junland <junland!~junland@173.255.47.222> has joined #yocto | 02:08 | |
| *** juristi <juristi!~juristi@nusku.fi> has quit IRC | 02:13 | |
| *** juristi <juristi!~juristi@nusku.fi> has joined #yocto | 02:14 | |
| junland | How would I change hob to have free space for the hddimg | 02:20 |
|---|---|---|
| junland | Or would I just have a partition for extra space. | 02:22 |
| *** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC | 02:25 | |
| *** ccube <ccube!ccube@nx.mindrunner.de> has joined #yocto | 02:27 | |
| *** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has joined #yocto | 02:30 | |
| *** junland <junland!~junland@173.255.47.222> has quit IRC | 02:32 | |
| *** ccube <ccube!ccube@nx.mindrunner.de> has quit IRC | 02:44 | |
| *** ccube <ccube!ccube@nx.mindrunner.de> has joined #yocto | 02:45 | |
| *** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has quit IRC | 02:46 | |
| *** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has joined #yocto | 02:51 | |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has joined #yocto | 03:13 | |
| *** Nilesh_ <Nilesh_!~minda@61.246.136.195> has joined #yocto | 03:18 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 04:00 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 04:04 | |
| *** flihp <flihp!~flihp@c-50-185-54-102.hsd1.ca.comcast.net> has joined #yocto | 05:03 | |
| *** systmkor2 <systmkor2!~systmkor@unaffiliated/systmkor> has joined #yocto | 05:11 | |
| *** systmkor1 <systmkor1!~systmkor@unaffiliated/systmkor> has quit IRC | 05:13 | |
| *** systmkor3 <systmkor3!~systmkor@unaffiliated/systmkor> has joined #yocto | 05:14 | |
| *** systmkor2 <systmkor2!~systmkor@unaffiliated/systmkor> has quit IRC | 05:16 | |
| *** e8johan <e8johan!~quassel@83.218.80.242> has joined #yocto | 05:26 | |
| *** himamura <himamura!~himamura@122.146.57.64> has joined #yocto | 06:15 | |
| *** systmkor3 <systmkor3!~systmkor@unaffiliated/systmkor> has quit IRC | 06:18 | |
| *** AndersD <AndersD!~anders@81-232-163-241-no29.business.telia.com> has joined #yocto | 06:19 | |
| *** fusman <fusman!~fahad@39.55.165.13> has joined #yocto | 06:19 | |
| *** Nitin <Nitin!nakamble@nat/intel/x-zxatcokzmrbdbycq> has quit IRC | 06:26 | |
| *** Nitin <Nitin!~nakamble@192.55.55.41> has joined #yocto | 06:27 | |
| Nilesh_ | Gm:) | 06:49 |
| *** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto | 06:57 | |
| *** fusman <fusman!~fahad@39.55.165.13> has quit IRC | 06:58 | |
| *** himamura <himamura!~himamura@122.146.57.64> has quit IRC | 06:58 | |
| *** himamura <himamura!~himamura@122.146.57.64> has joined #yocto | 07:06 | |
| *** pohly <pohly!~pohly@p5DE8D9DE.dip0.t-ipconnect.de> has joined #yocto | 07:12 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 07:15 | |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has quit IRC | 07:16 | |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has joined #yocto | 07:19 | |
| *** Cubi_ <Cubi_!~cubi@b2b-94-79-174-114.unitymedia.biz> has joined #yocto | 07:23 | |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-1243.bb.online.no> has joined #yocto | 07:25 | |
| *** irontia <irontia!d4178ac2@gateway/web/freenode/ip.212.23.138.194> has joined #yocto | 07:25 | |
| irontia | good morning everybody | 07:27 |
| irontia | I feel dizzy | 07:28 |
| irontia | My code doesn't compile yet with dizzy. Somehow build intermediates are in a work/.../build folder now, so are my autogenerated header files. But that location is not in the include paths... | 07:29 |
| *** j8 <j8!~IceChat9@199.44.250.3> has quit IRC | 07:30 | |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-1243.bb.online.no> has quit IRC | 07:30 | |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-1243.bb.online.no> has joined #yocto | 07:31 | |
| *** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has joined #yocto | 07:33 | |
| *** agust <agust!~agust@p4FDE77AE.dip0.t-ipconnect.de> has joined #yocto | 07:35 | |
| *** fusman <fusman!~fahad@39.55.207.126> has joined #yocto | 07:36 | |
| *** SorenHolm <SorenHolm!~quassel@93.165.148.186> has joined #yocto | 07:39 | |
| *** blitz00 <blitz00!stefans@nat/intel/x-smcwpgzstildqzsd> has joined #yocto | 07:52 | |
| *** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto | 07:52 | |
| *** Nitin1 <Nitin1!nakamble@nat/intel/x-pankmnhobwcvjywr> has joined #yocto | 07:54 | |
| *** Nitin <Nitin!~nakamble@192.55.55.41> has quit IRC | 07:55 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-bstqbaxpgkwyvedr> has joined #yocto | 07:56 | |
| *** jbrianceau_away is now known as jbrianceau | 07:57 | |
| *** mckoan|away is now known as mckoan | 07:57 | |
| mckoan | good morning | 07:57 |
| *** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto | 08:04 | |
| *** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 08:11 | |
| *** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC | 08:20 | |
| *** volker_123456 <volker_123456!~quassel@host-80-81-19-29.customer.m-online.net> has joined #yocto | 08:20 | |
| *** sameo <sameo!samuel@nat/intel/x-aogspcbaeaqmxpjo> has joined #yocto | 08:21 | |
| *** ddalex <ddalex!~ddalex@154.58.102.3> has joined #yocto | 08:24 | |
| *** fusman <fusman!~fahad@39.55.207.126> has quit IRC | 08:26 | |
| *** joseppc <joseppc!~Josep@sestofw01.enea.se> has joined #yocto | 08:30 | |
| *** fusman <fusman!~fahad@39.55.207.126> has joined #yocto | 08:48 | |
| *** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has quit IRC | 08:50 | |
| *** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has joined #yocto | 08:51 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 09:01 | |
| *** Nitin1 <Nitin1!nakamble@nat/intel/x-pankmnhobwcvjywr> has quit IRC | 09:03 | |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 09:03 | |
| *** Nitin <Nitin!nakamble@nat/intel/x-jldxukjohuwqcbsl> has joined #yocto | 09:04 | |
| *** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has quit IRC | 09:05 | |
| *** fusman <fusman!~fahad@39.55.207.126> has quit IRC | 09:08 | |
| *** tasslehoffWtf <tasslehoffWtf!~Tasslehof@ti0260a430-1243.bb.online.no> has joined #yocto | 09:08 | |
| *** JaMa <JaMa!~martin@ip-89-176-104-3.net.upcbroadband.cz> has joined #yocto | 09:10 | |
| *** fusman <fusman!~fahad@39.55.18.61> has joined #yocto | 09:13 | |
| *** tasslehoffWtf <tasslehoffWtf!~Tasslehof@ti0260a430-1243.bb.online.no> has quit IRC | 09:13 | |
| *** ddalex <ddalex!~ddalex@154.58.102.3> has quit IRC | 09:19 | |
| *** ddalex <ddalex!~ddalex@154.58.102.3> has joined #yocto | 09:23 | |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has quit IRC | 09:24 | |
| *** fusman <fusman!~fahad@39.55.18.61> has quit IRC | 09:28 | |
| *** jbrianceau is now known as jbrianceau_brb | 09:30 | |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has joined #yocto | 09:34 | |
| *** jbrianceau_brb is now known as jbrianceau | 09:35 | |
| *** phantoxe <phantoxe!~destroy@2a02:4780:1:1::1:123c> has joined #yocto | 09:37 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 09:39 | |
| bluelightning | morning all | 09:47 |
| *** ddalex <ddalex!~ddalex@154.58.102.3> has quit IRC | 09:48 | |
| *** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 10:01 | |
| *** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 10:05 | |
| *** nslu2-log <nslu2-log!~nslu2-log@140.211.169.184> has quit IRC | 10:07 | |
| *** nslu2-log <nslu2-log!~nslu2-log@140.211.169.184> has joined #yocto | 10:08 | |
| *** melonipoika_ <melonipoika_!~quassel@84.20.150.57> has joined #yocto | 10:10 | |
| *** melonipoika <melonipoika!~quassel@84.20.150.57> has joined #yocto | 10:10 | |
| *** belen <belen!~Adium@192.198.151.44> has joined #yocto | 10:11 | |
| *** jimBaxter <jimBaxter!~jbaxter@46.189.28.68> has joined #yocto | 10:12 | |
| *** melonipoika_ <melonipoika_!~quassel@84.20.150.57> has quit IRC | 10:16 | |
| *** melonipoika <melonipoika!~quassel@84.20.150.57> has quit IRC | 10:16 | |
| *** frsc <frsc!~frsc@host-89-241-60-133.as13285.net> has joined #yocto | 10:27 | |
| *** frsc_ <frsc_!~frsc@host-89-241-60-133.as13285.net> has joined #yocto | 10:33 | |
| *** frsc <frsc!~frsc@host-89-241-60-133.as13285.net> has quit IRC | 10:36 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 10:47 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 10:48 | |
| *** Nitin <Nitin!nakamble@nat/intel/x-jldxukjohuwqcbsl> has quit IRC | 10:50 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 11:00 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 11:00 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 11:11 | |
| *** e8johan <e8johan!~quassel@83.218.80.242> has quit IRC | 11:19 | |
| *** e8johan <e8johan!~quassel@83.218.80.242> has joined #yocto | 11:21 | |
| *** phantoxe <phantoxe!~destroy@2a02:4780:1:1::1:123c> has quit IRC | 11:27 | |
| *** phantoxe <phantoxe!~destroy@2a02:4780:1:1::1:123c> has joined #yocto | 11:30 | |
| *** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has joined #yocto | 11:31 | |
| *** jimBaxter <jimBaxter!~jbaxter@46.189.28.68> has quit IRC | 11:59 | |
| *** jimBaxter <jimBaxter!~jbaxter@46.189.28.49> has joined #yocto | 11:59 | |
| *** colrack <colrack!~colrack@2-228-95-148.ip190.fastwebnet.it> has joined #yocto | 12:00 | |
| *** _dany_ <_dany_!~Thunderbi@192.176.1.94> has quit IRC | 12:02 | |
| *** _dany_ <_dany_!~Thunderbi@192.176.1.94> has joined #yocto | 12:03 | |
| *** tmpsantos <tmpsantos!~tmpsantos@187-102-117-120.efibra-dyn.nwm.com.br> has joined #yocto | 12:04 | |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has joined #yocto | 12:08 | |
| lpapp_ | hi, how can I check if Yocto is trying to pass the correct ld library path to my build system? | 12:08 |
| lpapp_ | bitbake -e foo | 12:08 |
| lpapp_ | | grpe ^LD_LIBRARY_PATH does not bring up anything. | 12:08 |
| lpapp_ | but my tool run during the buildsystem steps cannot find the libncurses library even though it ought to be available. | 12:09 |
| *** Nilesh_ <Nilesh_!~minda@61.246.136.195> has quit IRC | 12:17 | |
| hundeboll | lpapp_: my guess is that the built target compiler uses its own sysroot by default | 12:17 |
| hundeboll | into which libraries are installed | 12:18 |
| hundeboll | e.g. build/tmp/sysroots/qemux86-64/usr/lib | 12:18 |
| *** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has joined #yocto | 12:29 | |
| *** mfleming <mfleming!~matt@94.8.52.96> has joined #yocto | 12:32 | |
| *** mfleming <mfleming!~matt@94.8.52.96> has left #yocto | 12:32 | |
| *** nbhat <nbhat!~nareshbha@111.93.218.67> has joined #yocto | 12:34 | |
| *** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC | 12:39 | |
| *** Siecje <Siecje!~Siecje@CPEbc1401239133-CMbc1401239130.cpe.net.cable.rogers.com> has joined #yocto | 12:50 | |
| *** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 12:52 | |
| *** jimBaxter <jimBaxter!~jbaxter@46.189.28.49> has quit IRC | 13:02 | |
| *** jimBaxter <jimBaxter!~jbaxter@46.189.28.38> has joined #yocto | 13:02 | |
| lpapp_ | hundeboll: hmm? | 13:04 |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-1243.bb.online.no> has quit IRC | 13:11 | |
| *** marka <marka!~marka@128.224.252.2> has joined #yocto | 13:17 | |
| *** nbhat <nbhat!~nareshbha@111.93.218.67> has quit IRC | 13:25 | |
| *** rwoolley <rwoolley!~rwoolley@128.224.252.2> has joined #yocto | 13:25 | |
| *** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has quit IRC | 13:33 | |
| ericbutters | hi. i am wondering how to extract a basic toolchain from a yocto sdk, so i can use it with buildroot? | 13:34 |
| lpapp_ | ericbutters: lol | 13:35 |
| ericbutters | :) | 13:36 |
| ericbutters | i only got the sdk, so i need to build some packages.. but not with yocto in that case | 13:37 |
| ericbutters | i did not built the sdk by myself | 13:37 |
| ericbutters | lpapp_: any idea? | 13:39 |
| lpapp_ | ericbutters: cannot you tell buildroot to use the path from the yocto sdk with regards to the toolchain? | 13:40 |
| bluelightning | ericbutters: the SDK basically is just the toolchain, so I don't think there's much to extract... | 13:40 |
| ericbutters | bluelightning: yes that is right, and i thought it should be clear to use it. but i got erros at first buildsteps og BR and i read "We do not support toolchains or SDK generated by OpenEmbedded or Yocto, because these toolchains are not pure toolchains" | 13:42 |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 13:43 | |
| bluelightning | ericbutters: you'd have to talk to the buildroot folks about that I guess | 13:43 |
| ericbutters | yes | 13:43 |
| bluelightning | I'm no expert for sure, but I'm not sure what qualifies as a "pure toolchain" | 13:43 |
| lpapp_ | vanilla? | 13:45 |
| ericbutters | hey, lets say i have only got the yocto sdk.. is it possible to use yocto with that sdk to build a package? | 14:00 |
| lpapp_ | yocto does not need the yocto sdk | 14:02 |
| ericbutters | to be clear: i only want to build a package, not an sdk | 14:02 |
| lpapp_ | still, you do not need the yocto sdk generated for that. | 14:02 |
| ericbutters | but yocto first must generate a toolchain, so you mean first is to say 'bitbake meta-toolchain' and then 'bitbake package' ? but as i got already a yocto toolchain from my supplier i want to use that one | 14:04 |
| ericbutters | i want to tell yocto to use that provided toolchain to build a package | 14:04 |
| lpapp_ | I think it is better to generate it once and use sstate cache, eventually. | 14:04 |
| lpapp_ | rather than messing with untested external toolchain setup like that. | 14:05 |
| ericbutters | to generate it i need the setup from the supplier which i do not have | 14:05 |
| lpapp_ | sorry, do not know what you mean. | 14:06 |
| *** olani <olani!user@nat/axis/x-xoazssvtrfphusdt> has joined #yocto | 14:06 | |
| ericbutters | np | 14:06 |
| *** dmoseley <dmoseley!~dmoseley@cpe-174-096-222-251.carolina.res.rr.com> has joined #yocto | 14:08 | |
| lpapp_ | I mean the same setup you need to build any package, more or less. | 14:09 |
| lpapp_ | whether it is toolchain or/and some other thing, that is nearly identical. | 14:09 |
| *** tlwoerner <tlwoerner!~trevor@linaro/tlwoerner> has quit IRC | 14:09 | |
| *** tlwoerner <tlwoerner!~trevor@linaro/tlwoerner> has joined #yocto | 14:10 | |
| *** agust <agust!~agust@p4FDE77AE.dip0.t-ipconnect.de> has quit IRC | 14:13 | |
| *** agust <agust!~agust@p4FDE6694.dip0.t-ipconnect.de> has joined #yocto | 14:13 | |
| bluelightning | ericbutters: our build system is not designed to take its own SDK as an external toolchain | 14:14 |
| bluelightning | you may need to contact your supplier and ask them for a layer which supports the target hardware | 14:14 |
| *** mago_ <mago_!~mago@c193-14-123-186.cust.tele2.se> has quit IRC | 14:15 | |
| ericbutters | bluelightning: i see, thanks for information | 14:16 |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has left #yocto | 14:19 | |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has joined #yocto | 14:20 | |
| lpapp_ | hundeboll: I am a bit surprised how ncurses works just fine for gdb-cross | 14:20 |
| lpapp_ | wait, I actually have not tried to run gdb-cross from a buildsystem, just separately. | 14:21 |
| lpapp_ | I guess that is a totally different issue because when you run it, it will likely know where to look for the libraries based on the path, I would assume so. | 14:21 |
| lpapp_ | but during buildtime, I am not sure... | 14:21 |
| *** nbhat <nbhat!~nareshbha@117.192.237.8> has joined #yocto | 14:22 | |
| lpapp_ | as a workaround, I would happily hand-craft some LD_LIBRARY_PATH in the make fucntion of the Yocto recipe, but I do not even know which path to hard code there... | 14:22 |
| lpapp_ | I guess I will use the one from build/tmp/sysroot or something. | 14:23 |
| hundeboll | lpapp_: I think you have ${sysroot} available in the receipes | 14:28 |
| lpapp_ | hundeboll: returning the target sysroot or the generic? | 14:31 |
| lpapp_ | I should probably print it out to see, I guess. | 14:31 |
| hundeboll | no idea :) | 14:31 |
| *** himamura <himamura!~himamura@122.146.57.64> has quit IRC | 14:31 | |
| *** himamura <himamura!~himamura@122.146.57.64> has joined #yocto | 14:32 | |
| *** jawilson <jawilson!~jawilson@73.172.161.128> has joined #yocto | 14:33 | |
| *** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC | 14:35 | |
| *** himamura <himamura!~himamura@122.146.57.64> has quit IRC | 14:40 | |
| lpapp_ | hundeboll: echo $sysroot -> empty output :( | 14:41 |
| *** himamura <himamura!~himamura@122.146.57.64> has joined #yocto | 14:42 | |
| lpapp_ | dylan here. | 14:42 |
| ericbutters | what is "meta-ide-support" ? | 14:46 |
| lpapp_ | check the layer description, if it confirms the guidelines, it should explain it. | 14:47 |
| *** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC | 14:48 | |
| Crofton|work | it isn't in the layer index | 14:48 |
| ericbutters | lpapp_: please provide a link to detail | 14:48 |
| lpapp_ | ericbutters: to what detail? | 14:48 |
| *** tmpsantos <tmpsantos!~tmpsantos@187-102-117-120.efibra-dyn.nwm.com.br> has quit IRC | 14:49 | |
| lpapp_ | ah, it is in oe-core | 14:49 |
| ericbutters | lpapp_: cman :) detail to meta-ide-support | 14:49 |
| lpapp_ | DESCRIPTION = "Meta package for ensuring the build directory contains all appropriate toolchain packages for using an IDE" | 14:49 |
| lpapp_ | ericbutters: https://github.com/openembedded/oe-core/blob/master/meta/recipes-core/meta/meta-ide-support.bb | 14:50 |
| ericbutters | lpapp_: thanks | 14:50 |
| ericbutters | does this what i need? a simple toolchain extraction? why there is not such functionality in yocto? | 14:52 |
| lpapp_ | heh, you are still stuck with that :D | 14:52 |
| lpapp_ | why don't you just ask your supplier if you need support from them? | 14:53 |
| lpapp_ | it is possible that even if you set it up, you will need to know platform specific details, etc. | 14:53 |
| ericbutters | lpapp_ because i can not ask them each time i need to build 3rd party sw | 14:53 |
| ericbutters | yocto sdk from a customer pov help with build their own sw, but as soon as they need 3rd party they are stuck with yocto | 14:54 |
| ericbutters | sdk | 14:54 |
| ericbutters | you always need to know how to cross compile.. instead of using buildroot or yocto for that | 14:55 |
| *** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has joined #yocto | 14:56 | |
| ericbutters | and i really can not believe that yocto as no option to generate a "pure" toolchain | 14:56 |
| lpapp_ | it seems to me that you have insufficient communication with your partner. | 14:57 |
| lpapp_ | I still have no idea what pure toolchain means. | 14:57 |
| lpapp_ | just assuming it means vanilla, but I do not see Yocto heavily patching the toolchain. | 14:58 |
| *** irontia <irontia!d4178ac2@gateway/web/freenode/ip.212.23.138.194> has quit IRC | 14:58 | |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-1243.bb.online.no> has joined #yocto | 14:59 | |
| *** rwoolley <rwoolley!~rwoolley@128.224.252.2> has quit IRC | 15:00 | |
| *** AndersD <AndersD!~anders@81-232-163-241-no29.business.telia.com> has quit IRC | 15:02 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 15:03 | |
| *** kscherer <kscherer!~kscherer@128.224.252.2> has joined #yocto | 15:09 | |
| ericbutters | what would be great: let users install any yocto sdk and then use bitbake and meta layers to build packages with that :) | 15:10 |
| lpapp_ | I think that makes not much sense, really. | 15:12 |
| lpapp_ | Yocto is meant for doing that, but then you want to avoid Yocto... what is the point? | 15:12 |
| lpapp_ | not to improve the communication with your co-workers? | 15:12 |
| ericbutters | lpapp_: that makes perfect sense to me.. why not making life easy? why making it hard? | 15:13 |
| lpapp_ | if one has to generate recipes, that person needs to work with the rest of yocto developers. | 15:13 |
| lpapp_ | exactly my point, imho you are making it hard | 15:13 |
| lpapp_ | you both need to work with _yocto_, yet you do not communicate | 15:13 |
| ericbutters | i want to use receipes not making one | 15:13 |
| lpapp_ | you do not share the work, etc. Based on my experience, it happens to people when they do not communicate properly. | 15:14 |
| *** e8johan <e8johan!~quassel@83.218.80.242> has quit IRC | 15:15 | |
| *** nbhat1 <nbhat1!~nareshbha@117.221.100.194> has joined #yocto | 15:15 | |
| ericbutters | lpapp_: you do not get my point.. i do not contribute to yocto in that case.. i want to use yocto without building a sdk.. just to build a package to use with a target based on my suppliers sdk.. so in the world today with yocto i have to ask my supplier to build that for me and that costs money.. or i cross compile by myself and that takes time and money. so why not using yocto then? that would be easy, take the sdk from supplier and use yocto. | 15:17 |
| *** nbhat <nbhat!~nareshbha@117.192.237.8> has quit IRC | 15:17 | |
| bluelightning | ericbutters: lpapp_ isn't necessarily speaking for all of us.. FWIW whilst we might not be able to do exactly what you are asking (for a number of reasons) we do intend to provide an easier means of building additional pieces of software for the target | 15:17 |
| ericbutters | i heared that suppliers can do meta-layers for that purpose | 15:17 |
| lpapp_ | ericbutters: I would fix your business model. | 15:18 |
| lpapp_ | if your established deal is so inflexible to work together, it is screwed imho. | 15:18 |
| ericbutters | lapp_: i think you did not work much with suppliers :) | 15:18 |
| lpapp_ | I mean it is quite common in every project that someone contributes back. | 15:18 |
| lpapp_ | ericbutters: never, I am begging on the street :p | 15:18 |
| *** rwoolley <rwoolley!~rwoolley@128.224.252.2> has joined #yocto | 15:19 | |
| lpapp_ | joke aside, I am actually currently heavily working with a supplier. | 15:19 |
| bluelightning | ericbutters: however if your current work is to build an image that goes onto the target device, then you should really have a proper BSP layer to support that | 15:19 |
| lpapp_ | bluelightning: he clearly indicated he does not want to build an image, just a package | 15:19 |
| lpapp_ | so that he can, I guess, install that by the package manager. | 15:19 |
| lpapp_ | I was missing that feature a while ago and complained about it, but then I was told it is corner case, so I accepted that. | 15:20 |
| bluelightning | lpapp_: right now, yes... but is that the end goal? | 15:20 |
| lpapp_ | and eventually moved on. | 15:20 |
| lpapp_ | bluelightning: this is my understanding: his supplier provides the image, and he would like to package his software onto the target using the Yocto sdk. If it is deb or rpm, I do not understand why recipes need to be used though. | 15:21 |
| *** SorenHolm <SorenHolm!~quassel@93.165.148.186> has quit IRC | 15:21 | |
| lpapp_ | (even if it is ipkg, it could be done separately, so I am not sure what is the matter with recipes) | 15:21 |
| lpapp_ | perhaps it would be easier, that is why, and more portable. | 15:22 |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 15:22 | |
| ericbutters | bluelightning: i got the image (kernel and rfs) as well as the sdk from the supplier. and everything building my own software is fine.. but sometimes i need some tools which i always need to cross compile myself, and i was wondering why there is no option to use yocto | 15:22 |
| ericbutters | lpapp_: i would love it to be able to use a package manager for that. but that is not an option | 15:23 |
| lpapp_ | please read this: http://www.yoctoproject.org/docs/1.6.1/adt-manual/adt-manual.html | 15:23 |
| bluelightning | ericbutters: part of the goal of our system is to avoid the situation where you are cobbling together images out of binary pieces outside of the build system, leaving you with something that in the long term is difficult to maintain | 15:24 |
| bluelightning | ericbutters: maybe you aren't doing that, but FWIW enabling that particular use case isn't really what our project is for | 15:25 |
| lpapp_ | ericbutters: if you cannot use a package manager, but you want to package, just confuses me even more. | 15:26 |
| lpapp_ | I guess you would need to explain what packaging means in your definition. | 15:26 |
| ericbutters | bluelightning: that makes sense to me.. and i see what you mean further. so with yocto you are stick to your sdk provider. or you are doing it on your own. so do not get me wrong, i like what yocto does. but as i said, from my POI, it would be nice to be able to use yocto without building an image/sdk | 15:27 |
| lpapp_ | I do that every day, cannot see the problem | 15:27 |
| lpapp_ | you definitely do not need to build an sdk for using Yocto | 15:28 |
| ericbutters | i also do not want to build a toolchain, just using it | 15:28 |
| lpapp_ | but again, your definition of SDK may vary... that is why it is confusing to discuss it. It would be nice to know all the details including the definitions. | 15:28 |
| lpapp_ | you have to build it once. | 15:28 |
| lpapp_ | what is the matter? | 15:28 |
| lpapp_ | I mean, sure, 1 > 0, but if you have got zero from your supplier, what is the problem? | 15:30 |
| lpapp_ | what target is it, etc? You did not share much details. | 15:30 |
| lpapp_ | does it require difficult BSP? | 15:32 |
| *** ancky <ancky!~ancky@2a01:4f8:d12:1d05::2> has quit IRC | 15:33 | |
| *** ancky <ancky!~ancky@2a01:4f8:d12:1d05::2> has joined #yocto | 15:33 | |
| *** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has quit IRC | 15:34 | |
| *** nbhat1 is now known as nbhat | 15:36 | |
| *** dl9pf <dl9pf!~quassel@static.88-198-106-157.clients.your-server.de> has joined #yocto | 15:37 | |
| *** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has joined #yocto | 15:37 | |
| *** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has quit IRC | 15:39 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 15:39 | |
| *** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has joined #yocto | 15:39 | |
| *** sameo <sameo!samuel@nat/intel/x-aogspcbaeaqmxpjo> has quit IRC | 15:40 | |
| *** sameo <sameo!samuel@nat/intel/x-nbtyhizkzdvmeaqy> has joined #yocto | 15:42 | |
| ericbutters | lpapp_: no it is simple as i explained. and it is no matter iof what is the target or the BSP. all i say is that let yocto reuse a given yocto sdk. thats it. | 15:43 |
| *** tmpsantos <tmpsantos!~tmpsantos@187-102-117-120.efibra-dyn.nwm.com.br> has joined #yocto | 15:45 | |
| *** Crofton|work <Crofton|work!~balister@pool-71-171-45-99.ronkva.east.verizon.net> has quit IRC | 15:46 | |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has quit IRC | 15:47 | |
| lpapp_ | ericbutters: OK, I disagree. IMHO, there is no use case for that :) | 15:51 |
| lpapp_ | (or if there is any, that means either corner case or an issue elsewhere) | 15:52 |
| lpapp_ | the thing is, you already made up your mind. | 15:52 |
| bluelightning | lpapp_: if you are going to talk to people in here can I ask that you do so politely... right now you aren't helping | 15:54 |
| *** nbhat <nbhat!~nareshbha@117.221.100.194> has quit IRC | 15:54 | |
| lpapp_ | bluelightning: I am sorry to disagree. | 15:54 |
| *** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has joined #yocto | 15:54 | |
| lpapp_ | and I do intend to help. It is not my problem that someone has made up his mind, and will not change it no matter what help he gets. I did ask for clarification, but could not get any response out of it. | 15:55 |
| lpapp_ | so probably he does not actually need help to solve the issue for today. | 15:55 |
| lpapp_ | otherwise, I assume he would have provided answers so that I can give advices. | 15:55 |
| *** sjolley <sjolley!~sjolley@134.134.137.75> has quit IRC | 15:56 | |
| lpapp_ | and complaining here about it will not help anyway; if you want a corner case to be considered, go to the bugtracker. | 15:57 |
| lpapp_ | (although that is usually closed, too, in such cases in my experience) | 15:57 |
| *** staylor <staylor!~staylor@mail.au-zone.com> has joined #yocto | 15:57 | |
| lpapp_ | ericbutters: please do not complain here about as it will not get implemented here; you do not want to pay to your suppliers, fair, the Yocto people may be cheaper. Go to the bugtracker and report it: https://bugzilla.yoctoproject.org/ | 15:59 |
| lpapp_ | but do not be surprised if it is closed as won't fix. | 15:59 |
| *** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has quit IRC | 15:59 | |
| lpapp_ | if you want workarounds for today, you have to share more details, otherwise you will remain without proceeding, really. | 16:00 |
| bluelightning | lpapp_: please do not discourage people from discussing things here | 16:04 |
| ericbutters | lpapp_: i kindly wanted to ask for thinking about such a feature in future. but as bluelighning explained, that is not what yocto is meant for. | 16:05 |
| lpapp_ | ericbutters: I do not understand bluelightning, imho he is saying conflicting things | 16:06 |
| lpapp_ | initially he wrote that yocto would support such things and then not. | 16:06 |
| lpapp_ | I am lost at that conflict, but if you think it is such a cool feature, I would surely report it, no matter what one person thinks here. | 16:07 |
| lpapp_ | I did that many times myselef. | 16:07 |
| bluelightning | I give up | 16:07 |
| lpapp_ | myself* | 16:07 |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 16:07 | |
| *** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has quit IRC | 16:07 | |
| lpapp_ | 15:16 < bluelightning> ericbutters: lpapp_ isn't necessarily speaking for all of us.. FWIW whilst we might not be able to do exactly what you are asking (for a number of reasons) we do intend to provide an easier means of building additional pieces of software for the target | 16:07 |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 16:07 | |
| lpapp_ | and | 16:08 |
| *** dl9pf <dl9pf!~quassel@static.88-198-106-157.clients.your-server.de> has joined #yocto | 16:08 | |
| *** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has joined #yocto | 16:08 | |
| lpapp_ | 15:23 < bluelightning> ericbutters: part of the goal of our system is to avoid the situation where you are cobbling together images out of binary pieces outside of the build system, leaving you with something that in the long term is difficult to maintain | 16:08 |
| lpapp_ | 15:23 < bluelightning> ericbutters: maybe you aren't doing that, but FWIW enabling that particular use case isn't really what our project is for | 16:08 |
| lpapp_ | to me, those two points are conflicting, so I cannot make sense out of them together currently. | 16:08 |
| *** nbhat <nbhat!~nareshbha@64.2.3.194.ptr.us.xo.net> has joined #yocto | 16:08 | |
| *** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has quit IRC | 16:09 | |
| lpapp_ | that is with due respect before people start becoming emotional and losing the track of being objective. | 16:09 |
| *** hundeboll <hundeboll!~hundeboll@mail.hundeboll.net> has joined #yocto | 16:10 | |
| *** hundeboll <hundeboll!~hundeboll@open-mesh.org/catwoman/hundeboll> has joined #yocto | 16:10 | |
| lpapp_ | ericbutters: and fwiw, he is not the main yocto maintainer, so if I was feeling cool about a feature regardless one person thinks - except if it is the main maintainer -, I would say, I would just report it, or even then if everyone disagrees for public recording when the blame game starts later. | 16:11 |
| ericbutters | lpapp_: i am going to report it as a feature request | 16:12 |
| lpapp_ | ok | 16:12 |
| lpapp_ | good luck :> | 16:12 |
| JaMa | I don't see is as conflict, my understanding is that 1st part is about not making 3rdparty binary components un-necessary difficult, 2nd part is recommendation to try to prevent it and build everything from source in one OE build | 16:12 |
| JaMa | and I agree with both parts, we have a lot of binary components built outside OE and it's a lot of pain | 16:13 |
| JaMa | not inflicted by OE as build system | 16:14 |
| ericbutters | JaMa: building outside OE means you did not use bitbake and yocto meta layers? | 16:14 |
| JaMa | yes | 16:14 |
| lpapp_ | but that is not what ericbutters wants based on his description. | 16:14 |
| lpapp_ | (in my understand of course) | 16:14 |
| ericbutters | yes, that is what i say, it it lot of pain then.. it would be nice to be able to re-use yocto then | 16:15 |
| lpapp_ | understanding* | 16:15 |
| JaMa | sorry I haven't read whole backlog, I was responding mostly to parts you copy-pasted from bluelightning | 16:15 |
| lpapp_ | well, it needs to be put in context ^_^ | 16:15 |
| *** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 16:18 | |
| ericbutters | lpapp_: that is what i said.. you got a yocto image on and a yocto sdk delivered, and then you want to build a tool like a browser, ie firfox for this.. so you got two options: 1. ask the supplier to build it -- or 2. build it on your own. but the later is not that easy.. and therefore there is yocto or buildroot | 16:18 |
| *** phantoxe <phantoxe!~destroy@2a02:4780:1:1::1:123c> has quit IRC | 16:18 | |
| ericbutters | lpapp_: but maybe that is a corner case, okay.. but i am stuck here right now. and i thought why not re-using the sdk i got.. | 16:20 |
| *** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 16:20 | |
| ericbutters | but that is not working, not with yocto and not with buildroot | 16:20 |
| JaMa | ericbutters: is there 3rd option? because these 2 are relatively well covered by OE | 16:20 |
| lpapp_ | ericbutters: I still do not get why 2) is difficult | 16:20 |
| lpapp_ | ericbutters: in my experience, you source the environment script | 16:20 |
| lpapp_ | and then you build your software the regular way unless its buildsystem is silly. | 16:21 |
| ericbutters | JaMa: no not as i know :) | 16:21 |
| JaMa | ericbutters: the 1st one is pain, because you need to send your SDK to browser supplier | 16:21 |
| *** phantoxe <phantoxe!~destroy@2a02:4780:1:1::1:123c> has joined #yocto | 16:21 | |
| lpapp_ | and that is the whole point, you know? | 16:21 |
| ericbutters | lpapp_: for building my software it is okay | 16:21 |
| lpapp_ | I keep telling you that you do not need a recipe | 16:21 |
| ericbutters | but for 3rd party sw... | 16:21 |
| lpapp_ | you do not need Yocto for that. | 16:21 |
| JaMa | ericbutters: and in some cases you're maintaining multiple versions at the same time, but your browser supplier needs to build the same code multiple times for each SDK you delivered to him | 16:22 |
| lpapp_ | ericbutters: why? | 16:22 |
| ericbutters | lpapp_: okay explain how to do it | 16:22 |
| ericbutters | please | 16:22 |
| lpapp_ | "in my experience, you source the environment script and then you build your software the regular way unless its buildsystem is silly." | 16:22 |
| lpapp_ | you said you did not need packages, so that oughta suffice, I presume? | 16:22 |
| ericbutters | lpapp_: right, that is how i do with my own source | 16:23 |
| ericbutters | but how to configure correct for cross build? that all is done proved and correct by yocto receipes | 16:23 |
| ericbutters | and i need to do by my own.. that is my problem | 16:23 |
| ericbutters | lpapp_: i said i *need* packages.. | 16:24 |
| ericbutters | you have to read carefully | 16:24 |
| lpapp_ | I will quote yourself, sec. | 16:24 |
| ericbutters | that is all about here.. all the discussion. | 16:25 |
| lpapp_ | 15:21 < ericbutters> lpapp_: i would love it to be able to use a package manager for that. but that is not an option | 16:25 |
| lpapp_ | so how can you use packages if package manager is not an option, please? | 16:25 |
| ericbutters | "but that is not an option" -- what does this mean? i can not use an package manager | 16:25 |
| lpapp_ | if you cannot use a package manager, how can you use packages? | 16:25 |
| ericbutters | eyyy.. i want to build a package and then use it | 16:26 |
| *** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has quit IRC | 16:26 | |
| lpapp_ | how if you cannot use a package manager to use the package? | 16:26 |
| ericbutters | okay.. package=some program/source that is build with bitbake.. so sorry for that.. | 16:27 |
| *** sjolley <sjolley!sjolley@nat/intel/x-ajwgpwzvhzhsonxo> has joined #yocto | 16:27 | |
| lpapp_ | by package you mean an executable? | 16:28 |
| ericbutters | yes | 16:28 |
| lpapp_ | see, this is why your definitions make it confusing to discuss | 16:28 |
| lpapp_ | that is not what usually people think about packages. | 16:28 |
| lpapp_ | and that is why I keep telling you to share your definitions to be on the same page. | 16:28 |
| ericbutters | okay you are right.. that was very confusing | 16:28 |
| lpapp_ | right, so what is wrong about regular cmake/qmake/make/autotools/ninja/scons/whatnot? | 16:28 |
| lpapp_ | they will generate executables for you, too. | 16:28 |
| ericbutters | but why to use different things and not using all in one called yocto.. that does this for me with one command? | 16:29 |
| ericbutters | and what is the matter re-using an yocto sdk with yocto? | 16:30 |
| ericbutters | or why there is no option to extract a simple toolchain out of the sdk? | 16:31 |
| lpapp_ | too unusual; Intel and LF did not need it. | 16:31 |
| lpapp_ | my opinion is that the business usually does not demand such an unreasonable scenario where you cannot collaborate for good. | 16:31 |
| lpapp_ | since if you do the layer Y on top of layer X yourself, that layer Y will not be usable for others. | 16:32 |
| lpapp_ | if it is integrated back to your supplier, they can give it to others off-hand. | 16:32 |
| lpapp_ | or at least you should get the BSP Yocto sources, etc. | 16:33 |
| ericbutters | lpapp_: i do not touch any layer or create one.. i simple want to use yocto to build an executable for my target platform.. simple.. | 16:33 |
| lpapp_ | but then again, I asked many times what your BSP is | 16:33 |
| lpapp_ | it is possible it just works, and you do not need any customization | 16:33 |
| lpapp_ | but you did not want to share that bit... | 16:33 |
| lpapp_ | how will you build your software without an own layer? | 16:34 |
| ericbutters | freescales imx6 bsp.. but the supplier made his own things, so the toolchain has special tune parameters etc. | 16:34 |
| ericbutters | my supplier is not freescale, and i really do not know what all is done by him to the freescale meta layers.. but all that is not what i want to know.. | 16:35 |
| ericbutters | lpapp_: i see, there is no way today for my needs here.. | 16:36 |
| lpapp_ | there sure is :) | 16:36 |
| ericbutters | JaMa: how did you build 3rd party software outside yocto? | 16:37 |
| ericbutters | lpapp_: then please tell me. | 16:37 |
| ericbutters | lpapp_: i got: yocto sdk for my target platform -- i need: let yocto build firefox with that sdk | 16:39 |
| lpapp_ | ericbutters: try to hard code the toolchain for your "image". | 16:40 |
| lpapp_ | in some common config. | 16:40 |
| JaMa | ericbutters: unpack SDK, source the script, run whatever build system your component is using to generate the binaries | 16:40 |
| ericbutters | JaMa: okay.. i see. i do not have a build system for that.. that is the issue. yocto is a build system | 16:41 |
| JaMa | by build system I meant cmake,qmake,automake,... | 16:42 |
| ericbutters | lpapp_: that is the feature i am asking for.. why do i need to hack this? but anyway that is a solution.. so please advise more | 16:42 |
| lpapp_ | advise more? :O | 16:42 |
| ericbutters | JaMa: okay, but there you got the configuration already setup | 16:43 |
| lpapp_ | ericbutters: I would consider your use case valid, if the situation is really that broken, but it is luckily not the usual case in my experience. | 16:43 |
| JaMa | the configuration (of the tools) is part of SDK script, the rest is configured by cmake/qmake/autotools | 16:43 |
| ericbutters | lpapp_: that is no magic that you do.. that there is a way by hacking is clear to me.. magic is to tell where and how to hack.. better provide some gist/patch :D | 16:44 |
| lpapp_ | JaMa: the only problem I see with that if you need to build multiple software pieces with dependencies, etc. | 16:44 |
| lpapp_ | but I still think that is a very rare case based on my industrial observation. | 16:45 |
| *** Cubi_ <Cubi_!~cubi@b2b-94-79-174-114.unitymedia.biz> has quit IRC | 16:45 | |
| JaMa | lpapp_: yes that's the pain I was mentioning before, we have multiple SDKs (with different versions of dependencies) and we need to get the 3rdparty binaries rebuilt multiple times even when it's from the same source | 16:46 |
| JaMa | and then we include SDK indentifier in the filenames of binary packages we're receiving back | 16:47 |
| lpapp_ | ericbutters: read about the config files. You could do it in your distro, image, local, site, etc. | 16:47 |
| lpapp_ | ericbutters: but if some buildsystems override that insanely, you are outta luck. | 16:48 |
| *** mckoan is now known as mckoan|away | 16:48 | |
| ericbutters | lpapp_: i would really appreciate if you can help here | 16:48 |
| JaMa | last time we were even running ABI checker to see what differences in SDK versions are important and we're rebuilding only components which are linking against some dependency with incompatible ABI (compared to previous SDK version) | 16:48 |
| lpapp_ | ericbutters: well, that is all that my resources allowed me today... | 16:49 |
| JaMa | we save some work to 3rdparty builders, but make it a bit more complicated to get consistent set of binary packages all with compatible ABIs | 16:49 |
| lpapp_ | ericbutters: I suggest you to listen to JaMa. | 16:50 |
| lpapp_ | JaMa: do you know by any chance how I could access to the ncurses library in my buildsystem? | 16:54 |
| lpapp_ | since the tool that I run during the make run does not find it which depends on it, I thought I would work it around with modifying the LD_LIBRARY_PATH | 16:54 |
| lpapp_ | but I cannot find a variable to the library path. | 16:55 |
| lpapp_ | so the use case is that I build for arm, and try to run an intel tool during the buildsystem run, but it cannot find the libncurses "so" file. | 16:55 |
| *** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC | 16:55 | |
| *** Nitin <Nitin!~nakamble@134.134.137.71> has joined #yocto | 16:55 | |
| *** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto | 16:56 | |
| JaMa | lpapp_: ncurses's pkg-config file doesn't provide the path? | 16:57 |
| *** phantoneD <phantoneD!destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 16:58 | |
| *** phantoxeD <phantoxeD!destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 16:59 | |
| *** dlschaeffer <dlschaeffer!~daniel.sc@63.229.12.125> has joined #yocto | 17:04 | |
| lpapp_ | JaMa: hmm, that is a good hint, thanks, I will look at it. Perhaps I can use a variable in Makefile that way. | 17:04 |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has quit IRC | 17:06 | |
| *** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 17:06 | |
| *** behanw <behanw!~behanw@S0106dc9fdb80cffd.gv.shawcable.net> has quit IRC | 17:08 | |
| *** jimBaxter <jimBaxter!~jbaxter@46.189.28.38> has quit IRC | 17:17 | |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has joined #yocto | 17:19 | |
| lpapp_ | jama: it seems it cannot be found because my yocto environment is in x86_64 | 17:19 |
| lpapp_ | and that particular tool is 32 bit | 17:19 |
| lpapp_ | how can I enforce the ncurses-native to be available in 32 bit (too?) | 17:19 |
| JaMa | dunno, I would probably use 32bit SDK if you need to call 32bit tools from it | 17:20 |
| lpapp_ | yeah, that would make sense for a bit more complex clash, but it is just one package and I have the setup already for everything | 17:21 |
| lpapp_ | so the porting would take quite a bit of effort. | 17:21 |
| lpapp_ | is it not possible with yocto to say DEPENDS = ncurses-native:32 or something? | 17:21 |
| lpapp_ | also, we need 64 bit tools as well at other places... a bit of mess, it is ... | 17:22 |
| lpapp_ | my only idea is to copy the recipe and enforce 32 bit in our layer | 17:23 |
| lpapp_ | (if the buildsystem of theirs supports that at all) | 17:23 |
| lpapp_ | so what I need is not only the dependency name, but dependency arch and platform. | 17:23 |
| lpapp_ | JaMa: as I need to leave soon, I asked this on the mailing list. | 17:31 |
| *** behanw <behanw!~behanw@S0106dc9fdb80cffd.gv.shawcable.net> has joined #yocto | 17:31 | |
| *** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 17:32 | |
| *** fusman <fusman!~fahad@39.55.59.226> has joined #yocto | 17:33 | |
| JaMa | lpapp_: sorry I'm on conf call | 17:34 |
| lpapp_ | np | 17:35 |
| *** ntl <ntl!~ntl@67-198-70-33.dyn.grandenetworks.net> has joined #yocto | 17:36 | |
| *** tmpsantos <tmpsantos!~tmpsantos@187-102-117-120.efibra-dyn.nwm.com.br> has quit IRC | 17:36 | |
| *** fusman <fusman!~fahad@39.55.59.226> has quit IRC | 17:49 | |
| *** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has joined #yocto | 17:49 | |
| *** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has quit IRC | 17:59 | |
| *** Jefro <Jefro!~jefro@50-1-91-108.dsl.dynamic.fusionbroadband.com> has joined #yocto | 18:00 | |
| *** jbrianceau is now known as jbrianceau_away | 18:01 | |
| *** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has joined #yocto | 18:01 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 18:02 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 18:03 | |
| *** Jefro <Jefro!~jefro@50-1-91-108.dsl.dynamic.fusionbroadband.com> has quit IRC | 18:04 | |
| *** tasslehoff <tasslehoff!~Tasslehof@ti0260a430-1243.bb.online.no> has quit IRC | 18:05 | |
| *** sarahsharp <sarahsharp!sarah@nat/intel/x-pvfnoteixrvwzzda> has joined #yocto | 18:17 | |
| *** phantoxe <phantoxe!~destroy@2a02:4780:1:1::1:123c> has quit IRC | 18:27 | |
| *** sameo <sameo!samuel@nat/intel/x-nbtyhizkzdvmeaqy> has quit IRC | 18:30 | |
| *** belen1 <belen1!~Adium@192.198.151.44> has joined #yocto | 18:31 | |
| *** belen <belen!~Adium@192.198.151.44> has quit IRC | 18:31 | |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has quit IRC | 18:40 | |
| *** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto | 18:45 | |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has joined #yocto | 18:55 | |
| lpapp_ | ericbutters: sorry if I had sounded impolite before. ;-) | 18:56 |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 18:59 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has joined #yocto | 18:59 | |
| *** ahmedammar <ahmedammar!~b33fc0d3@unaffiliated/b33fc0d3> has quit IRC | 19:00 | |
| *** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto | 19:01 | |
| *** belen1 <belen1!~Adium@192.198.151.44> has quit IRC | 19:09 | |
| *** belen <belen!~Adium@192.198.151.44> has joined #yocto | 19:11 | |
| *** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has quit IRC | 19:11 | |
| *** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 19:17 | |
| *** belen <belen!~Adium@192.198.151.44> has quit IRC | 19:18 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 19:18 | |
| -YoctoAutoBuilder- build #86 of nightly-qa-logrotate is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/86 | 19:20 | |
| *** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has joined #yocto | 19:24 | |
| -YoctoAutoBuilder- build #87 of nightly-x86-64 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/87 | 19:26 | |
| *** pohly <pohly!~pohly@p5DE8D9DE.dip0.t-ipconnect.de> has quit IRC | 19:31 | |
| -YoctoAutoBuilder- build #86 of minnow is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/minnow/builds/86 | 19:31 | |
| -YoctoAutoBuilder- build #86 of nightly-qa-extras is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/86 | 19:37 | |
| *** himamura <himamura!~himamura@122.146.57.64> has quit IRC | 19:44 | |
| *** himamura <himamura!~himamura@122.146.57.64> has joined #yocto | 19:45 | |
| *** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC | 19:47 | |
| -YoctoAutoBuilder- build #88 of nightly-non-gpl3 is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/builds/88 | 19:48 | |
| -YoctoAutoBuilder- build #86 of nightly-qa-skeleton is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-skeleton/builds/86 | 19:48 | |
| *** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto | 19:49 | |
| *** lpapp_ <lpapp_!~lpapp@kde/lpapp> has left #yocto | 19:50 | |
| *** LetoThe2nd <LetoThe2nd!~jd@unaffiliated/letothe2nd> has quit IRC | 19:50 | |
| *** JaMa <JaMa!~martin@ip-89-176-104-3.net.upcbroadband.cz> has quit IRC | 19:55 | |
| -YoctoAutoBuilder- build #86 of nightly-x32 is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/86 | 19:57 | |
| *** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto | 19:59 | |
| *** griznj <griznj!~griznj@ool-45773416.dyn.optonline.net> has joined #yocto | 20:08 | |
| -YoctoAutoBuilder- build #84 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/84 | 20:08 | |
| *** griznj <griznj!~griznj@ool-45773416.dyn.optonline.net> has quit IRC | 20:09 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-bstqbaxpgkwyvedr> has quit IRC | 20:11 | |
| *** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC | 20:18 | |
| *** ntl <ntl!~ntl@67-198-70-33.dyn.grandenetworks.net> has quit IRC | 20:20 | |
| *** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 20:22 | |
| -YoctoAutoBuilder- build #85 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/85 | 20:28 | |
| -YoctoAutoBuilder- build #86 of nightly-fsl-ppc is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/86 | 20:36 | |
| -YoctoAutoBuilder- build #85 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/85 | 20:43 | |
| *** pev <pev!~pev@95.151.249.127> has joined #yocto | 20:46 | |
| *** belen <belen!~Adium@190.227.187.81.in-addr.arpa> has joined #yocto | 20:47 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 20:48 | |
| pev | Evening. I've got a custom type of file that I use to produce fully self contained loads that I want to produce via an image recipe. They combines kernel, filesystem and a few other bits and bobs. I can easily run a script to generate it from a recipe but is there a more elegant way to do things? I've noticed "DEPLOYABLE_IMAGE_TYPES" when looking around, would that be a sensible mechanism to use and has anyone produced any examples of extending? | 20:52 |
| *** Crofton|work <Crofton|work!~balister@pool-71-171-45-99.ronkva.east.verizon.net> has joined #yocto | 20:57 | |
| -YoctoAutoBuilder- build #86 of nightly-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/86 | 21:02 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-zvdgddufmcpxaqrq> has joined #yocto | 21:03 | |
| *** rwoolley <rwoolley!~rwoolley@128.224.252.2> has quit IRC | 21:03 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 21:04 | |
| *** Siecje <Siecje!~Siecje@CPEbc1401239133-CMbc1401239130.cpe.net.cable.rogers.com> has left #yocto | 21:09 | |
| -YoctoAutoBuilder- build #87 of minnow-lsb is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/minnow-lsb/builds/87 | 21:09 | |
| *** Crofton|work <Crofton|work!~balister@pool-71-171-45-99.ronkva.east.verizon.net> has joined #yocto | 21:11 | |
| *** ant__ <ant__!~andrea@host138-24-dynamic.5-87-r.retail.telecomitalia.it> has joined #yocto | 21:12 | |
| *** belen <belen!~Adium@190.227.187.81.in-addr.arpa> has quit IRC | 21:16 | |
| *** rangergord <rangergord!~quassel@modemcable186.198-70-69.static.videotron.ca> has joined #yocto | 21:16 | |
| *** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto | 21:18 | |
| -YoctoAutoBuilder- build #89 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/89 | 21:21 | |
| -YoctoAutoBuilder- build #85 of nightly-fsl-arm is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1 BuildImages_1 BuildImages_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/85 | 21:22 | |
| *** rangergord <rangergord!~quassel@modemcable186.198-70-69.static.videotron.ca> has left #yocto | 21:32 | |
| -YoctoAutoBuilder- build #86 of nightly-multilib is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2 BuildImages_3 Running Sanity Tests_3 BuildImages_4] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/86 | 21:36 | |
| *** ant__ <ant__!~andrea@host138-24-dynamic.5-87-r.retail.telecomitalia.it> has quit IRC | 21:38 | |
| -YoctoAutoBuilder- build #87 of nightly-x86-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/87 | 21:42 | |
| *** ant__ <ant__!~andrea@host231-253-dynamic.0-87-r.retail.telecomitalia.it> has joined #yocto | 21:51 | |
| *** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC | 22:00 | |
| *** phantoneD is now known as phantoxeD | 22:00 | |
| -YoctoAutoBuilder- build #88 of nightly-ppc is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/88 | 22:04 | |
| -YoctoAutoBuilder- build #87 of nightly-arm is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/87 | 22:08 | |
| *** marka <marka!~marka@128.224.252.2> has quit IRC | 22:16 | |
| -YoctoAutoBuilder- build #88 of nightly-x86-64-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/88 | 22:22 | |
| *** rwoolley <rwoolley!~rwoolley@192-171-37-80.cpe.pppoe.ca> has joined #yocto | 22:23 | |
| *** sameo <sameo!~samuel@192.55.54.42> has joined #yocto | 22:34 | |
| *** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC | 22:38 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-ajwgpwzvhzhsonxo> has quit IRC | 22:39 | |
| *** sjolley <sjolley!~sjolley@134.134.139.72> has joined #yocto | 22:41 | |
| *** Nitin <Nitin!~nakamble@134.134.137.71> has quit IRC | 22:46 | |
| *** colrack <colrack!~colrack@2-228-95-148.ip190.fastwebnet.it> has quit IRC | 23:00 | |
| *** colrack <colrack!~colrack@host222-190-dynamic.244-95-r.retail.telecomitalia.it> has joined #yocto | 23:00 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 23:01 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 23:01 | |
| *** frsc_ <frsc_!~frsc@host-89-241-60-133.as13285.net> has quit IRC | 23:02 | |
| *** colrack_ <colrack_!~colrack@2-228-95-148.ip190.fastwebnet.it> has joined #yocto | 23:03 | |
| *** colrack <colrack!~colrack@host222-190-dynamic.244-95-r.retail.telecomitalia.it> has quit IRC | 23:06 | |
| *** agust <agust!~agust@p4FDE6694.dip0.t-ipconnect.de> has quit IRC | 23:10 | |
| *** RzR is now known as rZr | 23:11 | |
| *** sjolley <sjolley!~sjolley@134.134.139.72> has quit IRC | 23:11 | |
| *** staylor <staylor!~staylor@mail.au-zone.com> has quit IRC | 23:12 | |
| *** ulf` <ulf`!~ulf@134.134.139.74> has quit IRC | 23:22 | |
| -YoctoAutoBuilder- build #85 of nightly-mips-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/85 | 23:24 | |
| *** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto | 23:25 | |
| *** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC | 23:25 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 23:25 | |
| *** adam_ <adam_!~adam@s206-116-3-18.bc.hsia.telus.net> has quit IRC | 23:31 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-zvdgddufmcpxaqrq> has quit IRC | 23:31 | |
| *** adam_ <adam_!~adam@s206-116-3-18.bc.hsia.telus.net> has joined #yocto | 23:32 | |
| -YoctoAutoBuilder- build #86 of nightly-ppc-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/86 | 23:33 | |
| *** wto <wto!~wto@h-141-69.a336.priv.bahnhof.se> has quit IRC | 23:44 | |
| *** sjolley <sjolley!~sjolley@134.134.137.73> has joined #yocto | 23:54 | |
| *** dvhart <dvhart!~dvhart@134.134.139.76> has joined #yocto | 23:56 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 23:56 | |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!