Monday, 2018-04-23

*** stephano <stephano!~stephano@134.134.139.75> has quit IRC00:02
*** nighty- <nighty-!~nighty@s229123.ppp.asahi-net.or.jp> has quit IRC00:04
*** lucaceresoli <lucaceresoli!~lucaceres@45.11.168.109.cust.ip.kpnqwest.it> has quit IRC00:12
*** flying_sausages <flying_sausages!~flying_sa@static.21.60.9.5.clients.your-server.de> has quit IRC00:53
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto00:57
*** flying_sausages <flying_sausages!~flying_sa@static.21.60.9.5.clients.your-server.de> has joined #yocto01:00
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:02
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto01:03
*** nighty- <nighty-!~nighty@kyotolabs.asahinet.com> has joined #yocto01:06
*** lucaceresoli <lucaceresoli!~lucaceres@45.11.168.109.cust.ip.kpnqwest.it> has joined #yocto01:07
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:09
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto01:13
*** flying_sausages <flying_sausages!~flying_sa@2a01:4f8:161:610b::2> has joined #yocto01:17
*** flying_sausages <flying_sausages!~flying_sa@2a01:4f8:161:610b::2> has quit IRC01:20
*** flying_sausages <flying_sausages!~flying_sa@static.21.60.9.5.clients.your-server.de> has joined #yocto01:24
*** Willy-- <Willy--!~william@142.134.27.48> has joined #yocto01:27
*** flying_sausages <flying_sausages!~flying_sa@static.21.60.9.5.clients.your-server.de> has quit IRC01:28
*** flying_sausages <flying_sausages!~flying_sa@2a01:4f8:161:610b::2> has joined #yocto01:31
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC01:36
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:39
*** dengke <dengke!~dengke@106.120.101.38> has joined #yocto01:53
*** TooTallTims <TooTallTims!~quassel@161.97.215.98> has quit IRC02:21
*** kaspter <kaspter!~Instantbi@115.195.49.195> has quit IRC02:21
*** kaspter <kaspter!~Instantbi@115.195.49.195> has joined #yocto02:21
*** d3r3k <d3r3k!uid190567@gateway/web/irccloud.com/x-tuiuvsndmvcspxrd> has joined #yocto02:33
*** Willy-- <Willy--!~william@142.134.27.48> has quit IRC02:40
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto02:49
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-mvvscwdhzmekajns> has quit IRC03:00
*** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has quit IRC03:10
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC04:00
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC04:06
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto04:11
*** ntl <ntl!~nathanl@65-36-80-8.dyn.grandenetworks.net> has joined #yocto04:22
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto04:25
*** ntl <ntl!~nathanl@65-36-80-8.dyn.grandenetworks.net> has quit IRC04:27
jmk_2~2~04:40
*** jmk_ <jmk_!~jmk@87-93-63-101.bb.dnainternet.fi> has quit IRC04:40
*** b0g <b0g!~hello@triglide.urmom.org> has quit IRC04:50
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto04:51
*** b0g <b0g!~hello@triglide.urmom.org> has joined #yocto04:53
-YoctoAutoBuilder- build #994 of nightly-x86-64 is complete: Failure [failed Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64/builds/99405:25
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto05:30
*** frieder <frieder!~frieder@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has joined #yocto06:07
*** agust <agust!~agust@p4FCB48EA.dip0.t-ipconnect.de> has joined #yocto06:09
*** pohly <pohly!~pohly@p54849CF1.dip0.t-ipconnect.de> has joined #yocto06:13
*** gtristan <gtristan!~tristanva@221.147.85.22> has joined #yocto06:20
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC06:26
*** rovanceo_ <rovanceo_!~rovanceo@80.97.64.55> has joined #yocto06:27
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:28
*** rovanceo__ <rovanceo__!~rovanceo@80.97.64.55> has quit IRC06:30
*** tasslehoff_ <tasslehoff_!~aronning@80.77.101.233> has joined #yocto06:34
-YoctoAutoBuilder- build #988 of nightly-x86 is complete: Failure [failed Running Sanity Tests Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-x86/builds/98806:37
*** thaytan <thaytan!~thaytan@180-150-118-156.NBN.mel.aussiebb.net> has quit IRC06:39
*** mihais <mihais!~mihaiserb@86.120.134.70> has joined #yocto06:41
*** colrack <colrack!~colrack@94.126.8.166> has joined #yocto06:42
*** fl0v0 <fl0v0!~fvo@i577B9BA5.versanet.de> has joined #yocto06:53
*** varjag <varjag!~user@122.62-97-226.bkkb.no> has joined #yocto07:03
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto07:10
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has quit IRC07:11
*** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-84-4.fbx.proxad.net> has joined #yocto07:12
*** mckoan|away is now known as mckoan07:14
mcfriskhow to add source file to image recipe? I want to check that some files exists on target image as ROOTFS_POSTPROCESS_COMMAND but I need the reference as source file for each image.07:17
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC07:19
*** mdnneo <mdnneo!~umaucher@217.89.178.116> has joined #yocto07:22
nayfemcfrisk: in do_install_append, add source in deploy dir  install ${S}/stuff.c ${D}/${datadir}/stuff.c  , then   FILES_${PN}-dev += "${datadir}/stuff.c"07:24
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC07:28
*** JaMa <JaMa!~martin@217.30.68.212> has joined #yocto07:32
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto07:35
mcfrisknayfe: I don't want to install files to the image. I want to check after do_rootfs that certain files exists in image. These certain files are a list of files and metadata that I would like to refer within do_rootfs. Adding SRC_URI and a file://my_file_list.txt doesn't work. The SRC_URI files are not addressable at image recipe build time...07:37
*** vdehors <vdehors!~vdehors@91.162.62.2> has joined #yocto07:39
*** Bunio_FH <Bunio_FH!~bunio@213.46.252.136> has joined #yocto07:40
yoctiNew news from stackoverflow: How to port grpc helloworld(CPP) example on yocto <https://stackoverflow.com/questions/49975541/how-to-port-grpc-helloworldcpp-example-on-yocto>07:43
*** toanju <toanju!~toanju@185.27.182.30> has joined #yocto07:43
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto07:45
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto07:46
*** d3r3k <d3r3k!uid190567@gateway/web/irccloud.com/x-tuiuvsndmvcspxrd> has quit IRC07:49
nayfemcfrisk maybe you can look at sanity.bbclass & utility-tasks.bbclass for examples07:50
*** sno <sno!~sno@p54A24523.dip0.t-ipconnect.de> has joined #yocto07:52
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has joined #yocto07:53
*** ant_work <ant_work!~ant__@host138-188-dynamic.50-82-r.retail.telecomitalia.it> has joined #yocto07:55
*** yu <yu!413144c9@gateway/web/freenode/ip.65.49.68.201> has joined #yocto08:04
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC08:08
mcfrisknayfe: those classes do check rootfs files but not against input data.. image bbclass doesn't derive from base so fetch and unpack aren't available..08:09
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has quit IRC08:17
*** Bunio_FH <Bunio_FH!~bunio@213.46.252.136> has quit IRC08:18
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto08:20
*** yann <yann!~yann@37.173.111.72> has joined #yocto08:25
*** prabhakarlad <prabhakarlad!~prabhakar@194.75.40.178> has joined #yocto08:26
*** T_UNIX <T_UNIX!uid218288@gateway/web/irccloud.com/x-dpanrycjjvkkhfne> has joined #yocto08:28
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC08:29
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto08:29
*** boucman_work <boucman_work!~jrosen@wesnoth/developer/boucman> has joined #yocto08:32
*** morphis <morphis!~morphis@pD9ED7B64.dip0.t-ipconnect.de> has joined #yocto08:37
*** Bunio_FH <Bunio_FH!~bunio@213.46.252.136> has joined #yocto08:39
*** acrap <acrap!~acrap@host-85-237-33-147.dsl.sura.ru> has joined #yocto08:43
acrapHi, folks!08:43
acrapI know about this syntax to run bitbake "DISTRO=mydistro bitbake my-image-minimal"08:44
acrapcan I pass more than one variable like DISTRO and how?08:44
LetoThe2ndAFAIK you can have multiple recipes to build and even multiple package managers being fed, but MACHINE and DISTRO are singular.08:45
*** kaspter <kaspter!~Instantbi@115.195.49.195> has quit IRC08:45
*** kaspter <kaspter!~Instantbi@115.195.49.195> has joined #yocto08:45
acrapLetoThe2nd: you mean i can't do smth like that:"MACHINE=mymachine DISTRO=mydistro bitbake my-image-minimal"?08:47
*** ronnyand <ronnyand!c33c449d@gateway/web/freenode/ip.195.60.68.157> has joined #yocto08:49
LetoThe2ndyou can do that, but there is only one value for DISTRO and MACHINE08:50
LetoThe2ndthere has been some work on multimachine, but i don't think its worth recommending: http://lists.openembedded.org/pipermail/bitbake-devel/2016-June/007557.html08:51
*** yann|work <yann|work!~yann@37.173.81.176> has joined #yocto08:52
acrapLetoThe2nd: ok. thanks08:53
acrapLetoThe2nd: i asked just about setting of variables. Not about multimachines08:54
LetoThe2ndacrap: ah, the question was about more distinct variables? sure, no problem at all.08:55
LetoThe2ndbasically anything in BB_ENV_WHITELIST is allowed: https://www.yoctoproject.org/docs/2.4.2/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_WHITELIST08:56
*** yann <yann!~yann@37.173.111.72> has quit IRC08:56
mcfriskwhy doesn't image.bbclass import base.bbclass?08:57
*** ronnyand <ronnyand!c33c449d@gateway/web/freenode/ip.195.60.68.157> has quit IRC08:58
acrapLetoThe2nd: by the way. Syntax what I showed before doesn't work for me. DISTRO part does work, but machine doesn't08:58
acrapMACHINE=qemux86 DISTRO=mydistro-cgl bitbake my-image-cgl08:59
LetoThe2ndacrap: then look at your local.conf, probably you're assigning MACHINE by '=', and DISTRO by '?='08:59
acrapMACHINE assigned with ??=08:59
LetoThe2nd'=' means "always assing", '?=' means "only assign if not set already, like with the env"09:00
LetoThe2ndthen i'm pretty sure you reversed your last post.09:00
LetoThe2ndhere, see https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#variable-expansion09:01
acrapi found the error09:01
LetoThe2nd(3.1.3, 3.1.4, 3.1.5)09:01
acrapMACHINE was also assigned in layer.conf with "="09:01
acrapLetoThe2nd: thanks for the support09:02
acrapLetoThe2nd: I very appreciate that Yocto community is so friendly and helpful.09:02
LetoThe2ndnow i'm sad.09:03
LetoThe2ndseems like i totally failed to live up to my grumpy old guy image. :-(09:03
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has joined #yocto09:04
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC09:05
acrapLetoThe2nd: my English is not so strong to detect sarcasm09:05
LetoThe2ndacrap: all is well, no worries09:05
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:25
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC09:26
*** stallemanden <stallemanden!~stalleman@217.63.96.37> has left #yocto09:26
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto09:28
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC09:38
ostenHello, i'm trying to make my own class (.bbclass) file to generate an custom image for me. (Custom partition layout, but including efi boot loader) But where can i find more information about all the variables and stuff that i can use in a class file ? And also some basic information about how to write a class from the very start ?09:38
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto09:41
*** kaspter <kaspter!~Instantbi@115.195.49.195> has quit IRC09:43
*** kaspter <kaspter!~Instantbi@115.195.49.195> has joined #yocto09:44
LetoThe2ndosten: whatyou can use inside a class is actually not different from what you can use in a recipe, AFAIK09:47
LetoThe2ndosten: here is the official (albeit short) explanation as well as a lot of examples: https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-classes09:48
LetoThe2ndosten: in fact, i'd actually say that a bbclass is jsut "an include file that you can reach from anywhere"09:49
rburtoneffectively that's close enough :)09:50
rburtonosten: have you looked at wic for custom partition layouts?09:50
LetoThe2ndrburton: i'm sure there's a handful of corner cases :)09:50
ostenLetoThe2nd: Thanks, that's probably a good way to see it :)09:50
ostenrburton: i want to add some specific files when i do the partitions, as for example all my applications should be moved to the right partition. The reason behind this is because i want to use rauc as update system. With an a+b update structure for my applications.09:52
*** kaspter <kaspter!~Instantbi@115.195.49.195> has quit IRC09:53
*** kaspter <kaspter!~Instantbi@115.216.25.143> has joined #yocto09:55
*** sa2ajj_ <sa2ajj_!~quassel@dsl-hkibng21-54f864-131.dhcp.inet.fi> has quit IRC10:10
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC10:13
tasslehoff_should both syslogd.service and busybox-syslog.service be running on a system? I have two syslogd running.10:15
paulbarkertasslehoff_ do you know which package is providing syslogd.service?10:18
tasslehoff_paulbarker: which package puts it into the image, you mean?10:20
paulbarkeryes10:21
tasslehoff_paulbarker: searching now. might take a while10:21
paulbarkerOk. Which branch of yocto project are you using?10:21
tasslehoff_pyro10:21
* paulbarker looks at pyro10:22
tasslehoff_paulbarker: seems to be sysklogd10:22
tasslehoff_I have two of those as well :)10:22
tasslehoff_sysklogd and busybox-klogd10:23
paulbarkerYou may want to try backporting http://git.openembedded.org/openembedded-core/commit/meta/recipes-core/busybox/busybox.inc?id=597bbf99ee8e88294f2ed96c84a51f9ed83e893310:23
paulbarkerOr at least using a bbappend to set RCONFLICTS_busybox-syslog10:24
*** droman <droman!~david@nat01.ifae.es> has joined #yocto10:25
tasslehoff_paulbarker: ooh. highly relevant. thanks!10:25
paulbarkerI'd recommend taking a look at busybox.inc to see what gets packaged and how it gets pulled in as an RRECOMMENDS10:26
paulbarkerYou could also try adding busybox-syslog to BAD_RECOMMENDATIONS (https://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#var-BAD_RECOMMENDATIONS) if you want to make sure you get the sysklogd version10:28
*** rajm <rajm!~robertmar@cpc126996-macc4-2-0-cust25.1-3.cable.virginm.net> has joined #yocto10:29
tasslehoff_paulbarker: yeah. I just wondered which one I actually want :)10:30
paulbarkerPick one and see if anything breaks :p10:31
tasslehoff_paulbarker: my thought exactly. thanks :)10:31
paulbarkerThe scream test strikes again10:32
*** peacememories <peacememories!~textual@e246-176.eduroam.tuwien.ac.at> has joined #yocto10:38
*** Zajc <Zajc!~Zajc@89-212-111-208.static.t-2.net> has quit IRC10:48
acrapI can't access to Yocto manual from Russia without VPN O_o11:01
LetoThe2ndacrap: does your ISP maybe do some fancy filtering?11:08
tasslehoff_paulbarker: nothing broke. I lost /var/log/messages, but I don't miss it :)11:09
acrapLetoThe2nd: I've never seen this issue before... Looks like our censorship blocks Yocto resources accidentally.11:10
acrapI share this issue through Twitter and mentioned Roscomnadzor (our censorship bureau). But I am not sure they going to fix it. They are too busy with their process of blocking Telegram now.11:14
*** nighty- <nighty-!~nighty@kyotolabs.asahinet.com> has quit IRC11:14
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has quit IRC11:28
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has joined #yocto11:30
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC11:34
*** dlan <dlan!~dennis@58.246.136.202> has joined #yocto11:34
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto11:34
tasslehoff_paulbarker: it's my adding of packagegroup-core-full-cmdline that causes ksyslogd to enter the image11:40
*** frieder <frieder!~frieder@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has quit IRC11:49
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto12:02
*** frieder <frieder!~frieder@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has joined #yocto12:07
*** Zajc <Zajc!~Zajc@89-212-111-208.static.t-2.net> has joined #yocto12:09
-YoctoAutoBuilder- build #945 of buildtools is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/buildtools/builds/94512:10
tasslehoff_I have a recipe that depens on proj being installed in the image as well. What is the proper way to add it?12:20
tasslehoff_RDEPENDS_${PN} was seemingly not the way to go12:21
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC12:24
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto12:24
*** micka <micka!~micka@reverse-75.fdn.fr> has quit IRC12:27
rburtonyes, RDEPENDS is exactly what you want12:27
*** micka <micka!~micka@reverse-75.fdn.fr> has joined #yocto12:28
tasslehoff_rburton: hm. perhaps all the packages were already in my image then, since the manifest did not change.12:32
rburtonor, you didn't actually install PN12:32
rburtonbut yes, both possible12:32
tasslehoff_they were already in the manifest, but I was missing proj-dev, instead of proj.12:33
rburtona runtime package depending on a -dev is pretty unusual12:35
tasslehoff_rburton: yeah. investigating that now. seems maybe proj doesn't give me libproj.so in my image12:35
rburtonif the .so is what you actually need and not a development-only symlink then fix the packaging12:36
rburtonassumption is that .so is a development-only unversioned symlink to the versioned library in PN12:36
rburtonif thats not true, change the packaging12:37
tasslehoff_rburton: libproj.so.0 and its target is indeed in the image, so I think proj behaves well.12:39
tasslehoff_will have to see what gdal is doing.12:40
*** peacememories <peacememories!~textual@e246-176.eduroam.tuwien.ac.at> has quit IRC12:40
*** rajm <rajm!~robertmar@cpc126996-macc4-2-0-cust25.1-3.cable.virginm.net> has quit IRC12:42
*** nighty- <nighty-!~nighty@s229123.ppp.asahi-net.or.jp> has joined #yocto12:46
*** acrap <acrap!~acrap@host-85-237-33-147.dsl.sura.ru> has quit IRC12:48
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC12:49
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC12:57
*** ntl <ntl!~nathanl@65-36-80-8.dyn.grandenetworks.net> has joined #yocto13:04
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:06
*** yann|work <yann|work!~yann@37.173.81.176> has quit IRC13:07
*** JaMa <JaMa!~martin@217.30.68.212> has quit IRC13:08
*** ntl <ntl!~nathanl@65-36-80-8.dyn.grandenetworks.net> has quit IRC13:11
*** yann|work <yann|work!~yann@37.173.81.176> has joined #yocto13:11
*** toanju <toanju!~toanju@185.27.182.30> has quit IRC13:11
*** yann|work <yann|work!~yann@37.173.81.176> has quit IRC13:17
*** yann|work <yann|work!~yann@37.173.81.176> has joined #yocto13:21
-YoctoAutoBuilder- build #940 of nightly-arm64 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-arm64/builds/94013:22
*** daniele_ <daniele_!~daniele@94.138.189.133> has joined #yocto13:23
*** daniele_ is now known as daniele_d13:24
daniele_dhi all13:24
daniele_dI'm trying to build a gtk3 application in yocto13:24
daniele_dI configured eclipse and the hello world prog is ok in the remote machine13:25
daniele_dbut I can't figure it out how to add library to project13:25
daniele_dsomeone can help me?13:25
LetoThe2nddaniele_d: you mean you are missing the library on the target?13:27
daniele_dyes13:27
daniele_dgtk/gtk.h is missing13:27
LetoThe2ndand you aretrying to compile *IN* the target? why that?13:28
*** wolfmitchell <wolfmitchell!~mitchell@23-111-179-112.exho.co> has joined #yocto13:28
*** wolfmitchell <wolfmitchell!~mitchell@unaffiliated/wolfmitchell> has joined #yocto13:28
daniele_dI use ecplise as decribed13:28
daniele_dBut I don't know how can I compile and then move to the target13:28
LetoThe2ndi mean, usually you would have your application recipe DEPEND on all your libs, and thats it. during dev time, you would add all needed libraries/dependencies to the image, then build image, build sdk, and use that sdk to cross compile13:29
*** gtristan <gtristan!~tristanva@221.147.85.22> has quit IRC13:29
daniele_dso after i install the toolchain I need to create a recipe and bitbake my c prog against it?13:29
LetoThe2ndinstall which toolchain?13:30
daniele_di use a terminal in which I installed yocto13:30
LetoThe2ndthe steps are: 1) create an image that has all the libraries you need. build that.13:30
daniele_dok13:30
LetoThe2nd2) create a sdk that fits the image. its basically just bitbake -c populate_sdk $YOURFUNNYIMAGE13:31
LetoThe2nd3) use that sdk for cross compiling13:31
daniele_dok I'll try13:31
LetoThe2ndits all neatly laid out here: https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#sdk-using-the-standard-sdk13:31
mckoanLetoThe2nd: very well explained :-D13:32
-YoctoAutoBuilder- build #979 of nightly-multilib is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-multilib/builds/97913:32
daniele_dbut it will work in my environment? I have a variscite product13:33
mckoandaniele_d: Yocto is platform independent13:33
LetoThe2ndits the generic yocto/openembedded way.13:33
daniele_dok13:33
*** gtristan <gtristan!~tristanva@110.11.179.89> has joined #yocto13:34
daniele_dso I nedd to check all library for my peripherals are installed13:34
LetoThe2ndas long as you don't have a recipe for your application, yes.13:35
LetoThe2ndyou can also first create a dummy recipe for your application which does not yet install anything of its own, but already pull in the dependencies13:35
*** zarzar <zarzar!~zarzar@184.75.233.58> has joined #yocto13:35
daniele_dif I add libgtk-3-dev to local-conf bitbake gives me error13:40
daniele_dwhere can I found syntax for the packages?13:40
daniele_dexcuse  me my error... missin \13:41
*** henriknj <henriknj!~hnje@193.106.123.182> has quit IRC13:43
yoctiNew news from stackoverflow: OTA update with SWupdate in yocto [closed] <https://stackoverflow.com/questions/49897857/ota-update-with-swupdate-in-yocto>13:44
*** henriknj <henriknj!~hnje@193.106.123.182> has joined #yocto13:45
*** peacememories <peacememories!~textual@e246-176.eduroam.tuwien.ac.at> has joined #yocto13:48
-YoctoAutoBuilder- build #956 of nightly-mips is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-mips/builds/95613:51
-YoctoAutoBuilder- build #989 of nightly-x86 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-x86/builds/98913:52
*** diego_r <diego_r!~diego@host57-224-static.7-79-b.business.telecomitalia.it> has joined #yocto14:02
*** fberg <fberg!~kappe@93-42-191-214.ip88.fastwebnet.it> has joined #yocto14:06
-YoctoAutoBuilder- build #995 of nightly-x86-64 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64/builds/99514:10
*** marka <marka!~masselst@128.224.252.2> has joined #yocto14:10
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC14:10
fberghello guys, I'm adding vsftpd to my yocto image. The install task of vsftpd needs to be customized installing some files. Among them I need to add a file called pam_pwdfile.so. pam_pwd_file.so is a symbolink link to pam_pwdfile.so.1.0.0. in particulare pam_pwdfile.so is provided by libapm-pwdfile-dev and pam_pwdfile.so.1.0.0 by libpam-pwdfile. Both packages Are correctly generated by a custom recipe called libpam-pwdfile. So in my14:11
fbergvsftpd_%.bbappend I have added RDEPENDS_${PN} += "libpam-pwdfile libpam-pwdfile-dev". If I run "bitbake vsftpd" I get the following error: do_package_qa: QA Issue: vsftpd rdepends on libpam-pwdfile-dev [dev-deps]14:11
fberghow can I fix it ?14:11
*** dlan <dlan!~dennis@58.246.136.202> has joined #yocto14:16
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto14:16
*** aratiu <aratiu!~adi@80.97.64.55> has quit IRC14:21
*** armpit <armpit!~armpit@2601:202:4000:1184:ad3f:3096:6add:98d8> has quit IRC14:23
*** ant_work <ant_work!~ant__@host138-188-dynamic.50-82-r.retail.telecomitalia.it> has quit IRC14:26
*** aratiu <aratiu!~adi@80.97.64.55> has joined #yocto14:26
*** joseppc <joseppc!~josep@sestofw01.enea.se> has joined #yocto14:26
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto14:26
JPEWfberg: You shouldn't need the -dev package at runtime (via RDEPENDS), only build time (via DEPENDS).14:27
JPEWDEPENDS += "libpam-pwdfile" should be sufficent14:27
fbergJPEW: Maybe I'm wong but as far as I know I need the libpam-pwdfile.so at runtime14:28
fbergand this file is shipped with libpam-pwdfile-dev package14:28
fberg*pam_pwdfile.so14:29
JPEWfberg: Usually at "runtime" you link against a versioned library. The unversioned library is only for deveopment14:29
rburtonfberg: then the libpam-pwdfile package is broken14:30
fbergyes, in fact pam_wpdfile.so is a symbolic link14:30
rburtonoh its even more broken14:30
fbergthe versioned library is pam_pwdfile.so.1.0.0 shipped with libam-pwdfile package14:31
fbergrbuton: :o14:31
rburtonPAM modules are in /lib/security/libpam_*.so14:31
*** majuk <majuk!~majuk@75-163-194-62.clsp.qwest.net> has joined #yocto14:31
rburtonthats a real file, not a symlink, and there should not be symlinks14:31
rburtonits not a library, it's a module14:32
rburtonassuming this is the makefile, it does the right thing: https://github.com/tiwe-de/libpam-pwdfile/blob/master/Makefile14:32
fberglet me explain. I need to use vsftpd with virtual users. To enable virtual user I must have the pam_pwdfile.so. Since ther is no any out of the box recipe that ship pam_pwdifle.so, I have created one14:33
fberghttps://pastebin.com/WtSdXdh114:34
rburtonwhere to start14:34
rburtonline 5, no PR required14:34
rburtonline 7, don't use /archive/ links as they'll change14:34
rburtonline 15, name the recipe correctly and you can remove14:34
rburtonline 18 onwards, why are you inventing versions?14:35
*** armpit <armpit!~armpit@2601:202:4000:1184:adb4:757c:de15:c877> has joined #yocto14:35
*** majuk <majuk!~majuk@75-163-194-62.clsp.qwest.net> has quit IRC14:35
rburtonit comes with a makefile which does the right thing.  just have a do_install that does 'oe_runmake DESTDIR='${D}' install'14:36
fbergrburton: I have named it 1.0.0 since tha erchive referes to the 1.0.0 tag14:36
rburtonfberg: that's not what library versions are14:36
rburtonthe question you should be asking is "why doesn't the makefile do this"14:36
rburtonhttps://github.com/tiwe-de/libpam-pwdfile/blob/master/Makefile#L2914:36
rburtonthe answer is because PAM modules are not libraries, they're modules.  they don't get versioned.14:37
rburtonthere's no development package for a module because you can't link to a module14:37
fbergrburton: please be gentle with me. I'm not a software developer :)14:37
rburtonjust put $base_libdir/security into FILES_PN and you're done14:37
rburtonto expand on the /archive/ thing, those tarballs are generated on demand by github.  it's very annoying when the day after you ship something the tarball regenerates and your checksums are wrong.14:38
fbergrburton: thanks, so I will remove the version number and use oe_runmake DESTDIR='${D}' install14:38
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:38
-YoctoAutoBuilder- build #977 of nightly-ppc is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-ppc/builds/97714:39
rburtonthis package doesn't have proper tarballs so best practise is to do a git fetch14:39
fbergok, I will remove the archive SRC14:39
fbergthanks !14:39
*** majuk <majuk!~majuk@75-163-194-62.clsp.qwest.net> has joined #yocto14:40
*** ntl <ntl!~nathanl@65-36-80-8.dyn.grandenetworks.net> has joined #yocto14:41
*** droman <droman!~david@nat01.ifae.es> has quit IRC14:41
*** adelcast <adelcast!~adelcast@130.164.62.135> has quit IRC14:45
*** adelcast <adelcast!~adelcast@130.164.62.135> has joined #yocto14:45
daniele_dthanks for now and bye!14:47
*** daniele_d <daniele_d!~daniele@94.138.189.133> has quit IRC14:47
*** varjag <varjag!~user@122.62-97-226.bkkb.no> has quit IRC14:49
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has quit IRC14:51
prabhakarladHi, does DEPENDS also affect TARGET_CFLAGS  ? for example I want to add DEPENDS = "glib-2.0", so that I can include glib.h in a application, but I dont see the CFLAGS appended am I missing something ?14:53
LetoThe2ndprabhakarlad: nope, that are two independent thngs.14:55
LetoThe2ndprabhakarlad: DEPENDS tells bitbake that it has to make sure everything is in place.14:55
LetoThe2ndprabhakarlad: the actual generation of flags etc is up to the buildsystem that the source code uses internally, e.g. autotools, cmake, meson,...14:55
-YoctoAutoBuilder- build #1027 of nightly-arm is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-arm/builds/102714:56
rburtonprabhakarlad: if your code wants to use glib then it should use pkgconfig to get the flags as usual14:56
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has joined #yocto14:59
prabhakarladLetoThe2nd: rburton: thank you for your suggestion I did manually add the includes something like this "TARGET_CFLAGS += "-I${STAGING_INCDIR} -I${STAGING_INCDIR}/glib-2.0 -I${STAGING_LIBDIR}/glib-2.0/include/"" , as  I am adding my custom application14:59
prabhakarladsince I am not using the autotools, cmake I had to manually add them..14:59
LetoThe2ndprabhakarlad: then you're doing it wrong, cmake can certainly use pkg-config to properly detect them15:00
prabhakarladLetoThe2nd: sorry for my typo earlier I meant I am not using cmake/autotools/meason, I have just a simple Makefile15:02
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto15:02
*** andycooper <andycooper!uid246432@gateway/web/irccloud.com/x-zpsntmjvervpeajt> has joined #yocto15:04
-YoctoAutoBuilder- build #954 of nightly-mips64 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-mips64/builds/95415:04
LetoThe2ndprabhakarlad: well then, enjoy the pain :-D15:04
LetoThe2ndyou should *totally* still pour pkg-support into it15:04
rburtonprabhakarlad: use pkgconfig from your makefile15:05
*** TooTallTims_ <TooTallTims_!~quassel@2603:300b:1b:fd00:d13d:fa61:1e6e:1851> has joined #yocto15:07
*** yann|work <yann|work!~yann@37.173.81.176> has quit IRC15:10
prabhakarladrburton: Yes thats a good option to use pkgconfig from your makefile thank you :)15:13
*** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC15:13
*** fberg <fberg!~kappe@93-42-191-214.ip88.fastwebnet.it> has quit IRC15:13
*** yann|work <yann|work!~yann@37.173.81.176> has joined #yocto15:15
*** frieder <frieder!~frieder@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has quit IRC15:20
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC15:21
JPEWI know it is possible to share sstate between mulitple builders over NFS, is it also possible (safe?) to share the download cache over NFS?15:23
*** rajm <rajm!~robertmar@cpc126996-macc4-2-0-cust25.1-3.cable.virginm.net> has joined #yocto15:28
*** yann|work <yann|work!~yann@37.173.81.176> has quit IRC15:29
rburtonJPEW: i wouldn't trust nfs locking enough to do that15:38
JPEWrburton: sstate, downloads, or both?15:43
-YoctoAutoBuilder- build #968 of nightly-qa-extras is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/96815:46
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC15:47
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto15:48
-YoctoAutoBuilder- build #1049 of nightly is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly/builds/104915:52
*** rovanceo_ <rovanceo_!~rovanceo@80.97.64.55> has quit IRC15:56
rburtonJPEW: anything.  don't trust nfs :)15:58
khemwe have been using nfs for quite some time now without issues, there was a locking issue we faced which is already upstreamed into bitbake15:59
*** rovanceo <rovanceo!~rovanceo@80.97.64.55> has joined #yocto15:59
rburtoniirc you potentially have races to write to DL_DIR but the worst case is two machines download the same file and put it in the cache, there's no corruption16:00
khemyeah ofcourse, we do not write to it simultaneously16:01
khemthere is one autobuilder task to rsync it from official builds16:01
khemone good thing with nfs is that it will symlink into dldir of the consumer build so kind of saves space16:02
mckoanJPEW: it is possible to share sstate between mulitple builders over NFS but is not working though16:02
khemI dont think if you want consumers to share its possible but if you want to write to sstate cache at same time I would recommend not to16:03
rburtonJPEW: fwiw the yocto autobuilder has the master do a fetchall to populate DL_DIR once, and then sstate is rsync'd to the master after every build (using the master as a read-only sstate mirror)16:04
JPEWkhem: Hmm, ok. Do you know when that bitbake issue was fixed?16:04
khemso have a official build like nightly or something populate/refresh the sstate everyday and then run with that ssate for rest of day16:04
khemlog time ago probably a year or so16:04
JPEWK, that might not be recent enough for us, we are sadly still on morty16:05
khemyou can choose to do official builds more often than 24hrs16:05
khemmorty will have it16:05
JPEWYa, we have been using sstate over HTTP, but our nightly builds are.... questionable to say the least (which is an entirely different story)16:06
khemhttp://git.openembedded.org/bitbake/commit/?id=5a53e7d7b017769a6eb0f0a6335735a1fe51a5ec16:06
JPEWkhem: so you are using NFS for read-only sstate?16:07
khemyes16:07
khemand also for download mirror16:07
mckoanJPEW: NFS and sstate works only as read only16:07
khembased on ubuntu 14.0416:07
JPEWOK, that makes sense. Thanks all16:08
*** joeythesaint <joeythesaint!~joe@2605:6400:2:fed5:22:41:45ec:bf91> has joined #yocto16:09
*** scottrif <scottrif!~scottrif@191.97.80.19> has joined #yocto16:14
*** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-84-4.fbx.proxad.net> has quit IRC16:14
*** rovanceo <rovanceo!~rovanceo@80.97.64.55> has quit IRC16:15
*** rovanceo <rovanceo!~rovanceo@80.97.64.55> has joined #yocto16:17
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC16:19
-YoctoAutoBuilder- build #1011 of nightly-oe-selftest is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/101116:23
armpitRP, don't take any stable/*, I broke all of them :)16:24
RParmpit: nice :)16:24
*** mckoan is now known as mckoan|away16:25
*** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has joined #yocto16:28
*** TooTallTims_ <TooTallTims_!~quassel@2603:300b:1b:fd00:d13d:fa61:1e6e:1851> has quit IRC16:38
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto16:40
*** stephano <stephano!stephano@nat/intel/x-zzszdgxtszmrxisd> has joined #yocto16:42
rburtonarmpit: skills!16:48
*** martinkelly1 <martinkelly1!~martin@174-21-182-65.tukw.qwest.net> has joined #yocto16:49
*** Bunio_FH <Bunio_FH!~bunio@213.46.252.136> has quit IRC16:52
*** aratiu <aratiu!~adi@80.97.64.55> has quit IRC16:56
*** aratiu <aratiu!~adi@80.97.64.55> has joined #yocto16:58
*** Toumasu <Toumasu!~lty@78-22-168-64.access.telenet.be> has joined #yocto17:05
*** mdnneo <mdnneo!~umaucher@217.89.178.116> has quit IRC17:07
*** sno <sno!~sno@p54A24523.dip0.t-ipconnect.de> has quit IRC17:11
*** fl0v0 <fl0v0!~fvo@i577B9BA5.versanet.de> has quit IRC17:15
*** Toumasu <Toumasu!~lty@78-22-168-64.access.telenet.be> has quit IRC17:20
*** mihais <mihais!~mihaiserb@86.120.134.70> has quit IRC17:24
*** martinkelly1 <martinkelly1!~martin@174-21-182-65.tukw.qwest.net> has quit IRC17:24
*** rajm <rajm!~robertmar@cpc126996-macc4-2-0-cust25.1-3.cable.virginm.net> has quit IRC17:32
*** stephano <stephano!stephano@nat/intel/x-zzszdgxtszmrxisd> has quit IRC17:33
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has joined #yocto17:34
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto17:34
*** stephano <stephano!~stephano@134.134.139.83> has quit IRC17:35
*** stephano <stephano!~stephano@192.55.54.40> has joined #yocto17:36
*** flying_sausages_ <flying_sausages_!~flying_sa@static.88-198-40-49.clients.your-server.de> has joined #yocto17:42
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC17:46
*** colrack <colrack!~colrack@94.126.8.166> has quit IRC17:52
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has joined #yocto17:52
*** peacememories <peacememories!~textual@e246-176.eduroam.tuwien.ac.at> has quit IRC17:54
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:7518:8fc1:90a0:9603> has joined #yocto17:54
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has quit IRC17:54
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has joined #yocto17:55
*** aarcane <aarcane!~Christ@173.75.115.107> has joined #yocto17:56
aarcanewhy is there no image feature for wayland/weston like there is for x11, x11-base, and x11-sato?  Seems like a majour oversight...17:56
aarcanelike how is one supposed to do something like "${@bb.utils.contains('IMAGE_FEATURES', 'wayland-base', "packagegroup-mygroup-wayland", "", d)}"17:57
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto18:02
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC18:07
*** yann|work <yann|work!~yann@LFbn-1-9167-222.w86-238.abo.wanadoo.fr> has joined #yocto18:14
*** ladidadida <ladidadida!~ladidadid@ipbcc3cd17.dynamic.kabel-deutschland.de> has joined #yocto18:26
*** gabriel_ <gabriel_!~gabriel@177.92.19.154> has joined #yocto18:26
*** rewitt <rewitt!rewitt@nat/intel/x-jdliwirkhpfdjrdk> has quit IRC18:26
gabriel_Can I fetch files for a .bbappend though a git repo?18:28
gabriel_I tried adding the git path to the SRC_URI but it doesnt seen to work18:29
*** stephano <stephano!~stephano@192.55.54.40> has quit IRC18:29
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto18:30
*** stephano <stephano!~stephano@134.134.139.83> has quit IRC18:30
*** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has quit IRC18:34
otaviohello18:34
otaviois anyone involved in mingw layer maintenance?18:35
*** vmeson <vmeson!~rmacleod@192-0-133-4.cpe.teksavvy.com> has joined #yocto18:35
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto18:35
*** toanju <toanju!~toanju@xd527ab0c.dyn.telefonica.de> has joined #yocto18:37
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC18:39
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has quit IRC18:45
yoctiNew news from stackoverflow: How to add a new library using Yocto <https://stackoverflow.com/questions/28792597/how-to-add-a-new-library-using-yocto>18:45
*** gabriel_ <gabriel_!~gabriel@177.92.19.154> has quit IRC18:48
*** kaspter <kaspter!~Instantbi@115.216.25.143> has quit IRC18:51
*** kaspter <kaspter!~Instantbi@115.216.25.143> has joined #yocto18:51
*** ladidadida <ladidadida!~ladidadid@ipbcc3cd17.dynamic.kabel-deutschland.de> has quit IRC18:55
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has quit IRC18:55
ksjhow would I make a do_unpack_append? doesn't seem to work for me19:00
paulbarkerFetch & unpack are pretty special. You might be better with a _prepend on a later function instead of an _append on do_unpack19:02
ksjah okay, what about do_patch? could I make an append on that then?19:02
paulbarkerI've never actually looked where do_patch is implemented. Give it a try and see what happens :)19:03
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC19:04
paulbarkerare you trying to write your append in shell or python?19:04
ksjin shell19:04
ksjbut I really need to either make a shell script execute after either unpack or before patch19:05
paulbarkerAh ok. Those early tasks are in python19:05
ksjah I see19:05
paulbarkerYou could define a new task between unpack and patch that can be in shell19:05
ksjpaulbarker: I need the WORKDIR definition in the bb file which I am writing a bbappend for19:06
ksjit seems it can actually call my new task after do_patch but it can't see the WORKDIR definition now19:06
ksjI used do_patch[postfuncs] to call this shell code19:07
paulbarkerI think postfuncs is the wrong approach, not sure what that has access to19:07
paulbarkerHave a look at https://www.yoctoproject.org/docs/2.4.2/bitbake-user-manual/bitbake-user-manual.html#promoting-a-function-to-a-task19:07
paulbarkerbut obviously substitute a shell function instead of the python function used in the example19:08
ksjpaulbarker: seems like it adds my function now but something odd about it as it doesn't seem to be run19:18
aarcaneoiy, why does my packagegroup (seem to) RDEPEND every packagegroup defined inside it?  I want to be able to choose either x11 or wayland or both, but I always end up with both...19:19
aarcanehttps://pastebin.ca/401801819:19
paulbarkerksj: could you post the bbappend via a pastebin?19:19
ksjyea will do that19:20
aarcaneeven if I bitbake -g packagegroup-myproject-cli (Which specifically doesn't include -x11 or -wayland ) I get *both* versions of chromium showing up in the depends.dot files and the pn_buildlist19:21
ksjpaulbarker: https://pastebin.com/raw/JF84KaGe19:22
paulbarkerksj: You've said your task needs to be after do_patch but not before anything. So nothing depends on your task19:22
ksjI can see thatt he files are put into the $(WORKDIR) folder19:22
ksjpaulbarker: there's nothing running after this task19:23
paulbarkerTry "addtask something_j120 after do_patch before do_configure"19:23
paulbarkeror "before do_patch"19:23
ksjpaulbarker: ah that seemed to work but now it says it can't see my directories in the $(WORKSPACE)19:24
ksj"cannot create regular file '/Linux_for_Tegra/': Not a directory"19:25
paulbarkerYou need to use {} not ()19:25
ksjoh lol19:25
paulbarkeraarcane: Not sure you need to set PROVIDES, that might be causing bitbake some confusion19:26
ksjpaulbarker: wait I am using {}19:26
ksjI mistyped in irc19:26
paulbarkerksj: In the pastebin file you have both {} and ()19:26
ksjoh god what am I doing19:27
ksjhuh would you look at that, it did the trick :p19:28
ksjthanks a lot paulbarker19:28
*** mihais <mihais!~mihaiserb@86.106.54.225> has joined #yocto19:33
*** flying_sausages <flying_sausages!~flying_sa@2a01:4f8:161:610b::2> has quit IRC19:37
*** flying_sausages_ is now known as flying_sausages19:37
*** sjolley <sjolley!sjolley@nat/intel/x-ebtizgyfabcrylcj> has joined #yocto19:48
aarcanepaulbarker, if I do that, I get "Nothing PROVIDES 'packagegroup-myproject-cli'. Close matches:"19:48
paulbarkerLooking at http://git.openembedded.org/openembedded-core/tree/meta/recipes-sato/packagegroups/packagegroup-core-x11-sato.bb for reference you shouldn't need to set PROVIDES19:52
paulbarkerI would avoid making PACKAGES conditional on DISTRO_FEATURES. Maybe define packagegroup-myproject-gui where the contents of it's RDEPENDS is dependent on DISTRO_FEATURES instead19:53
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto19:55
*** bluelightning <bluelightning!~paul@118.148.68.78> has joined #yocto19:57
*** bluelightning <bluelightning!~paul@118.148.68.78> has quit IRC19:57
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:57
aarcanepaulbarker, I used core/packagegroups/packagegroup-base.bb as a template, built up from there19:57
aarcanepaulbarker, anyway, if I just throw both packages into PACKAGES then I just get both installed no matter which I request.20:00
paulbarkerok, that is strange. Just read through packagegroup-base.bb and looks like you're doing pretty much the same as it is doing20:01
paulbarkerI hadn't seen PROVIDES set for a packagegroup recipe like that before20:01
*** AbleBacon_ <AbleBacon_!~AbleBacon@unaffiliated/ablebacon> has joined #yocto20:01
paulbarkerOne concern is that you're mixing quotes when you use bb.utils.contains20:02
aarcaneshould I use all ' or all " ?20:02
paulbarkerIf your outer quotes for PACKAGES is "", you should probably stick to '' inside as I'm not sure how bitbake's parser handles nested quotes20:02
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has quit IRC20:03
*** AbleBacon_ is now known as AbleBacon20:04
paulbarkerOh, hang on. You don't define packagegroup-myproject in PACKAGES but you set RDEPENDS for it20:05
aarcanepaulbarker, I've added and removed both extensively20:05
aarcanepaulbarker, no change on either20:05
paulbarkerI'm a bit lost then and I need to get going sorry. Last suggestion is to do a really basic check, run `bitbake packagegroup-myproject -e` and check that DISTRO_FEATURES, PACKAGES and RDEPENDS for each package is set as you expect20:07
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has joined #yocto20:15
aarcaneand of course a packagegroup apparently has no knowledge of IMAGE_FEATURES because keying on that does no good...20:17
*** TooTallTims_ <TooTallTims_!~quassel@2603:300b:1b:fd00:f0f4:4819:31ac:2469> has joined #yocto20:26
*** TooTallTims <TooTallTims!~quassel@2603:300b:1b:fd00:f0f4:4819:31ac:2469> has joined #yocto20:28
*** marka <marka!~masselst@128.224.252.2> has quit IRC20:32
*** zarzar <zarzar!~zarzar@184.75.233.58> has quit IRC20:54
*** Snert_ <Snert_!~snert_@65.74.8.146> has quit IRC20:55
*** Snert_ <Snert_!~snert_@65.74.8.146> has joined #yocto20:56
*** thaytan <thaytan!~thaytan@180-150-118-156.NBN.mel.aussiebb.net> has joined #yocto20:58
*** TooTallTims <TooTallTims!~quassel@2603:300b:1b:fd00:f0f4:4819:31ac:2469> has quit IRC21:06
*** TooTallTims <TooTallTims!~quassel@2603:300b:1b:fd00:f0f4:4819:31ac:2469> has joined #yocto21:07
*** pohly <pohly!~pohly@p54849CF1.dip0.t-ipconnect.de> has quit IRC21:12
*** toanju <toanju!~toanju@xd527ab0c.dyn.telefonica.de> has quit IRC21:19
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has quit IRC21:23
*** mihais <mihais!~mihaiserb@86.106.54.225> has quit IRC21:29
*** rburton_ <rburton_!~textual@35.106.2.81.in-addr.arpa> has joined #yocto21:41
aarcaneuhm...  since I'm planning largely a read-only rootfs and no installable packages..  can I configure yocto to not build packages, and if I do, will it still be able to populate the rootfs and create a functional image?21:42
JPEWA read-only rootfs still requires packages. They get installed into build the image, then it is made read-only after that21:43
JPEW(basically)21:44
aarcaneJPEW, I was afraid of that, but was hopeful it could use the built software without first packaging and then depackaging it.21:44
aarcanebasically to save some CPU time and maybe disk space (I don't know how much of the built files are kept around...)21:45
JPEWIf you're worried about the disk space, you can do INHERIT += "rm_work" in local.conf21:47
JPEWhttps://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#ref-classes-rm-work21:47
aarcaneJPEW, not that worried.  It just seems a waste to package and then unpackage if I'm never going to update as a single package, y'kno?21:48
JPEWaarcane: Sure. I assure that as you get more use to it, you'll realize it makes perfect sense to do it that way :)21:50
*** d3r3k <d3r3k!uid190567@gateway/web/irccloud.com/x-iaipnvkzzhpxascb> has joined #yocto22:07
*** stephano <stephano!~stephano@134.134.139.83> has quit IRC22:15
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto22:15
*** gtristan <gtristan!~tristanva@110.11.179.89> has quit IRC22:18
*** dreyna <dreyna!~dreyna@2601:646:4201:b1a0:7518:8fc1:90a0:9603> has quit IRC22:21
*** stephano <stephano!~stephano@134.134.139.83> has quit IRC22:22
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto22:22
*** JaMa <JaMa!~martin@217.30.68.212> has joined #yocto22:27
*** stephano <stephano!~stephano@134.134.139.83> has quit IRC22:48
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto22:49
kergothIMAGE_FEATURES is image-specific by definition. it can differ from one image to another, at the time we build a packagegroup we have no idea what images will install it.22:51
kergothaarcane: ^22:51
aarcanekergoth, that makes sense, except that if we build an image, we have IMAGE_FEATURES set when we include the packagegroup, and can therefore only build or provide the packages and packagegroups we need now, and build the rest later.  Anyway...  Not sure what I changed, but I got it working finally.  also, pn_buildlist and the other .dot files build with -g don't accurately reflect the image output...22:53
kergothno, you're misunderstanding how the build works22:53
kergothrecipes produce binary packages which are then installed by image recipes22:54
kergoththat binary package is created once, not once per image22:54
aarcanekergoth, correct22:54
kergothpackagegroups emit empty binary packages with specific depnedencies22:54
kergoththey are not pure metadata22:54
aarcaneHmm...22:54
aarcanethat makes sense and is pretty much what I expected22:54
kergothit sounds like you might just want to bypass the packagegroup entirely in favor of explicit dependencies in the image, either directly in IMAGE_INSTALL or via image features22:55
kergothor alter how both the image and packagegroup are constructed with a distro feature, depending on your requirements22:56
aarcaneI just want to key off IMAGE_FEATURES to know which packagegroups to install...  and I have that working finally.  I had to create a new bbclass that inherits core-image and adds some new FEATURE_PACKAGES and IMAGE_FEATURE_CONFLICTS tags to it.22:57
kergothah, yes, that's definitely doable22:57
aarcanesince I have one distro, one basic everything, and the only difference between the two images (Future: 3) is which graphical environment loads the webpage and throws it onto the touch screen.22:58
*** scottrif <scottrif!~scottrif@191.97.80.19> has quit IRC23:01
aarcanenow I'm struggling slightly with needing a package version other than the latest and no option to specify RDEPENDS pkgname == version and therefore which .conf file to plug it into.  It's in layer.conf now since the version requirement is for a package in the layer and I'm not building a *custom* distro, just using poky.23:01
*** scottrif <scottrif!~scottrif@191.97.80.19> has joined #yocto23:03
*** TooTallTims <TooTallTims!~quassel@2603:300b:1b:fd00:f0f4:4819:31ac:2469> has quit IRC23:18
*** stephano <stephano!~stephano@134.134.139.83> has quit IRC23:24
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto23:25
*** majuk <majuk!~majuk@75-163-194-62.clsp.qwest.net> has quit IRC23:39
*** majuk <majuk!~majuk@75-163-194-62.clsp.qwest.net> has joined #yocto23:40
*** majuk <majuk!~majuk@75-163-194-62.clsp.qwest.net> has quit IRC23:41
*** majuk <majuk!~majuk@75-163-194-62.clsp.qwest.net> has joined #yocto23:41
*** Willy-- <Willy--!~william@142.134.27.48> has joined #yocto23:53
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has quit IRC23:56

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!