**** BEGIN LOGGING AT Thu May 18 03:00:03 2017 May 18 03:10:10 https://xkcd.com/1838/ May 18 06:12:34 good morning everyone May 18 06:12:47 ... at least it is morning in RO May 18 07:46:27 @CostinC Morning from FR ;) May 18 08:17:05 I'm trying to understand "meta-example" layer after working through this: recipes-example/bbexample/bbexample-lt_1.0.bb. What's with the 3 different bb files provided ? Which one gets processed ? May 18 08:19:57 hey, i'm trying to build mariadb from the meta-oe layer, however i either get this error( https://pastebin.com/ZJBxy4X2) when building 5.5.55, or it simply won't build/install anything with version 5.5.52. Does anyone know anything about this? May 18 08:22:12 Smitty_: never seen that layer before, but they're all different recipes May 18 08:23:22 they only differ in how the src_uri is formed afaict May 18 08:23:29 seems like a fairly useless example tbh May 18 08:26:31 I'm following this: https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles#Build_an_example_project_on_the_host_for_testing_.28optional.29 May 18 08:28:05 http://www.yoctoproject.org/docs/2.3/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe is the latest and greatest guide to writing a recipe, including using devtool to automate most of it May 18 08:29:33 And I don't understand what's going to happen when I add bbexample into local.conf because there's three recipies, and from the looks of it, they all get added : /home/smitty/poky/meta-example/conf/layer.conf has this: BBFILES += "${LAYERDIR}/recipes-*/*/*.bb May 18 08:30:08 in that layer there are three recipes with different names May 18 08:30:15 right May 18 08:30:33 just like oe-core has a hundred recipes with different names May 18 08:30:59 but the layer conf looks like it's adding all the recipies to BBFILES May 18 08:31:36 yes May 18 08:31:44 why would it not add all recipes? May 18 08:31:59 WHich means they're all going to get build, but they're all the same May 18 08:32:01 no it doesn't May 18 08:32:09 it means they're available to build May 18 08:32:12 Smitty_ : Adding all the recipes to BBFILES doesn't mean that every recipe they will be built May 18 08:32:28 So, So, which one gets built ? May 18 08:32:32 the one you ask for May 18 08:32:34 Smitty_ : The one you specify May 18 08:32:42 bitbake bbexample, or bitbake bbexample-rt, or whatever May 18 08:32:47 (or via dependencies in another target) May 18 08:32:49 Smitty_ : RDEPENDS, IMAGE_INSTALL ... May 18 08:33:03 Smitty_ : DEPENDS also May 18 08:33:09 And - back to the original isse - when nothing depends upon it yet ? May 18 08:33:15 then it won't get built May 18 08:33:26 the same way if you bitbake core-image-minimal, it doesn't built webkitgtk May 18 08:33:32 which *is* part of oe-core and *is* in BBFILES May 18 08:34:01 Smitty_ : When you need to bake, you need to specify which ingredient you would like from the fridge. But in the fridge there is all the ingrenients and some that you don't need. May 18 08:35:40 So, adding the layer to poky/conf/bblayers.conf.sample isn't enough to get a layer built ? May 18 08:36:35 a layer just provides recipes which you *can* build May 18 08:36:49 eg adding meta-python to bblayers.conf doesn't put every python module into core-image-minimal May 18 08:37:10 otherwise, your initramfs would have webkit in May 18 08:37:34 Smitty_ : Does putting food in fridge is enough to have something cooked ? May 18 08:37:59 hi for yocto 2.1 , i meed python gobject can not work well ? how can i solve this ? import gobject or from gi import gobject both can not work well for me May 18 08:39:33 rheagar: did you install python-pygobject? May 18 08:40:11 i test connman , connman-test rdepend python-pygobject May 18 08:40:12 rheagar: also the syntax is from gi import GObject, capitisation is important May 18 08:40:27 erm, from gi.repository import GObject, even May 18 08:40:37 import gobject won't work as that's pre-GI May 18 08:41:00 GObject does not work for me too May 18 08:41:10 does import gi work? May 18 08:41:18 yes May 18 08:41:45 import gi gi.__file__ works well for me May 18 08:42:26 what does pre-GI means? May 18 08:43:31 before gobject-introspection May 18 08:44:16 do you know how to fix this ? May 18 08:45:18 i can only see python-pyobject upgrade from 2.28 to 3.18. May 18 08:45:20 root@8x96auto:/usr/lib64/python2.7/site-packages# ls _dbus_bindings.la gi _dbus_bindings.so pygobject-3.18.2-py2.7-linux-x86_64.egg-info _dbus_glib_bindings.la pygtkcompat _dbus_glib_bindings.so setuptools-19.4-py2.7.egg dbus setuptools.pth May 18 08:45:51 then my site-packages does not have python-pyobject. May 18 08:46:03 hello May 18 08:46:14 There's clearly a disconnect between my idea of a build system, and what yocto is providing. I go to a restaurant, I look at the menu and see Beef Wellington on the menu, I order it. I don't order Filet steak coated with pate wrapped in pastry, baked and covered in mushroom sauce. May 18 08:46:15 rheagar: check that you have a GObject-2.0.typelib under /usr/ib somewhere May 18 08:46:17 i am trying to install ipk on yocto and getting this error any idea please? https://pastebin.com/8w05zeu4 May 18 08:46:27 Smitty_: layers are like pages in the menu May 18 08:48:13 Smitty_ : So you would like a window system based which you just tell in simple words what you want and everything do it without you but in case of bugs you can't do anything if I understand =) May 18 08:48:45 rburton : do you mean /usr/lib64/libgobject-2.0.so ? May 18 08:49:10 update-rc.d: /etc/init.d/gpsd exists during rc.d purge (use -f to force) whats this error? May 18 08:49:20 Smitty_ : In yocto, you're not somebody which go to restaurant in my mind, but more somebody that will cook. And Yocto project is kind of set of tools that make it easy to bake. As "small appliance". May 18 08:50:04 rburton use find / -name "*bject-2.0.*", i can only find libgobject-2.0.so. does my board miss some package ? May 18 08:50:42 Excuseme, I've been developing software for 30+ years. I have worked with raw makefiles, autotools, and CMake. I cannot understand how Yocto is expecting me to do the simplest thing, add a library to an already fully configured OS image build target. In every other build system I have already mentioned, this would be a 10 second task. May 18 08:51:10 Smitty_ : And it is a 10 second task. May 18 08:51:16 apparently not May 18 08:51:41 Smitty_ : If you can't see in which way yocto is powerfull, is maybe that you don't need it. May 18 08:52:43 So, what's the secret, how do I get my layer included in the OS image (in fact only the SDK build target), in tens seconds May 18 08:53:09 @PinkSnake: Bonjour :) May 18 08:53:18 Smitty_ : You put simply in your image recipe "IMAGE_INSTALL=" and the things you would like May 18 08:53:42 Smitty_ : You put simply in the recipe which dependency is critical RDEPENDS, so that you are sure that in the target you have what you need May 18 08:54:21 And the "image recipe" is which file ? May 18 08:54:28 ChrysD: Is there a way to include a full layer actually? Besides adding each recipe in IMAGE_INSTALL seperatly? May 18 08:55:20 Smitty_ : Most of time, it's in the " OS layer " May 18 08:55:43 Smitty_: For example: meta/recipes-core/core-image-base.bb May 18 08:55:59 Smitty_ : and most of time in "recipes-images" when the layer is made by third party May 18 08:56:24 rheagar: sounds like you're missing the gobject-introspection files. did you build this yourself or was it provided by a vendor? May 18 08:56:50 smartin: write recipe for library, IMAGE_INSTALL_append = " my recipe name" May 18 08:56:51 Smitty_ : But you know, for developpment, you can but in your conf/local.conf IMAGE_INSTALL_append May 18 08:56:53 damnit May 18 08:57:00 Smitty_: write recipe for library, IMAGE_INSTALL_append = " my recipe name" May 18 08:57:20 put* May 18 08:57:37 rj_: no. if a layer has a use-case for that it should provide a packagegroup for all recipes. May 18 08:57:51 rburton : i build it my self. May 18 08:57:52 rj_: struggling to come up with a use-case where you'd want *everything* in a layer May 18 08:58:04 rburton: Ah ofcourse, forgot about packagegroups May 18 08:58:06 rheagar: sounds like your distro is missing the gobject-introspection DISTRO_FEATURE May 18 08:58:31 meta/recipes-core/core-image-base.bb file does not exist May 18 08:58:36 rj_ : Have you been honestly interested in a recipebook by ALL the recipes ? May 18 08:59:06 ChrysD: well i'm making my own layer atm, and i need all the recipes installed May 18 08:59:18 rj_ : Yeah but not a layer that you download May 18 08:59:26 rburton : i disable DISTRO_FEATURES_BACKFILL_remove = "gobject-introspection-data" ,because of gstreamer issue. May 18 08:59:35 ChrysD: Nono, just my own layer May 18 08:59:46 rheagar: that would be why you have no gobject introspection data then May 18 09:00:03 rj_ : Usually when i do a my custom layer, I do one recipe, and then i add in the image, and I test, and then I do another recipe, i add, it test... May 18 09:00:20 rj_ : I think yocto doesn't provide mecanism which it let you doing undesired things May 18 09:00:27 ChrysD: I'm currently doing exactly that May 18 09:00:37 rj_ : By the fact that you need to specify what you want to install, you are aware of what you are doing May 18 09:00:52 rj_ : I'm to newbie in yocto project, but I guess it's the philosophy. May 18 09:01:28 ChrysD: but i was just wondering if there was a simple way to install a full layer since it looks cleaner compared to adding all those recipes one by one in the image recipe May 18 09:01:55 rj_ : what about doing a package which include everything in RDEPENDS and in your image you just install that package? May 18 09:01:55 EXACLTY ? May 18 09:02:13 ChrysD: i'm a newbie to yocot aswell :p, started maybe 3 months ago May 18 09:02:17 Yocto* May 18 09:02:32 rj_ : A kind of package, RDEPENDS_${What_i_need} = everything you need May 18 09:02:37 rburton : thanks for your help, i will try it now. May 18 09:02:40 rj_ : And in your image recipe, you put that package May 18 09:02:47 ChrysD: Thats a pretty good idea actually ^^ May 18 09:03:10 rj_ : But it's also the role of packagegroup May 18 09:03:26 ChrysD: Yea, i'll look into both ways when all packages are working correctly May 18 09:03:27 rj_ : so it's dirty May 18 09:03:54 ChrysD: For now it's far from done sadly May 18 09:04:36 rj_ : I also have only 1-2 months of yocto May 18 09:04:39 hello all, anyone familiar with gstreamer? May 18 09:04:45 pagios : A little yes May 18 09:05:08 rheagar: tell us the problem with gst and we can try and help solve that, or you can just disable gi in just the gst recipe May 18 09:05:33 rheagar: GI_DATA_ENABLED="0" in a bbappend will disable it May 18 09:05:52 Whew, mariadb finally compiled May 18 09:06:04 ChrysD, i am trying to add a missing plugin to my yocto, for that i did go to the recipe gstreamer1.0-plugins-bad.incand added to the EXTRA_OECONF += --enable-rtmp, then i did a bitbake install gst-plugins-bad, checking /tmp/ folder i dont see any generated ipk May 18 09:06:24 pagios : what's the plugin that you need? May 18 09:06:30 ChrysD, rtmp May 18 09:06:35 it is in the bad May 18 09:06:44 pagios: check that there isn't a PACAKGECONFIG already for it which is overriding your enable May 18 09:07:05 rburton, you mean a packageconfig with disable rtmp? May 18 09:07:22 yes May 18 09:07:30 in 2.3 there is, and its off by default May 18 09:07:51 56 PACKAGECONFIG[rtmp] = "--enable-rtmp,--disable-rtmp,rtmpdump" May 18 09:08:03 i see this line May 18 09:08:32 pagios: and see the assignment to PACKAGECONFIG above which doesn't include rtmp. if you've never used packageconfig before then read http://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#var-PACKAGECONFIG May 18 09:08:42 rburton, i also read in the .inc file: 66 # these plugins have no corresponding library in OE-core or meta-openembedded: RTMP May 18 09:09:14 i thought rtmpdump was in meta-oe May 18 09:09:21 turn it on and see if it fails :) May 18 09:09:33 --enable-rtmpdump ? May 18 09:10:01 no, read the docs i pointed you at May 18 09:19:29 i added rtmp to PACKAGECONFIG ??= " rtmp .. May 18 09:22:07 rburton, after reading the doc you pointed me to, i understand that rtmp needs to be added as ^ , i did and then executed bitbake gst-plugins-bad but it is not picking up the changes. i also checked that pkgconfig is not disabling rtmp in any other recipe May 18 09:24:16 pagios: gstreamer1.0-plugins-bad? May 18 09:24:30 yes May 18 09:26:06 rbunton : after enable the gobject-xx-data line, rebake python-pygobject , i can't see the different of the image dir . May 18 09:27:34 rheagar: the new file will be in glib-2.0 May 18 09:27:39 rheagar: just rebuild the image May 18 09:27:52 ok May 18 09:33:03 Error Nothing PROVIDES 'rtmpdump' May 18 09:34:07 pagios: http://layers.openembedded.org/layerindex/recipe/28609/ <— its in meta-multimedia May 18 09:34:17 (this would be why its disabled by default) May 18 09:36:29 rburton, /sources/poky/meta/recipes-multimedia$ ls May 18 09:36:29 alsa flac gstreamer lame liba52 libav libid3tag libmad libogg libomxil libpng libsamplerate libsndfile libtheora libtiff libvorbis mpeg2dec pulseaudio sbc speex tremor x264 May 18 09:37:17 pagios: *meta-multimedia* in meta-oe May 18 09:40:39 rburton, /sources/meta-openembedded/meta-oe/recipes-multimedia$ ls : alsa esound id3lib libass libdvdread libmodplug libsdl-image live555 minidlna opus-tools sound-themes wavpack webp xsp audiofile faad2 jack libcdio libmms libopus libsdl-mixer mikmod mplayer pulseaudio v4l2apps webm xpext May 18 09:42:50 pagios: http://cgit.openembedded.org/meta-openembedded/tree/meta-multimedia/recipes-multimedia/rtmpdump/rtmpdump_2.4.bb?h=master i guess you have an older branch where it didn't exist? May 18 09:42:55 copy/paste should work May 18 09:43:01 saw it :) May 18 09:43:24 rburton, it is in /sources/meta-openembedded/meta-multimedia/recipes-multimedia$ May 18 09:44:17 so i do now bitbake rtmdump right May 18 09:44:31 no, it will automatically build when you build gstreamer May 18 09:45:03 rburton, i tried previousl bitbake gstreamer but it didn not build it May 18 09:45:55 pagios: it you got the nothing provides error then bitbake couldn't find a rtmpdump recipe May 18 09:47:02 ok i was able to spot the rtmpdump in that directory , how can i make it visible to bitbake? May 18 09:51:47 rburton, is it ok to copy the rtmpdump recipe to /poky/meta/recipes-multimedia ? May 18 09:51:51 and then bitbake it? May 18 09:52:17 coz my bitbake seems to be working on the poky directory only May 18 10:03:11 Does anyone know why mariadb misses lots of stuff when installed with the standard yocto recipe from the meta-oe layer? May 18 10:03:54 It can't find the mysql.sock file, it can't find the command "find_mysql_client" May 18 10:08:19 rburton, https://pastebin.com/ut9iRBU5 i tried copying that rtmpdump to my poki and did bitbake rtmpdump it worked, did bitbake gst-plugin-bad generatd ipk but trying to instal it iget that error May 18 10:44:23 Hello, I'm getting a warning for Proprietary licence as not being collected, but I see that there is a Proprietary file in poky/... May 18 10:59:07 bitbake-layers show-recipes rtmpdump does not return anything, how cani install rtmpdump? May 18 10:59:55 pagios: it exists in meta-multimedia http://layers.openembedded.org/layerindex/recipe/28609/ May 18 11:12:41 I'm currently tyring to create an image with both libGL.so and libGLESv2.so but it seems I only get mesa to build libGLESv2. Is there any option in the yocto ecosystem that allows building both? (BTW, I'm only using EGL no X11) May 18 11:17:41 Volki : What did you try for now? May 18 11:19:07 ChrysD: I added dependencies for my recipe to virtual/libgl and have opengl in my DISTRO_FEATURES May 18 11:22:03 ChrysD: I also have an bbappend for Mesa with: EXTRA_OECONF += "--with-vulkan-drivers=intel --with-dri-drivers=i965,i915 --without-gallium-drivers" and as mentioned no x11 distro feature May 18 11:25:13 What is the minimum Python version that bitbake master works with? Python 3.x, but which x? May 18 11:26:24 Found it - lib/bb/__init__.py checks for >= 3.4. May 18 11:27:41 Volki : Let me check a second May 18 11:30:20 Volki : On a recipe I have PROVIDES and RPROVIDES like RPRODVIDE_${PN} = "lib egl libgles1 libgles2 ..." May 18 11:31:00 Volki : I don't know if it can helps May 18 11:31:46 Volki : I have also REQUIRED_DISTRO_FEATURES = "opengl" May 18 11:32:13 Volki : PROVIDES += " virtual/libgles2 virtual/legl ...." May 18 11:33:47 Volki: libGL.so is X11 explicitly May 18 11:33:53 you can't build libGL without X11 May 18 11:43:25 that's a pitty, as I use OpenGL without X11 but currently still linking to libGLESv2 (I use enable-shared-glapi). Now I have a library that uses glGetTexImage and complains about unresolved external symbol. That's why I tried adding libGL to the image as well. I'm quite sure, Mesa provides the function even without X11 May 18 11:46:51 say i want to install a specific package and it is not in /sources/poky/meta/recipes-multimedia , it is in a different directory, meta-io for example, is it a simple matter of copying that directory to /sources/poky/meta/recipes-multimedia and using bitbake to use it ? May 18 11:47:42 pagios : I'm not sure of what you want. May 18 11:47:44 pagios: no, set BBLAYERS to include the other layer May 18 11:47:50 in bblayers.conf May 18 11:48:26 unless you have a very strong reason to want just a single recipe and the layer is so broken that you can't even add it to your build May 18 11:48:30 rburton, coz it worked thats why i am asking May 18 11:48:42 define "it" May 18 11:48:48 i just copy pasted the directory May 18 11:48:48 coping the files will work, but its the wrong way May 18 11:48:52 rtmpdump May 18 11:48:55 ok May 18 11:49:05 the entire point is you add meta-multimedia to your bblayers and then you have access to everything in meta-multimedia May 18 11:49:20 and you can update meta-multimedia in the future instead of being stuck with this one specific release May 18 11:52:13 What exactly is the meaning of BUILDDIR? I know that it gets set in the environment by oe-init-build-env. But I can also cd into other build directories and builds there work fine (i.e. TOPDIR is the current directory, not the BUILDDIR from the environment). May 18 11:54:05 hi my sdk genarating a compiler error on /usr/include/c++/5/memory that void* to uintptr_t loses precision May 18 12:20:26 btw i cant find vo-aacenc-dbg on yocto recipes, any idea if it is supported? May 18 12:21:38 my new toy: yundoo y8 (a rk3399 tv-box). i have a few questions and hope for some answers and advice. the hardware is more or less equal to the firefly rk3399, can i use the firefly .dts for the kernel configuration? when i build the distribution with rockchips yocto, do i use the android recovery to flash the linux image from sd card or via usb adb? May 18 12:27:28 rburton: you will appreciate this commit message http://git.savannah.gnu.org/cgit/autogen.git/commit/?id=5cbe233387d7f7b36752736338d1cd4f71287daa May 18 12:30:23 woo May 18 12:40:07 Still here, still don't get it. I have a pre-made layer from here: https://github.com/DynamicDevices/bbexample but now idea how to include it into the core-image-minimal build May 18 12:42:20 Smitty_: thats not a layer, this is a layer https://github.com/DynamicDevices/meta-example :) May 18 12:43:41 Smitty_: also appending your desired package to CORE_IMAGE_EXTRA_INSTALL will include it in core-image-minimal, CORE_IMAGE_EXTRA_INSTALL += "bbexample" May 18 12:56:33 Soory, wrong link : https://github.com/DynamicDevices/meta-example May 18 12:56:43 That's a layer May 18 12:57:39 So, I expect to have to change 1 line in 1 config file *somewhere* in order to have that layer build when I build core-image-minimal May 18 12:57:48 but, not in the build directory May 18 12:57:59 while we get some more activity on the channel: my new toy, yundoo y8, is very similar hardware setting like the firefly rk3399, can i derive the settings from the firefly? and when it comes to the kernel, is it save to go with the firefly dts ? May 18 12:59:19 Smitty_: conf/bblayers.conf May 18 12:59:28 will add the layer May 18 12:59:40 then change your image recipe (or extend it in local.conf) to add the recipes you want May 18 13:00:51 I added the layer, why doesn't that layers recipes just build ? May 18 13:01:00 Smitty_ : What's the purpose of building a Layer that you didn't make yourself ? May 18 13:01:11 because it's an example May 18 13:01:12 Smitty_ : You should add only the packages do you need. May 18 13:01:22 Smitty_: we went through this in the morning. becayse if adding a layer caused everything to build your initramfs would have webkit in. May 18 13:01:23 so that I can understand the process May 18 13:01:31 images contain what you tell them to contain May 18 13:02:01 The layer I added only contains a single recipe. It's not an optional recipe - it should build May 18 13:02:03 Smitty_ : the Layer is "basicaly" and "only" a recipebook that containts lot of things in it. May 18 13:02:29 Smitty_ : Yes but even if it contain only ONE RECIPE it's not a recipe, it's still a layer. May 18 13:03:12 Images are composed of layers. layers are composed of recipes, right ? May 18 13:03:27 images are composed of packages May 18 13:03:31 packages are built from recipes May 18 13:03:34 recipes are grouped in layers May 18 13:04:16 exactly May 18 13:04:24 adding a layer means you have more recipes that *can* be built. May 18 13:04:36 bitbake myimage will look up all the packages that are in it, and then build the recipes it requires May 18 13:04:47 I can see that there is some kind of subtle difference in what you said compared to me - but that doesn't clarify anything May 18 13:05:02 A layer, is quite like a microcontroller... There is 3x UART, 2x SPI, 4x PWM etc etc... You won't use all of them, or maybe yes. So you have to declare what you will use. May 18 13:05:25 Smitty_ : Image =/= Layers May 18 13:05:37 ? May 18 13:05:39 ah, we come closer to device trees now May 18 13:05:48 ;-) May 18 13:05:48 Smitty_: real example: meta-python contains 213 recipes for python modules. adding it to bblayers doesn't add all 213 packages to all images. May 18 13:05:50 what does =/= layers May 18 13:06:07 Why not ? May 18 13:06:11 Smitty_ : Images is not a set of layers. rburton have explained it well May 18 13:06:20 What determines which packages get built then ? May 18 13:06:25 Smitty_: the image May 18 13:06:29 Smitty_ : the image May 18 13:06:32 IMAGE_INSTALL = "list of packages to install" May 18 13:06:46 Smitty_ : RDEPENDS_${PN} also May 18 13:06:49 where is the set of packages that makes up image defined ? May 18 13:06:59 IMAGE_INSTALL = "list of packages to install" May 18 13:07:27 if you know how make works, with it's rule based dependencies -- bitbake is similar. A recipe has a set of dependencies, each of those has a set of dependencies and so on.. May 18 13:07:34 Smitty_ : you won't have a list of all packages installed sometimes in a image recipe. But you can add a package which depends of lot of packages. May 18 13:07:39 in an image reciope, the IMAGE_INSTALL variable is effectively those dependencies.. May 18 13:08:03 Smitty_ : If you deploy a Qt App, you would like to put in RDEPENDS what the Qt apps depend on, so you get sure that your Qt App will have everything needed. May 18 13:08:11 so by specifying a small set of -required- (as in, my image MUST have this) -- the dependencies will be used to both build, and install the items into the image May 18 13:08:13 where do I find IMAGE_INSTALL variable May 18 13:08:21 Smitty_ : In the image recipe May 18 13:08:26 Smitty_ : In the layer that provides it May 18 13:08:35 Smitty_ : Sometimes you can check in "recipes-images" May 18 13:08:43 Smitty_: oe-core's sample images inherit core-image so they don't use it directly but it indirectly gets set in the classes May 18 13:08:49 you can also view the expanded version using 'bitbake -e " May 18 13:08:54 then searching for IMAGE_INSTALL May 18 13:10:30 Smitty_ : Image = Result of mix of packages. Layer = Recipebook. Recipe = How to do things, like a package, describe an image, describe even a machine... etc May 18 13:10:37 So, what is core-image-minimal/conf/bblayers.conf for isn't that the image recipe for core-image-minimal ? May 18 13:10:50 what? May 18 13:11:11 that is the layer's configuration file.. a layer is not a recipe May 18 13:11:27 so, wehre is the recipe for core-image-minimal ? May 18 13:11:55 http://layers.openembedded.org -> select recipes -> type 'core-image-minimal' May 18 13:12:15 Smitty_: $ find meta -name core-image-minimal.bb May 18 13:12:15 meta/recipes-core/images/core-image-minimal.bb May 18 13:12:17 search -> select core-image-minimal May 18 13:12:24 look for 'recipe file' May 18 13:12:28 recipes-core/images/core-image-minimal.bb May 18 13:12:41 located in: openembedded-core May 18 13:12:48 quick way to search and find recipes May 18 13:12:59 any idea how to install libfaac library? May 18 13:13:23 pagios: as fray just says, layers.openembedded.org. http://layers.openembedded.org/layerindex/recipe/20522/ May 18 13:14:56 Why would core-image-minimal recipe be in a different layer ? (meta) May 18 13:15:04 Smitty_: meta/ is oe-core May 18 13:15:21 The openembedded-core git repositroy contains a single layer called 'meta' May 18 13:15:43 (the poky - Yocto Project git repositroy contains multiple layers, one of which is meta) May 18 13:16:04 which I certainly don't expect to have to modify - naively - since it seems like a *core* component which I build upon. May 18 13:16:14 you should -never- modify it May 18 13:16:28 so then why would I edit one of its config files ? May 18 13:16:42 you can change the value of that variable within your project's local.conf or create your OWN layer and use .bbappend (usually the preferred approach) May 18 13:16:47 you wouldn't.. May 18 13:16:52 you asked where it was defined, we're telling you May 18 13:17:15 Smitty_ : You can even do your own image layer which inherit from one other image recipe i think. May 18 13:17:20 Smitty_: every image in oe-core is an example and it's expected that you make your own May 18 13:17:26 yes May 18 13:18:09 core-image-minimal is a layer - right ? May 18 13:18:15 no May 18 13:18:18 Smitty_ : It's an image May 18 13:18:26 core-image-minimal is a recipe, of the type 'image' May 18 13:18:28 Smitty_ : and the .bb the recipe of the image May 18 13:18:36 any file that ends in '.bb' is a recipe May 18 13:18:50 any file that ends in .bbappend is a modification to another .bb May 18 13:19:09 Because the philosophy it's to not change what is what done by the provider, but you append your own modification. May 18 13:19:19 So that you have your own layer of modification May 18 13:19:39 thanks May 18 13:19:42 This is precisely what I am trying to accomplish May 18 13:20:04 create a new layer.. create a recipe .bbappend make your changes/settings in there May 18 13:20:47 You create your own layer, if you would like the .bb in for example recipes-core/linux/ you will have in your layer the same " path " like recipes-cores/linux... your .bbappend will be named as the recipe name you would like to change, and you can overide, or append, or remove variables by the orignal recipe. May 18 13:21:08 of the original recipe* May 18 13:21:23 God my english is so bad that I should stop explaining. I will put more confusion than initially ahahah May 18 13:21:44 I want to add a single library to an existing Image (core-image-minimal). So, I create a layer for my library. Now I want to add my layer to core-image-minimal, so that when core-image-minimal gets built, my library gets built. I add my layer to core-image-minimal/conf/bblayers.conf May 18 13:22:10 what is that path though May 18 13:22:13 ?????? May 18 13:22:19 did you call your build directory core-image-minimal? May 18 13:22:20 @Smitty_ witch lib ? May 18 13:22:22 layers are collections of things.. you can not add a 'layer' to a recipe.. May 18 13:22:27 it should be added in build/conf/bblayers.conf May 18 13:22:28 you are likely just confusing terminology May 18 13:23:01 no, my layer is parallel to meta, meta-poky, meta-yocto-bsp. My layer is meta-example May 18 13:23:06 Ok May 18 13:23:10 where is your buuild directory ? May 18 13:23:21 ok.. then inside of there you will have a conf/bblayers.conf that explains 'what' meta-example is, when its been included.. May 18 13:23:33 for example i have build directory parallel to source directory. And in source directory i have all my meta's May 18 13:23:37 in your project (build directory) you add your layer (base path) to the conf/layers.conf file, so the contents of the layer will be loaded.. May 18 13:23:39 I presume my build directory will be the same as whatever core-image-minimal's build directory will be May 18 13:23:53 Have you ever source oe-init-... ? May 18 13:23:59 you then put, inside of your layer, one or more recipe (.bb) or bbappend to cause the system behavior to change May 18 13:24:10 Smitty_: 'I presume my build directory will be the same as whatever core-image-minimal's build directory will be' makes no sense May 18 13:24:51 Smitty_: oe-init-build-env will create a build/ directory, or you can give it a directory. in that directory you can build any number of recipes. i routintely build about 5 images and SDKs at once from my build directory. May 18 13:24:51 I added my layer to core-image-minimal, why would my layer be built in a seperate directory ? May 18 13:25:00 you can't add a layer to core-image-minimal! May 18 13:25:10 why not ? May 18 13:25:11 that's like saying you fed your cat to a bus May 18 13:25:13 Because a layer isn't an image May 18 13:25:22 you add a layer to a build directory May 18 13:25:25 core-image-minimal is an image May 18 13:25:28 a layer is collection of 'things' May 18 13:25:29 not a layer May 18 13:25:34 it is not a recipe, image, etc May 18 13:25:43 add a layer to build tree by editing conf/bblayers.conf in the build tree May 18 13:25:44 it may contain a recipe / image.. scripts, configuration files, etc May 18 13:26:25 @Smitty you should read the doc i think ... https://www.yoctoproject.org/sites/default/files/ypdd-oct2015-intro-lab.pdf May 18 13:26:48 The build directory, is the one that's tell you what you would like to do, what layers will be parsed, the final image to deploy, even the "temporary" works etc etc May 18 13:27:21 fray, rburton i am getting an error when installignthe ipk: * satisfy_dependencies_for: Cannot satisfy the following dependencies for faac: * libfaac0 (>= 1.28) May 18 13:30:09 pagios that sounds like the recipe has an error where an incorrect (or missing?) runtime dependency is specified May 18 13:30:21 could even be something like the soname of the library is incorrect (in some way) May 18 13:30:25 Build Directory => Your kitchen Workspace. Layers => Recipebook. Packages=> Ingredient. Recipes => Recipes. So you go to your kitchen workspace, you would like to do a recipe in your recipebook and the recipe explain how to have the ingredients. May 18 13:31:16 not sure packages->ingredients May 18 13:31:26 packages -> cakes May 18 13:31:30 rbuton : Yeah May 18 13:31:35 rburton : yeah, maybe May 18 13:31:48 images -> shelf in your cake shop May 18 13:31:50 rburton : But the image is's the result of a mix of ingredient May 18 13:31:52 this is the best metaphor May 18 13:32:11 rburton : I would liek to add SSH + Qt libs + etc etc etc to have the final meal May 18 13:32:28 Does the directory core-image-minimal contain the highest level meta data required to instruct the build environment to build an image ? May 18 13:32:37 But what is that directory? May 18 13:33:17 it's a directory which contains files describing the required layers for a image May 18 13:33:28 Smitty_: there is no core-image-minimal directory May 18 13:33:28 Noot in my case May 18 13:33:42 For me when you download for the first time yocto May 18 13:33:51 you shuold have a bunch of layers May 18 13:33:55 named "meta-" May 18 13:33:57 + poky May 18 13:34:08 When you source for the first time in poky/oe-init..... May 18 13:34:20 it will create the build directory where you are. May 18 13:34:27 hmm bitbake all the cakes May 18 13:34:35 for exemple if you are in /home/user/workspace/ May 18 13:34:45 and you do source /poky/oe-init etc May 18 13:34:56 it willd do a build directory in where you have done the command May 18 13:35:07 so /home/user/workspace/build May 18 13:35:27 You can even specify if you like the path as it ask you May 18 13:35:34 if you like another * May 18 13:35:55 Yep, I'm aware of that May 18 13:36:11 You can also name your build directory as you want when you source May 18 13:36:15 so where is this core-image-minimal directory you keep on referring to? May 18 13:36:27 So you should only have a build directory + the layers directories May 18 13:36:54 core-image-minimal is parallel to met, meta-poky, etc.. May 18 13:37:07 What i do, is => workspace/project1/ and in project1 i have my build directory + sources directory. In sources directory i have all my meta. May 18 13:37:17 Core-image-minimal doesn't exist May 18 13:37:34 You have maybe create your build directory which you named core-image-minimal May 18 13:37:44 yeah presumably that's what happened May 18 13:37:46 what does contain that directory? May 18 13:37:58 you did oe-init-build-env core-image-minimal May 18 13:38:07 instead of oe-init-build-env, then bitbake core-image-minimal May 18 13:38:28 OK, yet again, starting over. This whole process of doing the trivial has taken so long, I've forgotten what I've done, and what I haven't May 18 13:38:58 Smitty_: i'm curious what bits of the quick start were confusing, as we clearly need to fix it May 18 13:39:05 ther eis a Yocto Project 'quick start guide' have you attempted to follow it? May 18 13:39:20 as rburton said, if it's confusing we want to fix it May 18 13:40:19 Initialize the Build Environment: Run the oe-init-build-env environment setup script to define the OpenEmbedded build environment on your build host. $ source oe-init-build-env May 18 13:40:29 in the Quick Startup Guide May 18 13:41:40 hm it should say . instead of source May 18 13:42:03 rburton : 2.1 doc May 18 13:42:07 hm May 18 13:42:12 * rburton fixes May 18 13:42:25 ya, source is a 'bash-ism'.. and may not work for everyone.. May 18 13:42:42 Smitty_ : I think you get into yocto with presumption that make you very far from the yocto philosophy in the process May 18 13:42:52 though i guess most shells that a human use support source May 18 13:43:00 Smitty_ : That's why you get confused and some of the things are not logical for you May 18 13:43:04 CONFUSING< The quick start itself is not confusing, just misleading. As I stated, many times, the requirement to take a "basic working os image" like poky, and add a single library (or any executable) which resides in it's own layer (because that's what layers are for, really) and pass that enrtire source tree to another develoepr and say, look, here's the project to build the core os, plus my library on top. Just source oe-init.bl May 18 13:43:09 ...core-image-minimal May 18 13:43:15 ya, trying to remember, we ran into one recently that didn't work.. but I'm forgetting which.. May 18 13:43:47 Smitty_: so follow quick start to generate core-image-minimal, then follow development manual to create a layer and write a recipe and add a recipe to an image May 18 13:43:53 i can provide links to chapters if you'd like May 18 13:44:08 fray, sorry but i ddint get what you mean, still new May 18 13:44:57 pagios sorry too many conversations (here and elsewhere), hich part? May 18 13:45:00 Smitty_ : In 1 or 2 days you shuold be able to have an image with a custom layer + a recipe which describe your library if you follow whell the documentation at the first time. But I understand that could be difficult in a completely starting point to know how to start. May 18 13:45:16 Smitty_ : That's why the Quick Starting Guide is there, and after it links to other manual May 18 13:45:37 Smitty_ : at the end of the guide, you have the link to all the other guides May 18 13:45:55 I have followed, repeatedly, the quickstart guide. It has me modifying files in the build directory - which I have repeatedly stated is dumb !!! May 18 13:46:18 what do I get the message "WARNING: Host distribution "ubuntu-14.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution." May 18 13:46:35 When the host machine is ubuntu-14.04 May 18 13:46:44 or is that its 14.04 lts May 18 13:46:58 The build directory is where generated files go, so that the source directory stays clean May 18 13:47:12 @Smitty o.0 really ? It has me modifying files in the build directory ?? May 18 13:47:19 sure May 18 13:47:22 black_13, with the latest oe-core/YP, we've run into problems w/ 14.04. The newer 16.04 worked for us though May 18 13:47:46 i had the same warning message about 16.04 May 18 13:47:51 fray : No problems between krogoth and 16.04 May 18 13:47:58 fray : for now May 18 13:48:02 fray : but still not tested May 18 13:48:22 i wonder if there are problems because its LTS May 18 13:48:25 black_13 : which version of yocto you have ? May 18 13:48:27 most of my builds have been with Morty BTW May 18 13:48:37 morty May 18 13:48:41 @ Smitty_ : me too May 18 13:48:56 14.04 didn't have some of the necessary versions of software and (I might be confusing RHEL here) the kernel was too old May 18 13:49:10 old kernel == problems w/ qemu May 18 13:49:23 ok May 18 13:49:43 does yocto have ability to build an iso image May 18 13:49:47 black_13: yes May 18 13:49:47 Read the second sentence (http://www.yoctoproject.org/docs/2.3/dev-manual/dev-manual.html#enabling-your-layer) May 18 13:50:11 Smitty_ : What's bad about it? May 18 13:50:28 It says to modify a file in the build directory May 18 13:50:30 the build directory is where the build happens but conf/ inside the build directory is *configuration for the build directory* May 18 13:50:31 i have the yocto book with the fossil shells on front May 18 13:50:38 How does that make any sense ? May 18 13:50:49 Smitty_: ok, rename it workspace or something May 18 13:50:52 i must have missed instructions on how to build an iso in the book May 18 13:51:01 @Smitty_ conf/local.conf it's really build directory, it's used to configure the builddir May 18 13:51:05 rename what workspace ? May 18 13:51:19 when you see the words "build directory", pretend it says "work space" May 18 13:51:19 rburton: do you know of a guide on how to build the iso? May 18 13:51:24 Smitty_ : I don't understand what it did not make sense May 18 13:51:28 your build directory or what I call project directory is unique to YOUR configuration, this is where you should be making local configuration changes.. May 18 13:51:29 @rburton you are too fast for me ... May 18 13:51:48 PinkSnake: sorry :) May 18 13:51:50 the conf/local.conf and conf/bblayers.conf are the two primary things you will need to adjust for your local build configuration May 18 13:52:20 bblayers.conf for "Enabling " layers May 18 13:52:48 local.conf for telling which distro, which machien, do some kind of temporary tests such as IMAGE_INSTALL_append =" some packages " etc etc May 18 13:53:20 "workspace" or "build directory" or whatever is not a part of the source tree. Any modifications that I make there, don't get reflected back into the source tree, so they disappear when I next download my source tree May 18 13:53:42 so, why would I modify anyting there May 18 13:53:58 smitty, that is the intention May 18 13:54:12 if you want it to persist, you need to follow the developers guide and create a layer with your changes or new work May 18 13:54:38 the changes/new work still requires you to modify your build directory bblayers.conf to include it.. and your local.conf needs modification to tell it which machine you are tageting (if nothign else) May 18 13:54:38 That is exactly what I am trying to accomplish May 18 13:54:41 such as your layer can have a bblayers.conf.sample as we discussed earlier in the week, and a myspecialdistro.conf which configures the distro stuff May 18 13:54:58 machine.conf aswell May 18 13:54:58 but lets start with putting stuff in bblayers.conf and local.conf first May 18 13:55:03 No May 18 13:55:06 yes, please May 18 13:55:06 fray, what i am trying to do is get a gstreamer plugin called faac to work (its an audio encoder) for that i would like to install libfaac as an ipk and then install the gstreamer faac plugin as an ipk May 18 13:55:34 for what purpose ? how does that help solve the problem May 18 13:55:56 Smitty_: walk before you can run. get an image working with what you want, and then move the specific pieces that you need persistant into the layer May 18 13:56:04 Smitty_ : Because if you would like to add library, it's the way you should do. May 18 13:56:26 pagios, ok.. that error indicates that during the installation time there was a dependency on something that did not exist (wasn't built) May 18 13:56:33 Smitty_ : It's kind of development process. May 18 13:56:39 so either there is a typo is what you asked it to do -- or there is an error in the recipe you tried to use... May 18 13:56:44 it's totally senseless May 18 13:56:47 fray, ok how can i know what is the dep? May 18 13:56:48 I've not worked with that item to know beyond that May 18 13:57:06 the dep is what was reported on the screen.. lib.... (< ....) stuff in the ( ) is the version ifnromation May 18 13:57:23 Smitty_ : So if it is totally senseless, 99% of the way the things are done is completely senseless. May 18 13:57:24 how does that make any sense at all - please, what is the big mystery ? what secret do you all know, that I don't May 18 13:57:26 libfaac0 (>= 1.28) * May 18 13:57:44 fray, is there a recipe for libfaac0 ? May 18 13:57:46 build directory -- local to YOU where you configure what you want built... May 18 13:58:03 layer collection of 'things' May 18 13:58:11 recipe items that can be 'built', lives inside of a layer May 18 13:58:15 ? May 18 13:58:19 talkign to me? May 18 13:58:20 no mystery.. different purposes for each.. May 18 13:58:22 pagios no.. May 18 13:58:30 Build Directory = the Kitchen Workspace May 18 13:58:33 pagios -- libfaac0 should come from the 'faac' recipe May 18 13:58:48 unfortunatly that is the best I can tell you.. I've not done anything beyond that.. sorry May 18 13:58:52 You set which machine you will use to bake, such as for example furnace, knife etc.... May 18 13:59:58 For example, which type of image you would want ! ( if it is supported ) ubifs, wic.... May 18 14:00:47 Please explain how modifying a file in the build directory solves the requirement that I have explained in detail May 18 14:00:48 there has to be a way to set your local build items.. since layers are 'generic' (for the most part). And there is a very very large number of combinations possible with the various generic configurations available.. May 18 14:01:21 Because it's in the build directory that you say in which layer you will take the recipe that you need May 18 14:01:32 You MUST (no choice) configure your build directory.. youre "requirement" was that you want it reproducible for others.. so to do this, a combination of 'configure your project 'this way' and here is the layer I created -- is the official answer from the YP.. May 18 14:01:51 if you don't like it, then use a differnet build system.. this is the way the system is designed and has worked for many many years.. May 18 14:02:08 if the documentation is confusing, then suggest fixes and ask questions.. we are happy to help and want to improve the docs May 18 14:02:14 Smitty_: if you want to avoid forcing modifications then your layer can provide bblayers.conf.sample and local.conf.sample so it uses your layers and configuration out of the box. i told you this every day this week so far. May 18 14:03:44 Smitty_ : for example i have layers that includes recipes which depending the machine I use, it will ad some files. So if I don't specify in the build directory which machine i would like, how can it works ? for example? May 18 14:04:54 Smitty_ : It's like if you are seeing that you are using a microwave and you say """what is the purpose of telling the time of cook and the power used??""" If you put something in your microwave and you just close it, nothing will happen. May 18 14:19:06 rburton: oe-init-build-env calls scripts/oe-setup-builddir, that then calls other scripts. At some stage, after reading through these scripts, it rapidly becomes apparent that I really don't want to understand everything they do, I just want to hope that they work. So, I want to take the exisiting "sample" or "reference" project which allows me to build an OS IMage, and I want to make minimal modifications to it to satisfy my nee May 18 14:19:58 rburton: Any suggestion that I modify something in the build directory just doesn't make sense to me - I want my changes to be permanent, why would I make them in the build directory ? May 18 14:21:02 answered that *so many times* now May 18 14:21:23 any way look as i've spent vast amount of time on this already i've just gone and created an example May 18 14:22:57 Where ? May 18 14:25:59 https://github.com/rossburton/customdistro May 18 14:26:12 uses git submodules to pull in bitbake and oe-core May 18 14:26:31 has a custom oe-init-buildenv wrapper to specify where the templates are May 18 14:26:36 @rburton +1 May 18 14:26:53 i dislike having to use .. in some paths but they're rooted on where oe-core is May 18 14:27:30 that has a layer which provides a custom (minimal) distro, a bblayer.conf.sample adding itself, and a local.conf.sample that sets the distro to custom May 18 14:27:52 i used submodules because i know how they work and i wanted to get it done in five minutes May 18 14:28:11 wow, you understand submodules? May 18 14:28:44 Crofton: understand may be stretching the definition. i know how to make it fetch. May 18 14:28:51 updating means reading the manual :) May 18 14:28:55 still better than I May 18 14:29:02 git submodule add May 18 14:29:06 lol May 18 14:29:11 first attempt used my local aliases so oe:bitbake May 18 14:29:26 git was stupid enough to put that in the file so nobody else would be able to use it May 18 14:31:56 git pull https://github.com/rossburton/customdistro.git fatal: Not a git repository (or any parent up to mount point /home) May 18 14:32:13 @Smitty with clone maybe ? May 18 14:32:34 yeah that's not how git works May 18 14:32:36 d'oh May 18 14:32:51 Jeesus, getting tired May 18 14:34:20 ./custom-init-env: line 6: openembedded-core/oe-init-build-env: No such file or directory May 18 14:35:22 you need to fetch the submodules too May 18 14:35:54 something similar: https://github.com/ni/nilrt/blob/nilrt/comms-2.0/ni-oe-init-build-env May 18 14:35:55 git clone —recursive would have done it May 18 14:36:32 custom distro with submodules... May 18 14:36:57 what submodules is ? May 18 14:37:08 Can't anybody do anything that is simple any more May 18 14:37:16 Smitty_ : Is just simple. May 18 14:37:20 submodules aim to make it simple May 18 14:37:38 unless you'd prefer to manually clone & checkout specific shas of multiple repos :) May 18 14:37:39 Smitty_ : its you that making it complex ahah May 18 14:37:53 Smitty_ : but you can be a contributor to make the things simple ! May 18 14:38:02 Smitty_: the alternative is copy/paste all of bitbake and oe-core, or ask you to clone them both to a specific sha and expect you to do it right May 18 14:38:49 I'm refering to git's use of submodules May 18 14:39:05 yeah they're not pretty but they work and everyone has them May 18 14:39:58 Clearly when a submodule is added to a project, the author intends it to be a part of the project. Why would I have to specify that I want to include the submodule. Hek, that implies I know *beforehand* the structure of somebody else repository May 18 14:42:00 jesus, how do you make an rpi-3 work with an 800-480 flat panel May 18 14:42:27 Smitty_: the submodule project can be modified independently of the main project, you get the code without copying it to your main git top-level repo/workdir and you can easily track the other project development, even if upstream pushes new versions your submodule ref is constant May 18 14:42:35 aratiu: ni.github.io looks like interesting browsing May 18 14:42:40 rburton: I am so sorry - but: fatal: unable to connect to git.openembedded.org: git.openembedded.org[0: 104.236.212.160]: errno=Connection refused May 18 14:43:24 it's a lot easier to work with submodules when having subprojects which are themselves independently evolving projects to which you can also contribute, you can switch to your test branches locally and work with them in the submodule before they're integrated in their upstream May 18 14:43:40 Yes, it's a crappy implementation of svn:externals, from what I can tell - I am very, very familiar with the concept May 18 14:44:02 I do this all the time for example for my emacs configuration at https://github.com/10ne1/emacs-config May 18 14:44:42 Smitty_: works here, i suspect proxies May 18 14:44:52 Damn It ! May 18 14:45:24 I am so fed up with this crap, I'm about ready to quit this job May 18 14:47:34 Smitty_ : Proxy yeah i guess May 18 14:47:48 Smitty_ : I asked for a internet connection only for me to not have this kind of problem May 18 14:48:42 I can do this from home, of course, but, here in the office I can't access anything May 18 14:49:03 Smitty_ : But it's not the point of working at home :( May 18 14:49:45 Smitty_: clone normally without recursive, edit the .gitmodules to refer to http: instead, then fetch? May 18 14:49:55 no need to do it from home, just configure your proxy support May 18 14:50:10 but yeah git can tunnel out of the office just fine May 18 14:50:38 I've already set git proxy May 18 14:51:31 perhaps not correctly? May 18 14:52:02 [http] proxy = http://proxy.MYCORP.com:9999 May 18 14:52:15 what else is there to do ? May 18 14:52:43 git:// is not http May 18 14:52:55 which is why i said to fetch, edit, submodule fetch May 18 14:52:56 that's from .gitconfig May 18 14:53:13 huh ? May 18 14:53:43 https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy May 18 14:54:12 your corporation may have more specific configuration information available May 18 14:54:32 basically, git can't trivially proxy a git: URL May 18 14:55:04 Honestly, who dreams this crap up. May 18 14:55:11 why it can't just have a 'socksproxy' option nobody knows May 18 14:55:44 It doesn't need to be so complicated - why does everyone feel like they have to reinvent the wheel May 18 14:56:05 send a patch, i'm sure evveryone behind a proxy would love you if making git use socks was a one-liner May 18 14:56:40 Not a chance, I'm sure the git code is worse than anything else known to man. May 18 14:57:08 Smitty_: changed the URLs, re-clone with --recursive May 18 14:58:03 It was hacked together over a weekend, then added to over the past several years. I'm pretty sure I'd kill myself after about 5 minutes May 18 15:00:40 in my .bb file i see PACKAGECONFIG[faac] = "--enable-faac,--disable-faac,faac" , i want to compile the gstreamer faac so i did add to the EXTRA_OECONF --enable-faac --with-plugins=rtmp,rtmpdump,faac,libfaac" anything else missing? May 18 15:01:25 rburton: That works - thanks tons !. (weird I don't see the usual progress indicators during download) Maybe with your beautifully simple example, I can start making some progress May 18 15:01:44 yeah no progress with http clones May 18 15:03:33 completed, now, I source custom-init.. no targets yet ? May 18 15:03:43 how do I start with this ? May 18 15:04:02 bitbake May 18 15:04:08 its just oe-core May 18 15:04:18 but you'll see that you have custom bblayers and local.conf May 18 15:04:22 So, this is not an OS Image ? May 18 15:05:56 Sorry, obviously still not understanding. What have you provided here ? May 18 15:08:50 There is no target. May 18 15:09:22 you tell bitbake what you want to build May 18 15:10:41 the point was to show you how to provide a customised local.conf and bblayers.conf May 18 15:10:46 so the user doesn't have to do that May 18 15:11:03 meta-custom would also have a custom image in your situation May 18 15:11:13 so then the user would just do bitbake mycustomimage May 18 15:14:03 you can add a conf-notes.txt to meta-custom/conf/ to have it print suggested targets May 18 15:14:13 I'll look at this tomorrow, got to go now. Thanks again, I know I am frustrating the crap out of you - but I don't mean to be May 18 15:16:54 This might sound odd, but can I modify RPROVIDES based on content from ${S} and have other recipes correctly see it (i.e. be able to RDEPEND on it)? May 18 15:17:49 I have it working for the package generation (the .ipk show up as a provider), but other recipes can't RDEPEND on it May 18 15:18:48 JPEWhacker: rdepends/rprovides are used in two ways, first it's used by bitbake for runtime dependency generation, second it's placed in the binary packages. to modify it based on S, you'd have to do so in a task, not at parsing time, which would be long, long after bitbake has used it for runtime dependency handling, so it would only be able to alter the packaging May 18 15:19:28 you could add it to PACKAGES_DYNAMIC, however. this variable is a space separated list of wildcards patterns of what packages you might emit. it's most commonly used for recipes that emit a set of subpackages based on e.g. what plugins were built May 18 15:19:59 it's how you tell bitbake about packages you might emit, but don't yet know until packaging time May 18 15:20:16 so a combination of a new function in PACKAGEFUNCS and PACKAGES_DYNAMIC *might* work May 18 15:20:22 but i'd really recommend you look into alternative possibilities May 18 15:21:24 Ya, It's probably not an ideal situation, but I wanted to explore it. May 18 15:22:27 joshuagl: oh good idea May 18 15:22:51 What I really want it to be able to create a user that is a member of a set of groups, and have the user recipe get the dependencies on the recipes that provide those groups in a somewhat painless manner May 18 15:26:50 Smitty_: pushed more tweaks to make it include a custom image, and documentation when you run custom-init-env May 18 15:28:50 PACKAGE_DYNAMIC worked, but I would be open to better suggestions May 18 15:41:23 I solved the issue with mesa not providing libGL, even the desktop profile OpenGL functions are available in the libGLESv2.so by resolving the functions at runtime (using eglGetProcAddress). But I think it should be possible to build Mesa without X11 to create the libGL.so using EGL as context creation backend May 18 15:41:56 tlwoerner, any tips on getting audio driver to load on pi3? May 18 15:42:05 google space is polluted May 18 15:46:10 too many questions today, any idea where to find the VOAAC ENC package? May 18 15:46:12 recipe May 18 15:46:49 layers.openembedded.org? May 18 15:46:50 https://layers.openembedded.org/layerindex/branch/master/recipes/ May 18 15:47:06 No matching recipes in database. May 18 15:47:24 https://layers.openembedded.org/layerindex/recipe/41448/ May 18 16:20:11 where can i find instructions how how to make a iso of the minimal build May 18 16:20:58 black_13: put iso in IMAGE_FSTYPES May 18 16:21:11 ah! May 18 16:21:21 local.conf May 18 16:22:00 or distro, or image, wherever May 18 16:22:11 but thats the variable you're looking for May 18 18:02:26 A layer is a collection of recipes as well as potentially a configuration for an image (and maybe other stuff) ?? May 18 18:20:45 SomeDumbBumb: images are recipes. May 18 18:24:10 * paulg wasn't sure what the original question was.... May 18 18:24:45 the vagueness of "stuff" perhaps? May 18 18:52:12 to make an image requires a recipe for the image May 18 19:00:13 Does each layer always define an image ? May 18 19:00:21 or a distro ? May 18 19:00:25 or is that optional May 18 19:02:59 Unrelated question, but this caught my eye. "The script gets its default list of common targets from the conf-notes.txt " WTF would that be. Why wouldn't the current configuration end up populating the list of available targets ? May 18 19:03:16 SomeDumbBumb: all targets? May 18 19:03:26 even in oe-core thats several hundred May 18 19:03:53 not sure that would be useful May 18 19:04:22 OK, point taken. May 18 19:04:49 multipled for every native form, every nativesdk form, every multilib variant May 18 19:06:05 so, "common targets" is not all targets - what's it for ? May 18 19:06:15 exacrtly what it says May 18 19:06:21 poky says you may enjoy core-image-sato May 18 19:06:45 the conf-notes.txt is just a file that is displayed when you init the build env May 18 19:06:51 in what way are the targets in conf-note.txt "common" what does that mean ? May 18 19:06:57 say hello, put a quote of the day, whatever May 18 19:07:07 Common targets are: May 18 19:07:07 core-image-minimal May 18 19:07:07 core-image-sato May 18 19:07:07 meta-toolchain May 18 19:07:07 meta-ide-support May 18 19:07:21 they are common targets. the minimal image, the GUI image, a (deprecated, whoops) toolchain May 18 19:07:29 common for the *example* distro May 18 19:07:46 so, top level targets ? May 18 19:07:54 images and SDKs May 18 19:08:07 again its just a message, you can make it say anything May 18 19:08:10 an image is target, right ? May 18 19:08:25 in the context of this message yes May 18 19:08:32 the message could and probab;y should use recipe instead of target May 18 19:08:38 just to unify syntax May 18 19:08:52 it only says target because the line above says "bitbake " May 18 19:08:58 * rburton -> cook dinner May 18 19:09:04 so how do I know what images I can build ? May 18 19:29:32 SomeDumbBumb: in the real world, you know because you wrote them. if you didn't write them a colleague did and listed them in conf-notes.txt. in the abstract sense, 'bitbake-layers show-recipes -i image' will list all recipes that inherit the image class. May 18 19:33:56 rburton: I was looking at your ross/mut2 and there is one patch from me you can throw out for now "bash: Fix build with clang+security flags" May 18 19:34:23 rburton: and there are are few missing in that branch that I submitted May 18 19:35:02 rburton: see http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master May 18 19:35:46 you can leave the gcc/glibc ones out but others should be good to go May 18 19:36:52 yeah thanks May 18 19:36:59 been picking a bit oddly ;) May 18 19:37:19 khem: fwiw mut2 with musl failed like https://autobuilder.yoctoproject.org/main/builders/nightly-musl/builds/459/steps/BuildImages/logs/stdio May 18 19:41:16 error: 'PATH_MAX' undeclared May 18 19:41:44 trace-cmd need to include limits.h somewhere May 18 19:42:17 same is true for kernelshark May 18 19:42:26 see how musl keeps people honest ? May 18 19:42:50 so let the submitters know they have work to do May 18 19:48:45 OK, I can understand not displaying all the possible build targets, I mean, you wouldn't do that on any build system I know of. BUT, the whole point of yocto is buulding OS images, right ? So, why not display the list of images that were detected ? Or, is it because basically, there's no way to know - beuase an image is just a collection of things that can be built ? May 18 19:55:37 If you use the toaster, it will give you a list of all image targets available for your configuration. May 18 19:57:20 khem, if you have five mins pls try to build klibc against musl. I see in6.h & friends clashing May 18 19:58:13 there have been fixes to linux-libc-headers for musl about that May 18 19:58:18 iirc May 18 19:59:23 I used the toaster and got burnt bread. Wonder what I did wrong.... May 18 19:59:46 maybe I need to stick a fork in it and probe around. May 18 20:08:50 khem: so my glorious plan for 2.4 is 1) merge llvm, 2) add a nice way to change toolchain like we can change libc, so 3) meta-clang can have a tidy toolchain-clang.inc instead of clang.bbclass May 18 20:08:53 khem: sounds good? May 18 22:28:34 Crofton: oops, totally missed your question. audio works automagically for me on the raspi3; both via HDMI and the 3.5mm jack. last time i tested that was about 6 weeks ago, so i guess i'm "due" ;-) May 18 22:53:24 yes it should unless the kernel module is missing or snd device is not created May 19 02:35:12 what meta command do I add to local.conf to build an iso image for the minimal build. **** ENDING LOGGING AT Fri May 19 03:00:01 2017