**** BEGIN LOGGING AT Sat Jun 27 02:59:57 2020 Jun 27 04:52:47 Hi. I'm following an example of how to build a device image with yocto - page 15 here: http://down.myir-tech.com/MYD-Y6ULX-HMI/01-Document/User_Manual/English/MYD-Y6ULX-HMI%20Linux%20Development%20Guide_EN.pdf Jun 27 04:53:58 I've successfully built the image and the SDK, and I've managed to shoehorn libsdl2 in by putting it into core-image-base.bbappend and actually placing the files in "recipes-myir" which is where the custom stuff seems to live Jun 27 04:55:03 But I can't for the life of me get libglesv2 to build - I placed "libgles2"(which is its name) in the same .bbappend file, and bitbake still succeeds, but I have NOTHING on the output. No built libs, not in the SDK. Jun 27 04:55:07 What am I doing wrong? Jun 27 04:56:17 Bitbake fails if I put an unresolvable name in the same .bbappend file, so it reads and validates it Jun 27 06:00:32 Spirit532: that sounds pretty much off... may i reommend to have a good look at episode #2 of https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj Jun 27 06:01:17 Spirit532: which gives a very good rundown on how to do custom images - becasue bbappend'ing core-image-base is certainly weird at least and prone break at worst. Jun 27 06:01:33 I'd like to avoid spending 40 minutes staring at a half-frame-per-second console Jun 27 06:01:53 * Letothe2nd shrugs Jun 27 06:01:55 they already provide a custom image, but said custom image is broken as shit Jun 27 06:02:16 * Letothe2nd would like to avoid explaining it 40 minutes here already having done it on video for all the world to use. Jun 27 06:02:24 have fun, then. Jun 27 06:02:25 let's skip the "right way" part Jun 27 06:02:34 and go straight to the "you shouldn't do this, but..." Jun 27 06:04:45 they made their own meta folder for this board, inside there's several "recipes-" folders, one of which is core, the other one is fsl-*/...../ with "fsl-image-qt5.bbappend", which is the broken one Jun 27 06:06:05 * Letothe2nd skips this altogether, then. its saturday 8am here and family is calling. the video contains all i have to say, if you want something else, i wish you all the best in finding somebody who provides. Jun 27 06:06:09 * Letothe2nd is out again. Jun 27 06:14:33 yeah, that video appears to not explain anything I've already more or less understood Jun 27 06:14:42 what I need to know is why adding something to "IMAGE_INSTALL +=" does not, in fact, install it Jun 27 06:15:14 there's no documentation explaining how to use mesa with yocto, only people answering irrelevant questions on stackoverflow Jun 27 06:16:04 I can build any recipe I want by placing it in the right spot and appending it to "IMAGE_INSTALL +=", except things apparently "provided" by mesa, like EGL, GLESv2, and others Jun 27 06:16:46 it gave me an error when I added libsdl2, I installed the recipe and the error went away, sdl2 building successfully Jun 27 06:17:12 I did't install any mesa/egl/gles2 recipes, but adding any of it(mesa, libgles2, libegl) to the list does not result in errors, and I also don't get anything built Jun 27 07:39:49 Spirit532: if you run "bitbake -e | grep IMAGE_INSTALL"= does it have the values you expect? Jun 27 07:40:16 I've discovered another issue that potentially halts this, I will test in a bit Jun 27 07:41:12 Spirit532: sounds like you're referring to the freescale layer, does this hardware have accelerated GL? If so they layer could be doing strange things with GL/mesa. The freescale is known to do some things a little oddly (I don't remember exactly what) Jun 27 07:41:28 nope, this is the no gpu version for a smaller soc Jun 27 19:03:21 Failure expanding variable TUNE_FEATURES_tune-cortexa9-neon, expression was ${TUNE_FEATURES_tune-cortexa9} neon which triggered exception RecursionError: maximum recursion depth exceeded Jun 27 19:03:21 - why? **** ENDING LOGGING AT Sun Jun 28 02:59:57 2020