**** BEGIN LOGGING AT Tue Oct 09 02:59:59 2018 Oct 09 06:59:44 I believe, we must have recipe for almost all widely used applications. Oct 09 06:59:56 If yes then where I can find ? Oct 09 07:05:22 SHW_: http://layers.openembedded.org/layerindex/branch/master/recipes/ Oct 09 07:12:05 good morning Oct 09 07:50:37 LetoThe2nd, Great ! So can we add recipes from different category to create a distro as per out need ? Oct 09 07:52:48 SHW_: well thats the whole point of OE (which you basically just didn't want to see until now because you were so fixated on the "i need to generate a toolchain!" mindset)" Oct 09 07:53:31 SHW_: its about mixing and matching layers to pick exactly what you need in your imag4e Oct 09 07:53:32 LetoThe2nd, You got me Oct 09 07:54:35 LetoThe2nd, But I am concerned about Toolchain because there are some proprietary packages and few non-oe existent packages. which I want to add. Oct 09 07:55:09 Since I am much familiar with toolchain for compiling all needed package. So for my comfort zone, I am after Toolchain Oct 09 07:55:25 SHW_: so create recipes, bundle them in your custom layer, done. Oct 09 07:56:21 LetoThe2nd, It will be new thing to learn then. Accepted. Oct 09 07:59:13 SHW_: the point is that you gain reproductibility. "just a toolchain is my comfort zone" usually implies this workflow: i compile this like taht... and then i compile this other thing like that... and then i need this install script... then that install script... and finally this manual processes her, and there, and voila, see, here's the final image Oct 09 07:59:33 which is 100% job security, and 100% maintenance nightmare. Oct 09 08:01:09 if you got your stuff correctly prepared in recipes and even apply only minimal SCM, thenyou can basically reproduce any version that you shipped, any time. and its not only one build guru who can do it, but anybody who knows the basics of OE. Oct 09 08:01:53 (which maybe doesn't feel equally elite, but is certainly a good engineering practise) Oct 09 08:02:56 Yes. 100% Job security is prime and vital goal here to keep the things in pocket. Oct 09 08:03:12 Else, automation will make me go out of job Oct 09 08:03:37 SHW_: well then better leave OE alone, and grab the first edition of karim yaghmours book. Oct 09 08:03:50 its basically that. Oct 09 08:03:54 ;-) Oct 09 08:04:38 Man Oct 09 08:05:03 in case you didn't notice, there is a semicolon on that smiley Oct 09 08:05:22 Now after seeing OE feature, I can't let it go Oct 09 08:05:48 (Yes. I first laugh at myself and to your sense of humor) Oct 09 08:06:32 Here, I guess devtool will be my friend for **create recipes, bundle them in your custom layer** Oct 09 08:06:58 SHW_: but seriously. OE is big and complex, and can be overwhelming. both in learning curve, and also not every project actually needs the power. depending on what you need, buildroot might certainly an alternative Oct 09 08:07:32 SHW_: there is *extensive* and *excellent* documentation on how to write recipes in the yocto doc set :) Oct 09 08:08:32 LetoThe2nd, I had given first thought to buildroot only but it's first difference with OE is "toolchain creation". Buildroot DO NOT offer any toolchain. Hence I switch to OE. Oct 09 08:09:32 SHW_: oh, buildroot certainly does that too. and like i said: your mindset is fundamentally incompatible with any of those tools if you stick to "give me a toolchain!!11!!one!!" instead of "hey just do the complete build, i don't care how" Oct 09 08:51:39 LetoThe2nd, On a honest note, I do understand what you said. But my need is totally different than normal. Oct 09 08:54:31 SHW_: on a very honest note, about 80% of people think they have super special usecases, and that its only them. in at least 95% of those cases, it just isn't true. if you are actually willing to elaborate (without readymade prejudice) then i'm willing to listen and see. if you continue to stick to "i'm special, i need a toolchain, why don't you just believe me?" well, then... i'm probably not the one to Oct 09 08:54:37 help you. Oct 09 08:55:03 no offense meant, thats just my experience. Oct 09 08:58:00 Got you. Oct 09 09:01:04 When I create distro (out of toolchain), I deploy it at various hardwares. But some hardware need special tuning for performance then I have to either recompile a package or change some settings. Changing configuration or settings is easy but for recompilation purpose, I have to do that on toolchain Oct 09 09:02:09 ok, go ahead. Oct 09 09:02:16 And I can not have different Distro version for different hardwares (Company rules). So I must have generic distro which will work on wide range of hardware without compromising performance. Oct 09 09:04:20 so you need this: (basic image runs everywhere) -> (magic modification depending on hw type) -> (many images for many hw types) Oct 09 09:04:42 and your company rule says that they all have to use the same starting image. Oct 09 09:04:51 or what does "distro" mean? Oct 09 09:05:13 does it mean "everything we ship has to be based off debian X.Y"? Oct 09 09:05:33 (Almost) Yes Oct 09 09:05:42 yes to which? Oct 09 09:06:08 Yes that it should be compatible with debian X.Y Oct 09 09:06:22 well then you're on the totally wrong track with OE Oct 09 09:07:18 maybe take a loot at the infrastructure that linaro uses to crank out various specialized toolchains. Oct 09 09:07:47 That is why I want to be with OE to demonstrate them that sticking with some widely used distro for compatibility issue is not a good idea. Oct 09 09:08:01 Let's have our own recipes. Oct 09 09:08:04 but if you you want to harness OE into a build apparatus for X patched toolchains to feed a deb package builder, then its just ... wrong Oct 09 09:08:49 there's nothing bad with debian, if it fits the need. Oct 09 09:09:57 Well LetoThe2nd , I want to propose the company that building a distro from scratch with the help of OE is a very good idea than compiling everything from scratch. Oct 09 09:10:07 um. Oct 09 09:10:26 OE *DOES* recompile everything from scratch. you just don't do it manually. Oct 09 09:11:04 Yes. Exactly. Manual intervention is not there. We can use company's human resources for other tasks then. Oct 09 09:11:34 (May be we are going to some other direction.) Oct 09 09:12:33 so what i see at the moment is: 1) you have a whatever company rule that just doesn't mesh with OE technology at all. (not "special", but "just something else") and 2) the absolutely standard use case. Oct 09 09:20:52 I didn't get you Oct 09 09:21:42 what you descibed as you "is"-state just is not special, its just something else than what OE does. (the 1) ) Oct 09 09:22:17 and what you descibed as "want to convince"-state is about the standard usecase of OE: create specialized images per hardware. (the 2) ) Oct 09 09:22:20 not special at all. Oct 09 09:23:14 OK Oct 09 09:23:21 So I fall in first 80% Oct 09 09:23:37 no Oct 09 09:24:00 you would fall into the 80% if you manage o convince people that OE is for you Oct 09 09:24:27 right now, you're "just a debian user", be it good or bad, it doesn't matter. Oct 09 09:26:02 OK Oct 09 09:26:34 So back to OE now. Oct 09 09:27:26 I must gather my requirement, download those recipes if available else "create it and bundle it". After all recipes gathered, I must bitbake them to create an image. Oct 09 09:27:37 no Oct 09 09:27:55 (I was sure, I am missing something.) Oct 09 09:28:12 you must download the layers containing the recipes. and add them to your build Oct 09 09:28:39 and you must define an image recipe that suits your needs, e.g. defines what you want to go inside. Oct 09 09:28:54 then you do: bitbake my-funny-image Oct 09 09:29:08 thats it. no manual building of recipes to go in there. Oct 09 09:29:34 very well Oct 09 09:29:35 SHW_: seriously, there is excellent quickstart documentation on all of this. Oct 09 09:31:05 LetoThe2nd, Certainly. I will go through it. Surely. Oct 09 09:32:37 if you happen to be near scotland, on thu, oct 25th in edinburgh is the yocto dev day which offers all of that in a condensed form Oct 09 09:33:39 Oh. Thanks. Oct 09 09:34:27 we're currently in the process of ironing out some issues with registration, but i'm told that the beginner track (which exatly offers the information you miss) has still free seats. Oct 09 09:35:50 Well, I am from Asia. So chances are very slim that I will attend. Oct 09 09:36:03 thats sure ;-) Oct 09 09:37:25 SHW_: here's the whole presentation shbang from one of the previous events: https://wiki.yoctoproject.org/wiki/images/1/1d/Ypdd-2017.02-ELC-Portland.pdf Oct 09 09:37:38 any video tutorial do we have ? Oct 09 09:38:12 no video worth recommending that i'm aware of Oct 09 09:38:48 if anything, the closest should be https://www.youtube.com/watch?v=bJVYxlkHees Oct 09 09:39:22 or generally anthing https://www.youtube.com/channel/UCZC0bMcgbB8v-CViidufLUw/videos Oct 09 09:49:22 Going through PDF. Seems to be very helpful. Oct 09 23:08:30 khem, patch finally sent to the ML Oct 09 23:10:06 there isn't any easy way to split shared/static afais Oct 09 23:42:21 ant_home: thanks I staged it in mut **** ENDING LOGGING AT Wed Oct 10 02:59:59 2018