00:07.37 | *** join/#oe nitink (nitink@nat/intel/x-evzusekrnxcbtxam) |
00:32.17 | *** join/#oe W1N9Zr0 (~w1n9zr0@2605:6400:20:895b:22:0:1c4:4d6a) |
00:34.34 | *** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net) |
00:44.07 | *** join/#oe dylan__ (~dylan@blac972525.lnk.telstra.net) |
00:55.44 | *** join/#oe Shawn286 (~Shawn@unaffiliated/shawn156) |
01:15.27 | *** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net) |
01:44.39 | *** join/#oe Jafura (~Jean-Fran@2a02:2788:114:11ce:cc13:8316:54bf:e98) |
02:17.21 | *** join/#oe ccube (ccube@nx.mindrunner.de) |
02:21.26 | *** join/#oe fcooper (~a0273011@nat/ti/x-dbsgewepjsxmwhll) |
02:36.46 | *** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net) |
02:47.57 | *** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net) |
02:51.08 | *** join/#oe s3v3n62mm2 (~s3v3n62mm@p5DDC0E74.dip0.t-ipconnect.de) |
03:04.40 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
03:07.27 | *** join/#oe GusBrick_ (~GusBricke@cre1513898.lnk.telstra.net) |
03:18.13 | *** join/#oe rogue2 (~pompomJui@41.0.38.138) |
03:25.55 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
03:26.11 | *** join/#oe ccube (ccube@nx.mindrunner.de) |
03:38.17 | *** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net) |
03:42.12 | *** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net) |
05:36.51 | *** join/#oe clio (~andrej@85.159.109.222) |
05:47.23 | *** join/#oe tasslehoff (~Tasslehof@77.40.182.98) |
06:02.19 | *** join/#oe g1zer0 (~gizero@host168-65-static.12-87-b.business.telecomitalia.it) |
06:19.47 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
06:31.14 | tasslehoff | since I have bothered #oe with this the past days, I just want to say that for 720p@60 the qt5 performance is decent on my wandboard :) |
06:31.43 | tasslehoff | 1080p@60 was just totally outside its comfort zone.. |
06:31.48 | tasslehoff | good morning! |
06:37.55 | *** join/#oe dlan (~dennis@116.228.88.131) |
06:37.55 | *** join/#oe dlan (~dennis@gentoo/developer/dlan) |
06:48.01 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
06:51.01 | *** join/#oe diego_r (~diego@host65-246-static.10-188-b.business.telecomitalia.it) |
06:53.12 | *** join/#oe dlan (~dennis@gentoo/developer/dlan) |
06:53.31 | *** join/#oe ftagius (~fagius@99-178-168-231.lightspeed.rlghnc.sbcglobal.net) |
07:04.52 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
07:10.38 | *** join/#oe ao2 (~ao2@host128-138-dynamic.2-79-r.retail.telecomitalia.it) |
07:11.46 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
07:21.06 | *** join/#oe jbrianceau_away (uid10952@gateway/web/irccloud.com/x-ajhqziczzkooelaf) |
07:23.01 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
07:25.35 | *** join/#oe kroon (~kroon@fw.mikrodidakt.se) |
07:31.02 | *** join/#oe ao2 (~ao2@host61-146-dynamic.6-87-r.retail.telecomitalia.it) |
07:33.27 | *** join/#oe ant_work (~ant__@host54-128-static.10-188-b.business.telecomitalia.it) |
07:34.38 | *** join/#oe belen (~Adium@190.227.187.81.in-addr.arpa) |
07:40.02 | *** join/#oe mago__ (~mago@c193-14-123-186.cust.tele2.se) |
07:48.40 | *** join/#oe clio (~andrej@85.159.109.222) |
07:57.38 | rogue2 | good job men! |
08:05.18 | *** join/#oe afournier (~admin@46.255.181.29) |
08:05.29 | afournier | morning ! |
08:08.13 | *** join/#oe woglinde (~henning@91-64-83-166-dynip.superkabel.de) |
08:18.07 | mckoan | good morning |
08:19.04 | mckoan | IMAGE_INSTALL_append = does the same as IMAGE_INSTALL += ? |
08:23.13 | woglinde | no |
08:23.18 | woglinde | *g* |
08:23.32 | woglinde | append appends to the variable |
08:23.47 | woglinde | += appends the string and replaces the variable |
08:24.24 | woglinde | so thats why you ahve to take care about the whitspaces when using append |
08:24.33 | woglinde | bye till later |
08:25.46 | *** join/#oe stefan_schmidt (~stefan@p20030048094A3BA6F2DEF1FFFE6228F7.dip0.t-ipconnect.de) |
08:26.33 | mckoan | woglinde: so different behaviour but identical result |
08:28.51 | mckoan | https://lists.yoctoproject.org/pipermail/yocto/2012-June/007363.html |
08:29.40 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
08:33.30 | *** join/#oe ao2 (~ao2@host15-146-dynamic.6-87-r.retail.telecomitalia.it) |
08:33.46 | afournier | when using the built distro, the term is unable to display UTF8 i feel like i forget to declare something in the distro... i have LOCALE_UTF8_ONLY = "1" |
08:33.46 | afournier | <PROTECTED> |
08:34.21 | kroon | mckoan, i think one also needs to consider that the _append's are applied _after_ the recipe and its dependencies has been parsed, at least *i think* this is the case |
08:35.07 | XorA | it all goes hideously wrong when someone does BLAH_append += "" |
08:35.13 | kroon | mckoan, so setting foobar_append in a .bbappend would overwrite and wipeout a foobar_append set in the main recipe |
08:35.23 | XorA | which for some reason used to be really common |
08:36.11 | kroon | XorA, is BLAH_append += "" discouraged ? |
08:36.43 | XorA | kroon: it should be used with care, in most cases it was just wrong as what they meant was _append without the += |
08:36.56 | XorA | kroon: but it evaluates twice at different times |
08:39.26 | *** join/#oe bluelightning_ (~paul@pdpc/supporter/professional/bluelightning) |
08:41.25 | kroon | XorA, I guess the thing I'm struggling with in understanding in general, is how and when bitbake evaluates variables ... |
08:41.40 | XorA | kroon: aim for the simplest solution |
08:42.19 | mckoan | likes the enlightening comments above |
08:42.34 | mckoan | thx |
08:47.25 | bencoh | :) |
08:51.22 | kroon | bluelightning, hi. do you happen to know if it is correct to state that "_append"'s are applied _after_ a recipe has been parsed ? |
08:52.31 | bluelightning | kroon: well, the recipe parsing step is really just about populating the cache with values of variables that bitbake needs to be able to look up quickly |
08:52.44 | bluelightning | kroon: variable continues to occur after that |
08:52.53 | bluelightning | er, variable expansion I meant to type |
08:53.30 | bluelightning | references in variable values are expanded upon demand, basically |
08:54.05 | bluelightning | although you can force it immediately by using := |
08:54.19 | bluelightning | but generally on-demand is the right thing for almost all cases |
08:55.30 | bluelightning | when we talk about operations on variable values, those do happen at different times however |
08:56.08 | bluelightning | = += =+ .= and =. will change the value immediately |
08:56.52 | bluelightning | _append, _prepend and _remove will store the value to be appended / prepended / removed and then later each time the value is expanded the operations will be applied |
08:57.23 | bluelightning | ??= is deferred in the same way as well |
08:57.51 | bluelightning | ( ?= is immediate, it either takes effect or not depending on whether the variable has a value at the time the statement is parsed) |
09:00.13 | *** join/#oe clio (~andrej@85.159.109.222) |
09:00.16 | *** join/#oe rick___ (5a509091@gateway/web/freenode/ip.90.80.144.145) |
09:05.30 | *** join/#oe falk0n (~falk0n@a85-138-88-181.cpe.netcabo.pt) |
09:07.51 | *** join/#oe woglinde (~henning@91-64-80-232-dynip.superkabel.de) |
09:09.35 | *** join/#oe ao2 (~ao2@host147-17-dynamic.1-87-r.retail.telecomitalia.it) |
09:16.54 | *** join/#oe ionte (~jonatan@c-3345e055.164-1-64736c10.cust.bredbandsbolaget.se) |
09:29.44 | *** join/#oe anarsoul (~anarsoul@178.124.194.242) |
09:43.00 | *** join/#oe ao2 (~ao2@host177-139-dynamic.2-79-r.retail.telecomitalia.it) |
09:46.00 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
09:59.38 | *** join/#oe kristoffer (~kristoffe@ua-83-227-162-207.cust.bredbandsbolaget.se) |
10:04.13 | *** join/#oe ao2 (~ao2@host5-147-dynamic.2-79-r.retail.telecomitalia.it) |
10:12.11 | mckoan | how do you enable v4l2 in gstreamer? |
10:13.09 | mckoan | IMAGE_INSTALL_append = " gstreamer gst-meta-base gst-plugins-good gst-plugins-base v4l-utils " |
10:13.27 | mckoan | I have been googling for hours |
10:13.44 | mckoan | ERROR: pipeline could not be constructed: no element "v4l2src" |
10:14.15 | bluelightning | mckoan: I think the gst-plugins-good / gst-plugins-base packages are actually empty |
10:14.30 | bluelightning | mckoan: you want gst-plugins-good-meta and gst-plugins-base-meta |
10:14.40 | bluelightning | (there is a bug open for that, it's pretty annoying) |
10:14.57 | rogue2 | is there some base recipy that contains variables for all other recipies? |
10:15.31 | bluelightning | pompomJuice: not a base recipe, but there is a meta/classes/base.bbclass that is inherited implicitly by every recipe |
10:15.40 | pompomJuice | perfect |
10:15.42 | pompomJuice | thanks |
10:15.50 | mckoan | bluelightning: thx, bitbaking |
10:16.07 | bluelightning | pompomJuice: but you wouldn't modify that if that's what you're thinking of |
10:16.34 | pompomJuice | I presume I can add to it somehow... I want to save a variable somewhere that can be switched on inside the recipies for prod and dev mode |
10:16.45 | pompomJuice | ok |
10:16.47 | bluelightning | pompomJuice: all recipes start with the global configuration, that's typically what you change (or, if it's something you want to change only for a group of recipes, create a new class the recipes can inherit) |
10:17.14 | pompomJuice | the problem I have is merging between dev and prod refs |
10:17.19 | pompomJuice | the dev tree contains dev settings |
10:17.26 | koen | there's DISTRO_TYPE = "debug" for things like that |
10:17.31 | pompomJuice | thats what I want |
10:17.35 | pompomJuice | ok |
10:17.37 | pompomJuice | perfect |
10:17.40 | pompomJuice | I called mine IMAGE_MODE |
10:17.54 | pompomJuice | I can switch on DISTRO_TYPE in all recipies then |
10:18.08 | pompomJuice | thanks |
10:22.37 | *** join/#oe ao2 (~ao2@host208-79-dynamic.61-82-r.retail.telecomitalia.it) |
10:23.08 | bluelightning | is DISTRO_TYPE something we still use? |
10:23.47 | bluelightning | I mean, there's nothing to stop you using it - but there's nothing intrinsic to that variable in OE-Core at least |
10:24.01 | pompomJuice | aah |
10:24.10 | pompomJuice | it looks used |
10:24.25 | pompomJuice | not sure I understand how to use it properly |
10:24.30 | pompomJuice | where to overwrite it |
10:25.16 | pompomJuice | currently I pulled a trick where I have a /conf/distro/angstrom-v2014.06.conf that is overriding the one in angstrom |
10:25.30 | pompomJuice | instead of this include mechanism that I dont have time for |
10:28.38 | pompomJuice | unless it as easy as putting .inc files in /conf/distro/include? |
10:28.51 | pompomJuice | in my layer |
10:30.48 | mckoan | bluelightning: AFAYK is it possible to send gstreamer on framebuffer? |
10:37.52 | *** join/#oe woglinde (~henning@91-64-80-232-dynip.superkabel.de) |
10:47.17 | bluelightning | mckoan: I don't know, sorry |
10:47.37 | *** join/#oe Jafura (~Jean-Fran@2a02:2788:114:11ce:c7f:ab2b:5a69:4313) |
10:49.04 | *** join/#oe ao2 (~ao2@host78-81-dynamic.57-82-r.retail.telecomitalia.it) |
10:52.28 | mckoan | yes, at last I suceeded |
10:53.10 | mckoan | bluelightning: actually I needed only to tacke a shoot |
11:01.33 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
11:07.43 | *** join/#oe ao2 (~ao2@host88-82-dynamic.57-82-r.retail.telecomitalia.it) |
11:15.46 | pompomJuice | IMAGE_MODE = '${@base_conditional("DISTRO_TYPE", "release", "prod", "debug", "dev")}' |
11:15.47 | pompomJuice | AC_BUILD_STORER_STREAM = "${IMAGE_MODE}_storer" |
11:15.47 | pompomJuice | AC_BUILD_DOTNET_STREAM="${IMAGE_MODE}_dotnetfinal" |
11:15.47 | pompomJuice | AC_BUILD_MISC_STREAM="${IMAGE_MODE}_misc" |
11:16.48 | pompomJuice | , d |
11:17.39 | pompomJuice | nm |
11:25.49 | *** join/#oe mago__ (~mago@unaffiliated/blastur) |
11:38.23 | *** join/#oe ldnunes (~ldnunes_@177.35.70.10) |
12:14.38 | *** join/#oe joeythesaint (~joe@209.141.56.162) |
12:30.47 | *** join/#oe adelcast (~adelcast@130.164.62.249) |
12:36.23 | *** join/#oe ao2 (~ao2@host15-136-dynamic.11-87-r.retail.telecomitalia.it) |
12:45.07 | *** join/#oe woglinde (~henning@p5099b23e.dip0.t-ipconnect.de) |
12:52.08 | *** join/#oe woglinde (~henning@p5099b23e.dip0.t-ipconnect.de) |
12:53.08 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
12:54.53 | woglinde | bluelightning ping |
12:55.00 | bluelightning | woglinde: pong |
12:55.16 | woglinde | whois the dora maintainer? |
12:55.25 | bluelightning | of OE-Core or meta-oe? |
12:55.56 | woglinde | oe-core |
12:56.15 | bluelightning | Robert Yang |
12:56.29 | bluelightning | FYI: https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance |
12:57.27 | woglinde | ah okay |
12:57.44 | woglinde | thanks |
12:58.08 | woglinde | will give him some time for the perf stuff |
13:00.54 | *** join/#oe ao2 (~ao2@host153-151-dynamic.11-87-r.retail.telecomitalia.it) |
13:05.46 | afournier | i built lighttpd from oe, and when i started it with debug.log-request-handling = "enable", i noticed that the mesages contain path to sources because they use __FILE__,__LINE__. But as it has been built with oe, the path it wide ! So i am wondering if it would be a good idea to use -iremap src:dst in conjunction with --sysroot=path in order to hide the path, to make the output of program using __FILE__ more human readable, and to save some more bytes in binari |
13:18.27 | woglinde | afournier hm what? |
13:18.36 | afournier | :) |
13:20.36 | afournier | lighttpd uses __FILE__ in its source code, as sources are built somewhere on the host, __FILE__ contains a very long path + path to lighttpd source code |
13:20.59 | afournier | it's not a problem for lighttpd only, but i use it as an example |
13:22.55 | afournier | woglinde: do you get my point ? :) |
13:23.24 | woglinde | hm yes |
13:23.52 | woglinde | but better write to oe-core |
13:24.25 | afournier | ok |
13:30.45 | *** join/#oe tbr (dm8tbr@cl-45.waw-01.pl.sixxs.net) |
13:43.52 | *** join/#oe ajtag (~ajtag@cpc10-lee211-2-0-cust124.7-1.cable.virginm.net) |
13:45.10 | *** join/#oe tbr_ (dm8tbr@cl-790.ham-01.de.sixxs.net) |
13:48.46 | *** join/#oe ao2 (~ao2@host79-192-dynamic.3-87-r.retail.telecomitalia.it) |
13:55.10 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
13:55.41 | rick___ | when i try out the aotutool example on http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.htm i get "No rule to make target install" is the example incomplete? |
14:03.42 | bluelightning | rick___: it depends - if your Makefile does not provide an "install" target, you'll need to write your own do_install |
14:04.08 | bluelightning | the example probably assumes that the Makefile does provide that target |
14:07.37 | *** join/#oe ao2 (~ao2@host95-146-dynamic.3-87-r.retail.telecomitalia.it) |
14:09.55 | *** join/#oe adelcast (~adelcast@130.164.62.249) |
14:20.44 | *** join/#oe ant___ (~ant__@host54-128-static.10-188-b.business.telecomitalia.it) |
14:20.48 | *** join/#oe woglinde (~henning@91-64-83-166-dynip.superkabel.de) |
14:30.52 | rick___ | in what case do i use -b and not? |
14:31.02 | rick___ | bitbake -b |
14:40.22 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
14:51.52 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
14:56.03 | *** join/#oe nitink (~nitink@134.134.137.75) |
14:59.40 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
15:08.25 | bluelightning | rick___: generally, you should not use -b at all |
15:08.40 | bluelightning | I rarely use it |
15:09.49 | rick___ | bluelightning: a simple helloworld example (helloworld.c locallystored with no autotools) builds only with this option.. |
15:09.57 | *** join/#oe DJWillis (~djwillis@cpc2-trow6-2-0-cust204.aztw.cable.virginm.net) |
15:15.59 | bluelightning | rick___: that's probably because without -b, bitbake expects to find recipes via BBFILES |
15:16.53 | bluelightning | (and each layer you add to conf/bblayers.conf will extend BBFILES in its own conf/layer.conf to search directories within the layer for recipes) |
15:20.46 | *** join/#oe woglinde (~henning@91-64-80-232-dynip.superkabel.de) |
15:36.06 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
15:38.31 | *** join/#oe ao2 (~ao2@host50-138-dynamic.2-79-r.retail.telecomitalia.it) |
15:41.55 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
15:58.27 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
16:01.36 | *** join/#oe staylor (~staylor@mail.au-zone.com) |
16:22.42 | *** join/#oe ao2 (~ao2@host83-124-dynamic.60-82-r.retail.telecomitalia.it) |
16:29.00 | *** join/#oe anarsoul (~anarsoul@212.98.175.166) |
16:38.58 | awozniak | How do I set the location of the bitbake logfile? I'm getting "ERROR: Function 'staging_packager' failed (see /dev/null for further information)" |
16:39.21 | kergoth | afaik thats just a bug in old versions of bitbake |
16:39.25 | kergoth | really old versions of bitbake |
16:39.29 | kergoth | shrugs |
16:39.44 | kergoth | what versions are you building? |
16:49.29 | awozniak | kergoth: BitBake Build Tool Core version 1.12.0, bitbake version 1.12.0 |
16:50.07 | kergoth | what yocto/poky/oe-core version? |
16:50.20 | awozniak | kergoth: oe-classic |
16:50.42 | kergoth | there's no way to fix that message short of cherry picking the fixes from a future branch into your bitbake |
16:50.51 | kergoth | and crossing your fingers :) |
16:51.53 | awozniak | kergoth: slightly confused by your response. I want to see the "logfile" that it thinks its writing to "/dev/null" There's no way to set the location of the logfile? |
16:52.07 | kergoth | its not a configurable path |
16:52.09 | kergoth | its just a bug |
16:52.16 | kergoth | it was always intended to write to a real logfile |
16:52.56 | awozniak | so the logfile really exists somewhere, I just need to go find it. |
16:53.25 | kergoth | no |
16:53.27 | kergoth | well, maybe |
16:54.11 | kergoth | https://github.com/openembedded/bitbake/commit/90fc09ee050a24095a488d8ce98c7945bf282f6d |
16:54.36 | kergoth | afaik thats what fixed it |
16:54.46 | kergoth | from some quick searching of the git history with git log —grep=/dev/null |
16:54.53 | awozniak | kergoth: thanks, that looks super useful. |
16:55.41 | kergoth | np |
16:55.59 | bluelightning | also, you may wish to move to OE-Core when convenient ;) |
16:56.13 | kergoth | indeed, thats pretty ancient |
16:57.37 | awozniak | wish I could. This project is in maintenance mode, and there's lots of stuff I'm not allowed to do. |
17:02.33 | kergoth | it does look like that commit will cherry pick without conflicts onto 1.12.0, so hopefully.. |
17:08.20 | *** join/#oe ao2 (~ao2@host244-147-dynamic.2-79-r.retail.telecomitalia.it) |
17:09.48 | bluelightning | awozniak: understood |
17:14.27 | *** join/#oe bluelightning_ (~paul@pdpc/supporter/professional/bluelightning) |
17:31.45 | *** join/#oe thaytan (~thaytan@113.94.233.220.static.exetel.com.au) |
17:31.45 | awozniak | kergoth bluelightning: If I switched from bitbake 1.12 to bitbake 1.22, do you foresee any problems with an oe-classic build? |
17:32.53 | *** join/#oe dvhart (~dvhart@134.134.137.75) |
17:34.26 | *** join/#oe kroon (~kroon@89-253-118-72.customers.ownit.se) |
17:36.02 | *** join/#oe anarsoul (~anarsoul@46.28.101.214) |
17:54.26 | kergoth | awozniak: afaik there are at least some things that were deprecated and then removed along the line |
17:54.31 | kergoth | so there'd almost certainly be stuff to fix |
17:55.19 | awozniak | kergoth: Thank you |
17:56.29 | kergoth | np |
17:58.08 | *** join/#oe kgilmer (~kgilmer@65.209.23.146) |
18:27.49 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
18:30.28 | *** join/#oe nitink (~nitink@134.134.137.75) |
18:34.59 | *** join/#oe nitink1 (nitink@nat/intel/x-bqqbdgjkkceaadbt) |
18:38.13 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
18:41.51 | *** part/#oe challinan (~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net) |
18:42.28 | *** join/#oe ao2 (~ao2@host221-97-dynamic.59-82-r.retail.telecomitalia.it) |
18:55.15 | Crofton | JaMa, have you seen any more ice issues? |
19:02.42 | Crofton | denix, have you used wic? |
19:07.33 | *** join/#oe _chase_ (~a0271661@nat/ti/x-nskcqdguypetzlkx) |
19:10.34 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
19:17.17 | JaMa | Crofton: not today IIRC |
19:17.29 | JaMa | Crofton: wouldn't zeromq better fit in meta-networking? |
19:21.11 | *** join/#oe ao2 (~ao2@host72-149-dynamic.6-87-r.retail.telecomitalia.it) |
19:21.55 | Crofton | I guess I'm thinking it is pretty niche oriented |
19:22.42 | Crofton | and not focused on small networking devices |
19:23.24 | Crofton | does Joe Macdonald hang out on irc? |
19:26.31 | Crofton | It has seemed to me that meta-networking is not a catch all for everything that uses a network :) |
19:27.02 | bluelightning | Crofton: right, it should not be that |
19:27.23 | bluelightning | pretty much everything works over a network in some way these days :) |
19:28.02 | Crofton | lets move everything to meta-networking! |
19:28.25 | Crofton | do you know if wic has been used to make SD cards for things like the beagle stuff? |
19:29.19 | bluelightning | there's nothing particularly special about the beagle SD card layout, so I can't see why it wouldn't work |
19:29.35 | Crofton | I'm dumb, I need examples to work from :) |
19:29.40 | Crofton | and pizza arrived |
19:29.45 | bluelightning | mmm pizza |
19:30.09 | Crofton | btw, are congratulations in order? |
19:31.30 | bluelightning | you could use the galileo SD card wks file from the IoT devkit as an example |
19:31.41 | bluelightning | I guess so :) |
19:32.55 | bluelightning | example: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-devkit/tree/scripts/lib/image/canned-wks/iot-devkit.wks |
19:33.34 | bluelightning | (the comment in the second part is out of sync with the partition definition line) |
19:38.42 | *** join/#oe ao2 (~ao2@host4-137-dynamic.10-87-r.retail.telecomitalia.it) |
19:41.49 | *** join/#oe fcooper (~a0273011@nat/ti/x-hjfkqejyhozwopyf) |
19:42.01 | Crofton | Internet of Toilets? |
19:42.56 | Crofton | and yes, this is a thing: https://twitter.com/IoToilets |
19:45.11 | bluelightning | if you can imagine it, someone on the internet has probably done it :) |
19:46.19 | Crofton | that has variable flush amounts |
19:46.35 | Crofton | I'm thinking on the fixed amount USian ones, you could use this to detect leaks |
19:57.07 | *** join/#oe andre_d (~andred@212.17.57.101) |
20:03.35 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
20:18.17 | Crofton | this wic thing is clear as mud |
20:19.47 | kroon | Is it possible to whitelist env-variables on a per-recipe basis ? |
20:24.52 | *** join/#oe cbrake (~Thunderbi@cable-pool6-cs-200.doycomm.com) |
20:28.27 | dv_ | hello |
20:28.30 | dv_ | PACKAGECONFIG_remove = "${@bb.utils.contains('DISTRO_FEATURES', 'x11', '', 'eglgles', d)}" |
20:28.34 | dv_ | is this correct? |
20:28.37 | dv_ | it isnt working |
20:28.56 | dv_ | I want to remove "eglgles" from the packageconfig if x11 isnt being used |
20:31.25 | *** join/#oe dlan (~dennis@gentoo/developer/dlan) |
20:34.32 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
20:42.34 | staylor | is there a way to query bitbake for which package is pulling in a specific dependency? |
21:01.45 | *** join/#oe eFfeM (~frans@c73189.upc-c.chello.nl) |
21:05.40 | dvhart | staylor, bitbake -g -u depexp $targetimage |
21:05.50 | *** join/#oe ant__ (~andrea@host86-146-dynamic.30-79-r.retail.telecomitalia.it) |
21:05.54 | dvhart | staylor, find the package you are curious about, and see the box labeled RDEPENDS |
21:58.44 | Crofton | it looks like koen has the only solution for sd card generation that works with loop file systems? |
22:00.14 | kergoth | why would you want to use loop file systems if you don't have to? They generally cause a dependency upon running as root, or at least ensuring your user has the necessary access to loopback devices, which imposes a host setup dependnecy |
22:00.42 | Crofton | because I do not know what device the sd card reader is |
22:00.50 | Crofton | and it may not be attached to the build machine |
22:01.22 | kergoth | there are better ways to create a disk image than to use loop devices |
22:01.36 | kergoth | e.g. iirc parted can perform operations against a disk image, as can sfdisk |
22:01.40 | kergoth | see some of the alternative sd card bbclasses |
22:01.54 | Crofton | yeah, the problem is there are so many of them |
22:02.07 | kergoth | agreed |
22:02.17 | kergoth | wic seems like it's best positioned to replace them, but there aren't all that many examples of usage yet |
22:02.24 | Crofton | yep |
22:02.38 | kergoth | though the example bluelightning just linked looks extremely promising |
22:02.58 | Crofton | but I could n't work out wtf was really going on |
22:03.05 | kergoth | it's not that complex, just a language for describing the partitioning scheme |
22:03.14 | Crofton | it was just a piece and can't work out how it was tied into the rest of the problem |
22:03.26 | Crofton | partitions are only one piece of the problem |
22:03.29 | kergoth | bitbake produces a filesystem image, wic turns that into a disk image |
22:03.35 | kergoth | i don't really see a misisng piece there |
22:03.41 | kergoth | shrugs |
22:04.12 | Crofton | maybe I'm missing something |
22:04.24 | Crofton | like he said the docs are seriosly lacking |
22:04.57 | kergoth | it's a standalone tool that takes a disk image and description file to do the partitioning as well as splitting up the filesystem into the multiple partitions (e.g. splitting out what's currently in /boot onto th emsdos /boot partition) |
22:08.33 | kergoth | hmmm |
22:08.53 | kergoth | the —ondisk bit is slightly concerning, i can see what you're worried about there, it seems to want to operate directly, which wouldn't be ideal |
22:09.12 | *** join/#oe stefan_schmidt (~stefan@p200300480923DFA6F2DEF1FFFE6228F7.dip0.t-ipconnect.de) |
22:11.45 | Crofton | yeah |
22:12.47 | Crofton | it seems like there are ways of setting up stuff in fstab to work around the loop root issue |
22:12.52 | kergoth | https://github.com/canatella/bitbake-el/blob/master/bitbake.el#L573-L624 may be of interest |
22:13.15 | Crofton | if somethign writes into random places, I'd like them to be safe |
22:13.17 | kergoth | emacs function which wraps bitbake image + wic create + dd, might serve as an example of usage, if not wks contents |
22:14.12 | Crofton | emacs mode for bitbake |
22:14.15 | Crofton | madness |
22:15.20 | kergoth | https://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html#creating-partitioned-images |
22:16.58 | kergoth | 5.6.7. OpenEmbedded Kickstart (.wks) Reference seems of use, though it could be more fleshed out |
22:17.10 | Crofton | yeah |
22:17.21 | Crofton | I need to lower my head and run into the pile |
22:17.32 | Crofton | reseraching stuff is just frustrating me |
22:17.55 | kergoth | doesn't seem like it'd be too bad to get going with this, i'll have to play with it for my minnow, omap5-evm, or beagle |
22:18.01 | Crofton | wic is a crappy name the google spacce is overloaded |
22:18.15 | Crofton | http://www.fns.usda.gov/wic/women-infants-and-children-wic |
22:18.29 | Crofton | needless to say, lots of web pages about wic |
22:18.32 | ant__ | the explanation for the name is even worse |
22:19.31 | ant__ | beat me, OpenEmbedded Image Creator (oeic) is sort of unheard |
22:19.34 | kergoth | agreed |
22:19.38 | kergoth | i never heard of oeic before |
22:19.42 | kergoth | seems pointless to retain that history |
22:19.43 | Crofton | me niether |
22:20.11 | kergoth | i'm no good at names, i tend to just describe what hte thing does verbatim :) |
22:25.14 | ant__ | this is x86 only stuff ? |
22:25.35 | ant__ | boot type seems to be 'efi' or 'pcbios' (syslinux) |
22:26.09 | kergoth | the bootloader command seems to be, but the partitioning stuff seems generic, afaict |
22:26.24 | kergoth | shrugs |
22:26.56 | dvhart | ant__ those are just the implemented templates |
22:27.08 | dvhart | ant__ others can be added for other layouts, bootloaders, etc. |
22:27.36 | ant__ | I see |
22:29.02 | kergoth | still does need better docs, but whats in the dev manual is a good starting point, it seems |
22:29.29 | dvhart | definitely an area we would all like to see improved |
22:29.42 | Crofton | directdisk seems to be the thing |
22:29.44 | dvhart | deployment is quite challenging with the "can't be root" restriction |
22:29.58 | dvhart | directdisk.bbclass? heh... that's a disaster |
22:30.23 | Crofton | well, we can't use mkefidisk |
22:30.42 | dvhart | mkefidisk fulfills a very specific purpose |
22:30.46 | dvhart | what are you looking to do? |
22:30.50 | kergoth | i'd create a custom wks for your needs, but the existing ones work as examples |
22:31.15 | dvhart | That would be my suggestion as well |
22:31.15 | Crofton | make images I can dd to an sd card |
22:31.34 | dvhart | for which ARCH/bootloader? |
22:31.42 | Crofton | arm u-boot |
22:31.45 | dvhart | right |
22:31.54 | dvhart | So you have two choices really |
22:32.05 | Crofton | fish around the existing sd card classses |
22:32.08 | dvhart | the wks or write your own version of mkefidisk |
22:32.11 | dvhart | I don't recommend the latter |
22:32.32 | dvhart | the problem with anything that is a bbclass is it has to work around the no root restriction |
22:32.39 | Crofton | yep |
22:32.45 | dvhart | which means a lot of error prone code |
22:33.12 | dvhart | by working outside of bitbake, things like wic can use the well tested established tooling to do that |
22:33.28 | dvhart | anyway, that's a major win in my book |
22:33.32 | kergoth | i've been hoping for image creation to move out of bitabke for many years, so i'm very glad to see this |
22:33.33 | dvhart | but I'm lazy ;-) |
22:33.45 | kergoth | now i just want to see rootfs creation from package feeds out too, but not everyone might agree :) |
22:33.57 | dvhart | kergoth, what would you do instead? |
22:34.07 | Crofton | kergoth, your wish list is a mile long :) |
22:34.12 | dvhart | oh, same thing, just not with bitbake? |
22:34.44 | kergoth | yeah, just conceptually different, not functionally, now that we've gained the ability to build images from existing feeds |
22:34.54 | Crofton | things like narcissus made images from feeds for ages :) |
22:35.41 | Crofton | I'm tired of copying bits and pieces onto an sd card |
22:36.56 | kergoth | nods |
22:38.51 | Crofton | ok, I need a break from this |
22:39.09 | Crofton | now to look into openbts state of the disunion |
22:51.49 | Crofton | how do you avoid the --ondisk bit |
22:51.56 | Crofton | or will that take a file name? |
22:52.32 | kergoth | i'm not clear on what exactly that does, given it still ends up emitting a disk image file anyway, not writing to that device, unless it's used by the bootloader setup |
22:52.36 | kergoth | shrugs |
22:52.41 | kergoth | hopefully someone else knows better |
23:00.23 | Crofton | I need to figure out where the wks files go |
23:00.46 | Crofton | it seems like people are copying the wic files into their layer |
23:02.21 | Crofton | this seems like a bad idea |
23:02.47 | kergoth | that does seem unfortunate, it should either be able to accept a full path to the wks, or should be able to search alternate paths via BBPATH |
23:02.54 | Crofton | yep |
23:03.12 | Crofton | also need to grok --ondisk |
23:05.30 | kergoth | on the surface it doesnt' make much sense other than potentially to configure the bootloader, could examine the wic code and find out for sure, i suppose |
23:06.28 | *** join/#oe nitink (nitink@nat/intel/x-ibaokoilsedxepkw) |
23:09.09 | *** join/#oe RushPL (~quassel@dragon.rushbase.net) |
23:11.26 | Crofton | maybe ondisk refers to the partitions on the target device? |
23:12.01 | Crofton | this could be a breakthrough! |
23:12.24 | kergoth | that does seem likely, as it doesnt seem like it should touch host devices anyway |
23:12.31 | kergoth | (one would hope, anyway) |
23:12.47 | Crofton | yeah |
23:13.01 | Crofton | and I think I can give it a path to a wkx file |
23:14.44 | kergoth | ah, nice |
23:37.35 | Crofton | I suppose I report wic bugs via yp bugzilla? |