**** BEGIN LOGGING AT Thu Feb 14 02:59:57 2019 Feb 14 10:11:22 join #yocto Feb 14 10:13:11 Some packages build with autotools for linux, but use CMake for cross-compiling to other targets (looking at you, protobuf). Specifically I'm trying to build nativesdk-protobuf for mingw32 Feb 14 10:14:10 ... tried conditional inheritance, but that does not seem to work the way I need it to (i.e. at inheritance time, bitbake has not yet decided whether it's building for target or sdk). Feb 14 10:14:50 Any ideas on how to enable cmake build for sdk only? Feb 14 10:15:34 writing a new recipe might be the best solution, as that's not just all sdks but mingw sdks Feb 14 10:16:11 or, fix the autotools build. Feb 14 10:16:17 everything else works fine... Feb 14 10:16:42 good point. ack, will write a dedicated recipe. Thanks! Feb 14 10:18:44 give it a different name, have it PROVIDES the existing name, package into the existing names, then you might be able to set PREFERRED_PROVIDER_protobuf_class-nativesdk_mingw32 = "protobuf-cmake" Feb 14 10:18:59 the other alternative is can protobuf use cmake for building on/for linux Feb 14 10:20:51 From how I understand upstream documentation, cmake is not recommended for linux, so I'll stick to the mingw32 special case. Feb 14 16:22:56 erk. oe has been around for 17 years now? i feel old Feb 14 16:23:17 should we have a party? Feb 14 16:23:24 and what are you considering the birth? Feb 14 16:24:51 the exact date isn't entirely clear, but i know the irc discussions that formed the initial design occurred around the end of jan to the middle of feb, iirc Feb 14 16:25:02 think i have the dates written down somewhere or other Feb 14 16:25:28 We rally need to give a presentation of th ehistory of OE and try explaining how we have survived this long Feb 14 16:27:36 but first we should have that party Feb 14 16:27:42 * JaMa already started with 2 beers Feb 14 16:30:49 Crofton: probably not a bad idea. it might help folks with their conceptual understanding to hear some of the reasons behind its current design and implementation, both from the beginning and the major changes and why they were done Feb 14 16:31:11 i have a doc somewhere where i started such a thing, probably would need updating and fleshing out though Feb 14 16:35:11 yes, the part how poky and then oe-core was created is interesting for many people not only from historical reasons, but because they still don't understand it today Feb 14 16:40:00 the part where the YP sprung fully formed, like a virgin birth :) Feb 14 16:55:47 * khem pours tea into beer mug Feb 14 16:56:25 its fun to watch people reaction when you have geen tea in beer mug and drive your kids to school in morning .. Feb 14 16:56:35 ha Feb 14 16:58:19 I am sure some of them must of thinking of calling child services immediately ;) Feb 14 16:58:50 mind constructs Feb 14 16:59:21 I think oe has cornered itself by ignoring feeds Feb 14 17:00:30 OE is like a F1 car, but every developer drives maybe Toyota Feb 14 17:02:10 feeds are a service by distro engineers Feb 14 17:02:16 but You have a point Feb 14 17:06:39 Crofton: how do you recruit more poeple into user/dev community Feb 14 17:06:54 make it easy to use Feb 14 17:12:06 I like this train of thought Feb 14 17:13:02 so give them something easy to start Feb 14 17:13:28 I had a young kid and he figured out building a package on debian in a day Feb 14 17:13:42 for OE 3 weeks and he still is not sure Feb 14 21:30:14 so I was all set to send out an email about the Recipe Reporting System, but I've just added a "meta-openembedded" maintenance plan covering meta-oe and meta-networking (to start with) and I'll wait for the data to show up in that so people have something to look at Feb 14 21:30:51 you can see what's there for OE-Core though: https://layers.openembedded.org/rrs/ Feb 14 22:11:24 bluelightning, nice Feb 14 22:11:53 meta-oe has notthing lsitsed? Feb 14 22:12:08 yeah the backend processing runs once a day, so it should be there tomorrow Feb 14 22:12:26 ok Feb 14 22:14:07 bluelightning, can I sort the maintainer report by different columns? Feb 14 22:14:26 yeah some of the columns are sortable Feb 14 22:14:36 the chevrons aren't showing up in the right place, that's fixed in master Feb 14 22:14:45 ok Feb 14 22:35:04 hi. im trying to fix some simple errors, and found that this commit solves the problem in five out of six files: http://git.linaro.org/openembedded/meta-linaro.git/commit/?h=dizzy&id=000a7e7e0eee0b8840ddc6a362321a11d6e05909 Feb 14 22:35:27 one file was however not updated, but should have been: http://git.linaro.org/openembedded/meta-linaro.git/tree/meta-linaro/recipes-extra/powerdebug/powerdebug_0.7.3.bb?h=dizzy&id=000a7e7e0eee0b8840ddc6a362321a11d6e05909 Feb 14 22:35:54 im new to oe, so my question is basically, where should i turn to reach the right people that can fix this? Feb 14 22:36:03 is it an OE issue or something i should go to the linaro folks with? Feb 14 22:39:14 I'd start with the Linaro people since it is their layer Feb 14 22:39:42 koen, any advice? Feb 14 22:39:55 I fear they may not be around at the moment :) Feb 14 22:40:10 ok cool :) Feb 14 22:40:23 ill have a go in the linaro channel Feb 14 22:40:25 thanks! Feb 14 22:43:38 oe is very interesting. unfortunately im completely new to it. do you have any recommendations for videos to watch to get as good understanding of it as possible, while not spending hours and ours watching videos? like, is there something that's a nice bootstrap? im mostly interested in how to understand all the layers, recipes, file/dir structures, so i can work with the building of openvario(.org) Feb 14 22:46:56 oh nice, need to show that to a freind Feb 14 22:47:27 http://openvario.org/doku.php?id=projects:series_00:software:overview Feb 14 22:48:50 yeah its great. i have two friends using it in their private gliders. we're currently going to replace two LX7000s with two openvarios in club gliders, more to come. Feb 14 22:49:38 wehn I have a chance, I'll look over what they are doing Feb 14 22:49:59 Crofton: if your friend wants to get it but doesnt want to build it all him/herself, he/she can just buy ready-built hardware from stefly.aero - it's not expensive at all Feb 14 22:50:17 real plug and play :) Feb 14 22:50:42 there's an irc channel for it, #openvario, and one for #xcsoar as well Feb 14 22:50:55 I do not need another hobby Feb 14 22:51:03 hah Feb 14 22:52:30 this might help Feb 14 22:52:31 https://e-ale.org/seminar/building-images-with-yocto-project/ Feb 14 22:54:55 ah, the recording button there. nice. Feb 14 22:55:07 and the talk before it, i presume, to get the basics :) Feb 14 22:55:12 yeah, and I think you can jump back in time for the other talk Behan mentions Feb 14 22:55:20 cheers Crofton, youre very helpful! Feb 14 22:55:28 ssshhhh Feb 14 22:55:36 gonna watch this, looks relevant Feb 14 22:56:36 I ahven't seen it, but Behan is pretty sensible Feb 14 22:56:43 thats good Feb 14 22:57:00 most hits on youtube are very introductory, this one seems like more right into it Feb 14 22:57:04 if that makes any sense, lol Feb 14 22:58:06 Crofton: while i have you on the line here, may i ask about angstrom.. more specifically, the website just has empty articles, and it seems to not be updated at all. in fact most public stuff besides the actual code of angstrom seems to be rather dead. is it a largely inactive project? Feb 14 22:59:37 it is not the most active project, especially from the PR side Feb 14 22:59:42 I suspect the base feeds are OK Feb 14 23:01:17 yet people seem to still use it. what does it bring that other similar projects doesnt? im still a bit unsure about where angstrom fits into e.g. openvario Feb 14 23:04:34 basially it has binary package feeds Feb 14 23:05:41 right Feb 14 23:09:21 bluelightning: awesome, can you add all layers under meta-openembedded there Feb 14 23:09:29 bluelightning: it would help me a loy Feb 14 23:12:11 rawtaz: you are on dizzy which is pretty old and maybe you should use default toolchain i.e. remove meta-linaro from your bblayers.conf Feb 14 23:12:57 hmm, shoudl look close at openvario and mabe see abohelping them update Feb 14 23:13:15 khem: there's reasons the openvario project are still on dizzy, driver stuff. so that part is fine. the problem isnt the using of an old version, they cant upgrade right now, but that this sixth file wasnt correct in the commit i linked to Feb 14 23:13:52 if that file is just corrected in the dizzy branch, then the oepnvario project can update their layers.txt that reference this branch to make it use the new commit, and things should be fine :) Feb 14 23:14:22 rawtaz: ok, then I guess you can send a pull request for meta-linaro/dizzy Feb 14 23:14:54 project seems cool. Do you have plan to upgrade s/w to latest at some point ? Feb 14 23:15:20 to do builds, you need an older build system lnux :) Feb 14 23:15:27 I ahve to use docker for things like that Feb 14 23:16:30 Crofton: yeah I like this page http://openvario.org/doku.php?id=projects:series_00:software:overview Feb 14 23:16:38 khem: im just getting started with the openvario project from a development perspective. it's lacking in documentation and has a few small hurdles for newcomers, so im intending to create a docker build container and brush up the developer manual. but i still dont know my way around OE and that part of the build process. right now im just trying to fix this little URL problem. Feb 14 23:17:01 khem: i asked the linaro peeps, will do that. just gotta figure out how to send that PR, as theyre not on github :> Feb 14 23:17:03 and this http://openvario.org/lib/exe/fetch.php?media=projects:series_00:ov_asw24.jpg Feb 14 23:17:18 rawtaz: yeah they have their gerrit Feb 14 23:17:30 as many people as many systems Feb 14 23:17:42 Crofton: yeah, i tried building it on the latest ubuntu 18.xx, but that didnt work because of incompatibilities between the autocomp and newer perl Feb 14 23:17:56 see Feb 14 23:17:59 https://review.linaro.org/#/q/status:open Feb 14 23:18:15 mmm gerrit Feb 14 23:18:29 khem: as i told Crofton, if you want to get an openvario for your aircraft, you can get a ready built unit kit from stefly.aero - you can install it in a few minutes Feb 14 23:19:20 khem: oh but to answer your question, yeah they are working on upgrading. the problem is: "We have to use kernel-3.4 because of the mail driver for the Allwinnner A20 SoC on the cubiebaord. As we have to use this old kernel, we also have to use the Yocto Dizzy Release as actual releases (like pyro) are not compatible with such an old kernel. So everything depends on the Mail driver for the SoC. An update of the Mail driver is in progess, but not an easy tas Feb 14 23:19:39 so it will be done. but at the same time there's nothing in terms of features that need anything newer than dizzy, so its not urgent Feb 14 23:19:42 but if you git format-patch and prefix subject [meta-linaro][dizzy] and send it to openembedded@lists.linaro.org that will do it Feb 14 23:19:58 khem: awesome, thanks for those pointers :) Feb 14 23:20:15 very helpful and useful Feb 14 23:20:43 rawtaz: 3.4 kernel is usable with latest OE no problem Feb 14 23:20:48 khem: shall i take it you're a glider pilot? Feb 14 23:20:49 you dont have to stick to dizzy Feb 14 23:20:57 I have 3.3 kernel working with OE master Feb 14 23:21:08 but yes its a bit of stretch I agree Feb 14 23:21:19 khem: hmm ok. thats not something i can put into complete understanding now, but ill take it with me for when i understand OE better Feb 14 23:21:33 rawtaz: no I am not but a good friend of mine is Feb 14 23:21:38 ah ok :) Feb 14 23:22:25 rawtaz: kernel is just one package amongst many when you put together an OS using OE build system Feb 14 23:22:35 so its flexible to pick version Feb 14 23:22:52 but mileage varies depending on SOC support Feb 14 23:23:21 right makes sense Feb 14 23:24:23 OE and Yokto isnt just for embedded i take it? you can build a linux distro that you use in a container or in a VM or on a physical server as well? i mean, the next kick-ass linux distro that everyone will want to use, for example. or would that be weird somehow? Feb 14 23:24:42 rawtaz: correct, anything Feb 14 23:25:29 OE provides infrastructure to build a linux based distro Feb 14 23:25:45 there are many OE based distros out there Feb 14 23:25:59 so cool. can you name some of the common ones that i might recognize? Feb 14 23:26:01 mint? Feb 14 23:26:06 nah thats ubuntu based i think Feb 14 23:26:20 no desktop distros though Feb 14 23:26:34 angstrom is most famous one Feb 14 23:26:43 for embedded linux Feb 14 23:27:27 i never heard of angstrom before, to me it's a distro for embedded stuff. i still dont know what its actually useful for more than other distros. Crofton mentioned they have binary package feeds Feb 14 23:27:48 smart watch e.g. https://asteroidos.org/ Feb 14 23:27:55 oh, nice Feb 14 23:29:00 rawtaz: the core is really small. so you can install a 16M image with updater Feb 14 23:29:10 and then install packages you need from binary feeds Feb 14 23:29:29 we can get a base image that small with desktop distros :) Feb 14 23:29:32 thats the difference Feb 14 23:29:42 s/can/cant Feb 14 23:30:35 makes sense Feb 14 23:32:24 and you can easily rebuild portions you need to Feb 14 23:37:59 yeh Feb 14 23:38:15 hmm it seems that the fix to that file is already done, in 1b666f257c23ffb3720464c4f09a198dc1318a94 - its just not in the dizzy branch Feb 14 23:38:37 perhaps i can just mail that list and ask them to pick that commit into the dizzy branch then Feb 14 23:41:55 nah it covers more files Feb 14 23:57:46 khem: mail sent, thanks again for your help :) Feb 14 23:57:54 now for some food.. Feb 15 00:12:42 rawtaz: good deal Feb 15 00:24:16 rawtaz: you might have heard of WebOS, the software that palm->hp->LG used in phones and now TVs. that's OE. **** ENDING LOGGING AT Fri Feb 15 02:59:56 2019