| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 00:25 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 00:26 | |
| *** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC (Remote host closed the connection) | 00:32 | |
| *** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto | 00:35 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds) | 00:49 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 00:49 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 265 seconds) | 00:54 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 00:54 | |
| *** davidinux <davidinux!~davidinux@host-79-54-161-160.retail.telecomitalia.it> has quit IRC (Ping timeout: 252 seconds) | 01:03 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 01:05 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 01:06 | |
| *** davidinux <davidinux!~davidinux@host-82-63-81-174.business.telecomitalia.it> has joined #yocto | 01:09 | |
| *** rabbi[11]58 <rabbi[11]58!~rabbi11]@54-240-198-34.amazon.com> has joined #yocto | 01:09 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 01:16 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 01:17 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds) | 01:24 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 01:25 | |
| *** RobertBerger <RobertBerger!~rber|res@62-46-95-134.adsl.highway.telekom.at> has joined #yocto | 01:32 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 265 seconds) | 01:33 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 01:33 | |
| *** rber|res <rber|res!~rber|res@62-46-95-134.adsl.highway.telekom.at> has quit IRC (Ping timeout: 248 seconds) | 01:34 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds) | 01:49 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 01:49 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 246 seconds) | 01:54 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 01:54 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.) | 02:23 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto | 02:39 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo) | 02:40 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto | 02:42 | |
| khem | fray: if you are in comcast coverage then you can buy comcast mesh APs they do run yocto | 02:43 |
|---|---|---|
| *** jclsn <jclsn!~jclsn@2a04:4540:6511:2900:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 248 seconds) | 02:57 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:6510:f900:2ce:39ff:fecf:efcd> has joined #yocto | 02:58 | |
| *** pbsds <pbsds!~pbsds@84.20.102.91> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 03:05 | |
| *** pbsds <pbsds!~pbsds@84.20.102.91> has joined #yocto | 03:05 | |
| *** amitk <amitk!~amit@103.208.69.149> has joined #yocto | 03:09 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds) | 03:34 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 03:39 | |
| *** odra__ <odra__!~odra@179.110.183.71> has quit IRC (Ping timeout: 265 seconds) | 03:53 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 246 seconds) | 04:39 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 04:39 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 248 seconds) | 04:43 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 04:44 | |
| *** thomasd13 <thomasd13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto | 04:52 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 04:53 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 248 seconds) | 04:58 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 04:58 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.) | 04:59 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 244 seconds) | 05:03 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 05:03 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 265 seconds) | 05:35 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 05:35 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 252 seconds) | 05:39 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 05:40 | |
| *** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Remote host closed the connection) | 05:51 | |
| *** camus <camus!~Instantbi@58.246.136.202> has joined #yocto | 05:51 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 06:12 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 06:13 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Remote host closed the connection) | 06:26 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 06:27 | |
| *** rabbi[11]58 <rabbi[11]58!~rabbi11]@54-240-198-34.amazon.com> has quit IRC (Ping timeout: 252 seconds) | 06:30 | |
| *** rabbi[11] <rabbi[11]!~rabbi11]@54-240-198-34.amazon.com> has quit IRC (Ping timeout: 252 seconds) | 06:30 | |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto | 06:33 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto | 06:35 | |
| *** leonanavi <leonanavi!~Leon@46.55.231.62> has joined #yocto | 06:35 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 06:41 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 06:42 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds) | 06:45 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 06:45 | |
| *** mckoan|away is now known as mckoan | 06:45 | |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4605:ca00:24d7:51ff:fed6:906d> has joined #yocto | 06:57 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 07:02 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:02 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 07:02 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 07:12 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:12 | |
| *** davidinux <davidinux!~davidinux@host-82-63-81-174.business.telecomitalia.it> has quit IRC (Ping timeout: 268 seconds) | 07:12 | |
| *** davidinux <davidinux!~davidinux@92.118.62.197> has joined #yocto | 07:13 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has joined #yocto | 07:14 | |
| *** manuel1985 <manuel1985!~manuel198@185.144.162.58> has joined #yocto | 07:19 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 07:22 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:23 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Remote host closed the connection) | 07:23 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:23 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Remote host closed the connection) | 07:23 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:23 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has quit IRC (Ping timeout: 252 seconds) | 07:25 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:6510:f900:2ce:39ff:fecf:efcd> has quit IRC (Quit: WeeChat 3.0) | 07:32 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:6510:f900:2ce:39ff:fecf:efcd> has joined #yocto | 07:35 | |
| jclsn | JPEW: Getting expansion errors since the last Pyrex update | 07:38 |
| jclsn | It also says the latest Ubuntu version 22.04 is not supported | 07:38 |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has joined #yocto | 07:38 | |
| jclsn | Guess Pyrex is only compatible with the latest Yocto release? | 07:38 |
| jclsn | No issues when building without Pyrex... | 07:41 |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has quit IRC (Ping timeout: 268 seconds) | 07:45 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has joined #yocto | 07:45 | |
| *** ederibaucourt <ederibaucourt!~ederibauc@abordeaux-655-1-154-138.w92-162.abo.wanadoo.fr> has joined #yocto | 07:48 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has quit IRC (Ping timeout: 268 seconds) | 07:50 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has joined #yocto | 07:51 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 08:03 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 08:04 | |
| *** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has quit IRC (Ping timeout: 252 seconds) | 08:21 | |
| *** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has joined #yocto | 08:21 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 08:24 | |
| *** davidinux <davidinux!~davidinux@92.118.62.197> has quit IRC (Ping timeout: 265 seconds) | 08:25 | |
| *** davidinux <davidinux!~davidinux@host-82-63-81-174.business.telecomitalia.it> has joined #yocto | 08:28 | |
| *** davidinux <davidinux!~davidinux@host-82-63-81-174.business.telecomitalia.it> has quit IRC (Ping timeout: 268 seconds) | 08:33 | |
| *** davidinux <davidinux!~davidinux@92.118.62.102> has joined #yocto | 08:34 | |
| *** zkrx <zkrx!~slimshady@2001:1715:9d9e:65f0:d4cc:dbff:fe3c:3b93> has quit IRC (Ping timeout: 268 seconds) | 08:41 | |
| *** davidinux <davidinux!~davidinux@92.118.62.102> has quit IRC (Ping timeout: 260 seconds) | 08:41 | |
| *** davidinux <davidinux!~davidinux@host-82-63-81-174.business.telecomitalia.it> has joined #yocto | 08:43 | |
| *** zkrx <zkrx!~slimshady@adsl-89-217-230-95.adslplus.ch> has joined #yocto | 08:48 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 08:49 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 08:49 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 08:54 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 08:54 | |
| *** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:10d6:cd9b:247:1e52> has quit IRC (Remote host closed the connection) | 08:55 | |
| *** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:1082:df66:e73b:d67> has joined #yocto | 08:56 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has quit IRC (Ping timeout: 268 seconds) | 09:05 | |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has joined #yocto | 09:18 | |
| *** greenwhale <greenwhale!~greenwhal@145.94.144.99> has joined #yocto | 09:24 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128148.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 09:25 | |
| *** odra <odra!~odra@2804:431:c7e1:3111:f4b:e24d:e065:16cb> has joined #yocto | 09:29 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds) | 09:29 | |
| *** tomzy_0 <tomzy_0!~tomzy_0@84-10-27-202.static.chello.pl> has joined #yocto | 09:31 | |
| *** fuzzybear396515 <fuzzybear396515!~fuzzybear@2001:420:c0c0:1004::4a6> has joined #yocto | 09:33 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 09:34 | |
| fuzzybear396515 | Is do_configure[foo] how I would define the configure task if foo is in DISTRO_FEATURES ? | 09:37 |
| ptsneves | fuzzybear396515: no, what lead to that assumption? | 09:37 |
| fuzzybear396515 | ptsneves I was pretty sure it was false, that's why I asked. But, I saw examples using notation like do_configure[foo] and thought that maybe that might work with DISTRO_FEATURES in addition to other flags. | 09:38 |
| rburton | fuzzybear396515: as said yesterday, DISTRO_FEATURES are not overrides (or var flags). It's just a variable. If you want to do condititional things on it, then d.getVar("DISTRO_FEATURES") and poke at it (which is what bb.utils.contains does, it's getVar().strip().contains()) | 09:39 |
| rburton | [foo] is a flag for the do_configure variable | 09:39 |
| fuzzybear396515 | rburton and do_X[foo] means that foo is an override for the X task? | 09:39 |
| rburton | no | 09:39 |
| rburton | overrides are :like_this | 09:39 |
| rburton | do_configure[cleandirs] = "${B}" sets the cleandirs flag on do_configure to ${B}. this tells bitbake to ensure ${B} is an empty directory when it runs. | 09:40 |
| ptsneves | no. the S[X] is just notation for flag setting on a variable. By default you can do it but nothing happens. | 09:40 |
| rburton | (this is in the bitbake manual) | 09:40 |
| rburton | https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-metadata.html#variable-flag-syntax | 09:41 |
| ptsneves | fuzzybear396515: can it be you are confusing things with PACKAGECONFIG? | 09:41 |
| rburton | compare with https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-metadata.html#conditional-syntax-overrides | 09:41 |
| fuzzybear396515 | ptsneves I'm pretty confused generally. So, it's not some misunderstanding of PACKAGECONFIG that's causing my confusion. | 09:43 |
| fuzzybear396515 | I was just searching for the example recipes in the Yocto manual where they did do_configure[noexec] () { } | 09:43 |
| fuzzybear396515 | I couldn't find it. | 09:43 |
| fuzzybear396515 | I was having a hard time finding the OVERRIDES documentation. Thanks rburton | 09:44 |
| ptsneves | then as @rburton mentioned a glance at the bitbake manual is a good idea. It is not so long and is a great way to start grasping things. That is actually how i did it a long time ago. Jumping to the general yocto docs before the bitbake ones felt extremely confusing. :) | 09:45 |
| rburton | fuzzybear396515: top hit for 'yocto overrides documentation' so not sure what you googled :). its all on docs.yoctoproject.org. | 09:45 |
| fuzzybear396515 | rburton I was searching within the Yocto Project manual. | 09:46 |
| *** greenwhale <greenwhale!~greenwhal@145.94.144.99> has quit IRC (Quit: Client closed) | 09:46 | |
| fuzzybear396515 | I think my questions are Bitbake-specific, not Yocto-specific. | 09:46 |
| fuzzybear396515 | I think I'd benefit from reading the BitBake Manual. | 09:46 |
| rburton | yes | 09:47 |
| *** zpfvo <zpfvo!~fvo@i59F5CF9F.versanet.de> has quit IRC (Ping timeout: 246 seconds) | 09:48 | |
| fuzzybear396515 | I'm confused about these Bitbake-style Python functions. Our do_configure and do_install look more like POSIX shell functions than Python functions. | 10:02 |
| fuzzybear396515 | We have case statements and install/mv/cp calls. | 10:02 |
| fuzzybear396515 | If the tasks are truly Python functions then these should fail to parse. | 10:03 |
| ptsneves | search for tasks. Both are supported | 10:03 |
| fuzzybear396515 | ptsneves I see, now, thanks: https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-metadata.html#tasks . | 10:04 |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 10:04 | |
| fuzzybear396515 | So basically the parsing phase will try to detect which style you've used. | 10:04 |
| fuzzybear396515 | It defaults to Python, say, and if that parse fails then it assumes sh. | 10:05 |
| ptsneves | fuzzybear396515: no, it does not detect. Come on this is litereally in the introduction of the bitbake manual: https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-intro.html#introduction | 10:07 |
| qschulz | fuzzybear396515: python tasks are prefixed with "python", e.g. python do_compile() {} | 10:12 |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds) | 10:14 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 10:14 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Ping timeout: 246 seconds) | 10:14 | |
| fuzzybear396515 | ptsneves with all due respect, I appreciate you linking out to the introduction, but I just read the entire introduction after your prompting and didn't see any description of how BitBake executes tasks or how recipe authors annotate tasks to indicate the language/runtime. | 10:17 |
| fuzzybear396515 | qschulz okay, that makes sense. I saw that I could promote my own python functions to tasks. Somehow I didn't connect that all python functions need to be prefixed with the "python" keyword. I thought for tasks it was implicitly-determined. | 10:18 |
| rburton | https://docs.yoctoproject.org/bitbake/2.0/bitbake-user-manual/bitbake-user-manual-metadata.html#functions | 10:18 |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 244 seconds) | 10:18 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 10:19 | |
| fuzzybear396515 | I read that > Only BitBake-style Python functions can be tasks. | 10:19 |
| fuzzybear396515 | and thought that meant that tasks can only be written in BitBake-style Python functions. | 10:19 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 10:20 | |
| fuzzybear396515 | I understand now that they can also be shell functions. | 10:20 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 10:20 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 10:25 | |
| ptsneves | fuzzybear396515: No problem. I meant this as the original statement "I'm confused about these Bitbake-style Python functions. Our do_configure and do_install look more like POSIX shell functions than Python functions. [...] If the tasks are truly Python functions then these should fail to parse." | 10:26 |
| ptsneves | In the introduction it mentions both are supported. From the link: | 10:26 |
| ptsneves | "Fundamentally, BitBake is a generic task execution engine that allows shell and Python tasks to be run " | 10:26 |
| ptsneves | That means leads to the next thing i answered, tasks, and they can be sheell and python | 10:26 |
| *** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Quit: camus) | 10:27 | |
| *** camus <camus!~Instantbi@58.246.136.202> has joined #yocto | 10:27 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 10:29 | |
| fuzzybear396515 | ptsneves Oh, yeah. My confusion about the support for shell functions arose from this in the BitBake Manual: Only BitBake-style Python functions can be tasks. | 10:29 |
| fuzzybear396515 | The context was in comparing normal Python functions to BitBake-style Python functions, though, so out of context it sounds like only Python code can be written in tasks. | 10:29 |
| fuzzybear396515 | The support for both (and the need to annotate with python if using a BitBake-style Python function) is clear, now. | 10:30 |
| ptsneves | fuzzybear396515: nice catch! | 10:32 |
| ptsneves | @qschulz: is this not incorrect? I found the statement in https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html | 10:32 |
| fuzzybear396515 | ptsneves Now it's clear that it's not saying that "tasks may only be written with BitBake-style Python functions" but, instead, that "tasks may be written in either POSIX-compliant shell functions or in Python style, but if in Python style then they must be BitBake-style Python functions (where certain imports are automatic, where the def keyword | 10:34 |
| fuzzybear396515 | is not used, etc.)". | 10:34 |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds) | 10:44 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 10:44 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 252 seconds) | 10:48 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 10:49 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 10:53 | |
| qschulz | ptsneves: sorry, not following, what is correct/incorrect? | 11:00 |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Ping timeout: 252 seconds) | 11:12 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 11:15 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 11:15 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Ping timeout: 268 seconds) | 11:19 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving) | 11:29 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 11:34 | |
| *** fuzzybear396515 <fuzzybear396515!~fuzzybear@2001:420:c0c0:1004::4a6> has quit IRC (Quit: Ping timeout (120 seconds)) | 11:44 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 11:45 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 11:45 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Ping timeout: 268 seconds) | 11:56 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 11:56 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 12:06 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 12:06 | |
| JPEW | jclsn: set a different version in pyrex.ini | 12:07 |
| *** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has joined #yocto | 12:09 | |
| *** manuel1985 <manuel1985!~manuel198@185.144.162.58> has quit IRC (Ping timeout: 244 seconds) | 12:24 | |
| *** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-146.mrsn.at> has joined #yocto | 12:31 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Ping timeout: 240 seconds) | 12:33 | |
| *** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-146.mrsn.at> has quit IRC (Ping timeout: 250 seconds) | 12:36 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto | 12:36 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Quit: quit) | 12:42 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 12:45 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 12:46 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds) | 12:49 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 12:49 | |
| *** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 12:50 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto | 12:51 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Client Quit) | 12:53 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 264 seconds) | 12:54 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 12:54 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto | 12:54 | |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto | 12:56 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto | 12:56 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Client Quit) | 12:58 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto | 12:59 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Client Quit) | 12:59 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Ping timeout: 268 seconds) | 13:06 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto | 13:07 | |
| *** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has quit IRC (Ping timeout: 265 seconds) | 13:08 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto | 13:11 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Ping timeout: 246 seconds) | 13:15 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 13:18 | |
| JPEW | jclsn: More specifically, we always default pyrex.ini to be the latest image, so if you're starting fresh it's going to use that. You can specify a different image in your pyrex.ini file | 13:20 |
| ptsneves | qschulz: In the manual there is the statement " Only BitBake-style Python functions can be tasks." | 13:32 |
| qschulz | ptsneves: the section is called "BitBake-Style Python Functions Versus Python Functions" | 13:40 |
| qschulz | and the list starts with: Following are some important differences between BitBake-style Python functions and regular Python functions | 13:41 |
| qschulz | so I think it's ok that we do not mention shell tasks in there? | 13:41 |
| ptsneves | hmm i see. Sorry for the noise | 13:41 |
| qschulz | np :) | 13:43 |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in) | 13:45 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 13:46 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 13:46 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto | 13:50 | |
| *** tlwoerner_ <tlwoerner_!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has quit IRC (Quit: Leaving) | 13:58 | |
| *** tlwoerner <tlwoerner!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has joined #yocto | 13:59 | |
| *** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto | 14:00 | |
| *** kscherer <kscherer!~kscherer@dsl-173-206-238-19.tor.primus.ca> has joined #yocto | 14:04 | |
| qschulz | mmmm, I'm starting to work on a kirkstone brnch for our bsp layer (never too late..) and our custom kernel recipe does not fetch | 14:12 |
| qschulz | complains about "Recipe uses a floating tag/branch without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev()" but I use a fixed SRCREV and a fixed branch too | 14:13 |
| qschulz | ooof, found the issue | 14:15 |
| *** thomasd13 <thomasd13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 248 seconds) | 14:15 | |
| qschulz | for some reason my copy-paste didn't copy the whole checksum | 14:15 |
| qschulz | I tested again with 39 digits instead of 40 and indeed, it triggers the error | 14:16 |
| qschulz | I think we can do a better job at guiding the user for this specific case | 14:19 |
| qschulz | mm I see JaMa have a patch in master for this one error | 14:21 |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection) | 14:22 | |
| ptsneves | qschulz: can you share the patch? | 14:23 |
| qschulz | ptsneves: https://git.openembedded.org/bitbake/commit/?id=04dc17bef9b762cef9eecdf91c9f37738d8ae44d | 14:24 |
| qschulz | still not obvious what the error could be though | 14:25 |
| qschulz | sakoman: hi, I was wondering if it was possible to backport https://git.openembedded.org/bitbake/commit/?id=04dc17bef9b762cef9eecdf91c9f37738d8ae44d to kirkstone? | 14:31 |
| sakoman | qschulz: sure, I can do that | 14:32 |
| ptsneves | qschulz: it still wont catch you are missing 1 character due to it considering a tag/branch name correct? | 14:32 |
| qschulz | ptsneves: yeah :/ | 14:34 |
| ptsneves | :/ how would we catch that? Maybe the issue is that branches tags or hashes get all put in SRCREV. | 14:36 |
| ptsneves | maybe add in the message that it can also be broken hash? | 14:36 |
| qschulz | it's not that easy as the code that is printing this error is handling bazaar, mercurial and git fetchers | 14:50 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 14:51 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 14:52 | |
| qschulz | nvm, can't read | 14:52 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Remote host closed the connection) | 14:52 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 14:52 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Ping timeout: 248 seconds) | 14:56 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 14:59 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto | 15:11 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Ping timeout: 250 seconds) | 15:15 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 15:16 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Quit: quit) | 15:19 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Ping timeout: 252 seconds) | 15:20 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto | 15:20 | |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has joined #yocto | 15:20 | |
| *** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has joined #yocto | 15:22 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Ping timeout: 246 seconds) | 15:28 | |
| *** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto | 15:30 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 15:31 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 15:32 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 15:32 | |
| ptsneves | qschulz: Recipe uses a floating tag/branch '%s' for repo '%s' without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE). If the SRCREV was meant to be a hash check if the length is correct as well as check for typos. | 15:33 |
| ptsneves | would this be better? If so i will send the patch | 15:33 |
| qschulz | ptsneves: I think there are two cases for this message to appear | 15:35 |
| qschulz | 1. invalid hash (not hexadecimal character or not 40-character long) | 15:35 |
| qschulz | 2. AUTOREV but with missing SRCPV in PV? | 15:36 |
| qschulz | I think we should print the correct message depending on the case | 15:36 |
| JaMa | not only AUTOREV any non-fixed SRCREV needs SRCPV in PV IIRC | 15:36 |
| *** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has quit IRC (Ping timeout: 252 seconds) | 15:37 | |
| qschulz | JaMa: so we could have a branch name in SRCREV provided PV contains SRCPV? | 15:38 |
| *** leonanavi <leonanavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving) | 15:40 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving) | 15:40 | |
| ptsneves | qschulz: a tag name for sure | 15:43 |
| ptsneves | and the ambiguity remains. | 15:43 |
| qschulz | But.. why? | 15:43 |
| qschulz | we have a ;branch= and a ;tag= parameter for the fetcher | 15:44 |
| qschulz | so just force SRCREV to be a git commit hash or AUTOREV and nothing else | 15:44 |
| qschulz | no? what am I missing? | 15:44 |
| ptsneves | ah so i am in the wrong. You are right that we have these URL params | 15:44 |
| qschulz | I am not saying it's not what we currently support though :) | 15:45 |
| ptsneves | qschulz: and AUTOINC? | 15:45 |
| qschulz | ptsneves: AUTOREV is AUTOINC | 15:45 |
| qschulz | internally | 15:45 |
| ptsneves | you are right get_autorev sets it | 15:49 |
| ptsneves | qschulz: is the SRCREV 40 character SHA-1 in every fetcher, or just in git? | 15:58 |
| qschulz | ptsneves: the 40-character check is only for git | 15:59 |
| qschulz | ptsneves: https://git.openembedded.org/bitbake/tree/lib/bb/fetch2/git.py#n256 | 16:00 |
| qschulz | so we could check if SRCREV is set to AUTOINC, then we know it's SRCPV that is missing from PV that triggers this issue (still to be confirmed though, haven't tested) | 16:01 |
| qschulz | and we can advise the user to add SRCPV to PV | 16:01 |
| ptsneves | that code check is already very late perhaps. As there ud.revisions may indeed have used the branch/tag parameters. | 16:02 |
| qschulz | and if it's not, we know it's an invalid sha1 | 16:02 |
| qschulz | don't know, I have no experience in Bitbake code base :/ | 16:03 |
| *** Guest8423 <Guest8423!~Guest84@wsip-184-185-74-99.dc.dc.cox.net> has joined #yocto | 16:03 | |
| ptsneves | seems a bit more complicated :( | 16:03 |
| qschulz | ptsneves: I think it makes sense to only allow sha1 or AUTOREV in SRCREV | 16:06 |
| qschulz | this forces users wanting to use a branch or tag to use AUTOREV in SRCREV | 16:06 |
| *** mckoan is now known as mckoan|away | 16:06 | |
| qschulz | which very much shows that it's not guaranteed to be stable | 16:06 |
| ptsneves | the thing is that the SRCREV is not even read in git.py. In the git.py the hash is retrieved from ud.revisions[name] which, may be set by SRCREV. I do not know yet | 16:08 |
| *** zpfvo <zpfvo!~fvo@i59F5CED1.versanet.de> has quit IRC (Quit: Leaving.) | 16:11 | |
| Guest8423 | Hi, I'm new to Yocto and I'm getting an error while trying to build fribidi-native. Is the the right channel to ask for help? | 16:18 |
| rburton | sure | 16:18 |
| rburton | ask away | 16:18 |
| Guest8423 | Thank you. I am using a BSP based on Yocto Thud and I added meta-ros layer that I think it pulled in fribidi native and it is causing this error: | Traceback (most recent call last): | 16:21 |
| Guest8423 | | File "/*******/tmp-glibc/work/x86_64-linux/fribidi-native/1.0.5-r0/recipe-sysroot-native/usr/bin/meson", line 30, in <module> | 16:22 |
| Guest8423 | | from mesonbuild import mesonmain | 16:22 |
| Guest8423 | | ModuleNotFoundError: No module named 'mesonbuild' | 16:22 |
| Guest8423 | | ERROR: meson failed | 16:22 |
| rburton | Thud has been EOL since 2019, you know that right? | 16:22 |
| Guest8423 | Yes, I am using the BSP package from a chip vendor and this is my only option. | 16:23 |
| rburton | i'm assuming you're using the thud branch of meta-ros, and not master | 16:23 |
| rburton | your option is to shout at your vendor that thud has been EOL since 2019 and they expect you to pay for this? | 16:23 |
| rburton | whilst people don't get angry at them, they'll continue to release obsolete BSPs | 16:24 |
| Guest8423 | correct, I'm using thud branch of meta-ros. | 16:24 |
| rburton | weird. i'd suggest removing your tmp and trying again. it has the meson wrapper but not the actual package. | 16:25 |
| rburton | from meta-ros: "building with thud is no longer supported as of Milestone 15 (2020-12-23)." Just saying :) | 16:26 |
| rburton | can you name and shame the vendor? its possible that there's an unofficial but modern bsp you can use | 16:26 |
| Guest8423 | I have tried a clean build a few times and I keep getting the same error. | 16:27 |
| rburton | try "bitbake meson-native -C unpack" to force it to rebuild meson | 16:28 |
| Guest8423 | do you think even thud branch of meta-ros os not supporting thud anymore? | 16:28 |
| rburton | the thud branch of meta-ros isnt supported. it supports thud, its just that they don't support it | 16:28 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 16:31 | |
| Guest8423 | I tried "bitbake meson-native -C unpack" which succeeded and then "bitbake fribidi-native". Still getting the same error. | 16:33 |
| rburton | very strange | 16:33 |
| rburton | an interesting test would be a clean poky with no vendor bsp and no meta-ros, just bitbake fribidi-native | 16:33 |
| Guest8423 | Sure, I'll try it. Thanks. | 16:34 |
| sakoman | qschulz: Taking the commit you suggested for kirkstone results in oe-selftest errors: https://errors.yoctoproject.org/Errors/Details/672179/ | 16:45 |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 260 seconds) | 16:45 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128148.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 246 seconds) | 16:46 | |
| sakoman | qschulz: So for now I can't take that. If you'd like to research the error and submit a fix I'd be happy to reconsider :-) | 16:46 |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat) | 16:52 | |
| Guest8423 | rburton: clean poky with no vendor bsp and with vendor bsp is working. That error shows up when I add meta-ros layers. Any suggestion on how to start debugging? | 17:09 |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 268 seconds) | 17:18 | |
| denix | JPEW: so, I'm hitting this gdk-pixbuf breakage with ubuntu 22.04 container, apparently it is known - https://github.com/moby/moby/issues/43595 | 17:25 |
| denix | apparently, the "fix" is to disable building gdk-pixbuf tests... | 17:26 |
| JPEW | denix: Hmm | 17:26 |
| JPEW | denix: Passing `--security-opt seccomp=unconfined` to docker might fix it? | 17:31 |
| JPEW | You can put that in `run.args` in pyrex.ini | 17:32 |
| denix | yeah, disabling seccomp is mentioned there, but not sure about the consequences... I can try | 17:33 |
| *** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:1082:df66:e73b:d67> has quit IRC (Ping timeout: 250 seconds) | 17:33 | |
| JPEW | Might be able to pass a custom seccomp policy | 17:34 |
| *** _wmills <_wmills!~wmills@pool-96-241-133-205.washdc.fios.verizon.net> has quit IRC (Ping timeout: 265 seconds) | 17:43 | |
| denix | seccomp=unconfined seems to help - it's building w/o breakage, will see if there are any other issues | 17:53 |
| rburton | JaMa: any thoughts on Guest8423 above? | 17:55 |
| *** odra <odra!~odra@2804:431:c7e1:3111:f4b:e24d:e065:16cb> has quit IRC (Ping timeout: 260 seconds) | 17:59 | |
| JaMa | Guest8423: whole meta-ros isn't activelly maintained anymore and I don't think it was doing anything with fribidi nor meson, I guess it's just thud being incompatible with your host OS as it's failing in -native | 18:00 |
| JaMa | Guest8423: try some old unsupported host OS in docker container (like ubuntu 18.04) if you want to build old unsupported junk bsp | 18:01 |
| *** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Ping timeout: 252 seconds) | 18:04 | |
| Guest8423 | JaMa: Thank you. I am currently using Ubuntu 18.04. I used "bitbake -c devshell fribidi-native" to get some insight. When meta-ros is NOT enabled, python3 version in devshell terminal is "3.5.6" and when I enable meta-ros, python version switches to "3.7.5". Not sure if this information is useful. | 18:38 |
| *** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Read error: Connection reset by peer) | 18:56 | |
| *** florian_kc <florian_kc!~florian@dynamic-078-048-117-097.78.48.pool.telefonica.de> has joined #yocto | 18:57 | |
| *** mario-goulart <mario-goulart!~user@chicken/developer/mario-goulart> has joined #yocto | 18:59 | |
| JaMa | Guest8423: yes newer python3 was backported from warrior to thud in https://github.com/ros/meta-ros/tree/thud/meta-ros-backports-warrior/recipes-devtools/python | 19:00 |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4605:ca00:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection) | 19:15 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 244 seconds) | 19:19 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 19:19 | |
| *** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto | 19:22 | |
| *** Guest3857 <Guest3857!~Guest38@17-14-39.cgnat.fonira.net> has joined #yocto | 19:26 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 250 seconds) | 19:29 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 19:29 | |
| *** florian_kc is now known as florian | 19:34 | |
| Guest3857 | Hi! I am currently setting up yocto for my embedded system. I have a question related to devtool: I want to split my meta-layers into "meta-bsp" and "meta-project-specific". The bsp layer should only include pure HW support whereas the project-specific layer should only contain project specific stuff. Still it might be needed to have kernel patches | 19:38 |
| Guest3857 | in both layers some are only for HW support the others might be project specific. How can I handle that with devtool properly? When I do: "devtool update-recipe -a meta-project-specific" all my patches which are already included in meta-bsp are copied to meta-project-specific. Is it possible to only generate the patches which are not already | 19:38 |
| Guest3857 | included in meta-bsp? | 19:38 |
| *** mrnuke <mrnuke!~mrnuke@c-98-197-58-203.hsd1.tx.comcast.net> has quit IRC (Read error: Connection reset by peer) | 19:42 | |
| *** mrnuke <mrnuke!~mrnuke@c-98-197-58-203.hsd1.tx.comcast.net> has joined #yocto | 19:44 | |
| *** rabbi[11] <rabbi[11]!~rabbi11]@54-240-198-36.amazon.com> has joined #yocto | 19:49 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 19:50 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 20:01 | |
| *** violet <violet!~vi@user/violet> has quit IRC (Quit: leaving) | 20:04 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Ping timeout: 252 seconds) | 20:17 | |
| *** Guest3857 <Guest3857!~Guest38@17-14-39.cgnat.fonira.net> has quit IRC (Ping timeout: 244 seconds) | 20:18 | |
| *** Guest3827 <Guest3827!~Guest38@17-14-39.cgnat.fonira.net> has joined #yocto | 20:25 | |
| mcfrisk | linux-yocto from master is very slow to fetch/download. Would switching from git to https protocol help? | 20:26 |
| *** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto | 20:31 | |
| *** Minvera2 <Minvera2!~Minvera@user/Minvera> has joined #yocto | 20:37 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Ping timeout: 246 seconds) | 20:38 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds) | 20:54 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto | 20:54 | |
| *** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 250 seconds) | 20:58 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 20:59 | |
| *** Minvera2 <Minvera2!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection) | 21:01 | |
| *** Guest3827 <Guest3827!~Guest38@17-14-39.cgnat.fonira.net> has quit IRC (Quit: Connection closed) | 21:09 | |
| *** PhoenixMage <PhoenixMage!~phoenix@206.83.114.26> has quit IRC (Ping timeout: 250 seconds) | 21:10 | |
| *** PhoenixMage <PhoenixMage!~phoenix@206.83.112.22> has joined #yocto | 21:12 | |
| *** PhoenixMage <PhoenixMage!~phoenix@206.83.112.22> has quit IRC (Ping timeout: 244 seconds) | 21:40 | |
| *** PhoenixMage <PhoenixMage!~phoenix@206.83.113.14> has joined #yocto | 21:42 | |
| *** wmills <wmills!~wmills@pool-96-241-133-205.washdc.fios.verizon.net> has joined #yocto | 22:03 | |
| *** Guest8423 <Guest8423!~Guest84@wsip-184-185-74-99.dc.dc.cox.net> has quit IRC (Ping timeout: 252 seconds) | 22:10 | |
| *** Bardon <Bardon!~Bardon@user/Bardon> has quit IRC (Ping timeout: 268 seconds) | 22:32 | |
| *** Bardon <Bardon!~Bardon@user/Bardon> has joined #yocto | 22:52 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 22:58 | |
| *** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has quit IRC (Ping timeout: 264 seconds) | 23:17 | |
| *** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has joined #yocto | 23:19 | |
| *** florian <florian!~florian@dynamic-078-048-117-097.78.48.pool.telefonica.de> has quit IRC (Ping timeout: 246 seconds) | 23:39 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!