**** BEGIN LOGGING AT Fri Jul 19 02:59:58 2013 Jul 19 03:03:33 damn, i should've checked sooner... Jul 19 03:04:13 stupid proxy doesn't back-fill the user list Jul 19 07:30:54 Hi Jul 19 07:31:19 I'm investigating how to play video files with Qt in a qemu with a bitbaked qemuarm linux image :) Jul 19 07:31:30 Now I understand that for Qt4 I need phonon :) Jul 19 07:32:52 But I assume the qt4-pkgs don't include phonon by default (I'm looking at it, but I'm still waiting for find :/) Jul 19 07:42:22 find did not return qt4-pkgs? Jul 19 07:42:30 I thought it was a recipe? Jul 19 07:44:08 all i see is packagegroup-core-qt4e.bb has qt4-embedded-plugin-phonon-backend-gstreamer in it Jul 19 07:46:13 I'm not using Qte Jul 19 07:46:15 but Qt Jul 19 07:46:32 besides Qt Embedded is deprecated in version 5 Jul 19 07:48:31 that's just all i get from find/grep in poky master/meta-openembedded Jul 19 07:49:22 hhhmm, crap XD Jul 19 07:49:43 and meta-qt5 even Jul 19 07:50:06 nerdboy: meta-qt5 is still not "complete" Jul 19 07:50:50 yeah, not really using it... Jul 19 07:51:43 nerdboy: probably the maintainer told me that it doesn't support generating a toolchain so, I was asking myself why people would use it :o Jul 19 07:54:38 well, it's past my bedtime Jul 19 07:56:33 nerdboy: hahaha okay goodnight I presume (it's morning here) Jul 19 07:59:52 okay I'm officialy retarded, I forgot to source the enviroment before I started using qtcreator that's why it couldn't compile decently Jul 19 08:16:04 Can I assume that phonon is not supported by qemu? Jul 19 08:26:32 fenrig: I don't think there's any connection, as far as I am aware Jul 19 08:28:07 morning all Jul 19 08:37:34 bluelightning: morning ;) Jul 19 08:37:41 hi fenrig :) Jul 19 08:37:52 bluelightning: how do u mean "there is any connection"? Jul 19 08:38:30 fenrig: well, phonon exists as a way to isolate Qt/KDE applications from changes in the underlying audio input/output/codec system Jul 19 08:38:58 bluelightning: okay sounds intelligent, Qt is wel organised Jul 19 08:39:00 fenrig: qemu just needs audio input/output Jul 19 08:39:26 bluelightning: okay but I tried making a base Qt phonon application Jul 19 08:39:52 bluelightning: and Qemu is complaining: "VideoPlayback: error while loading shared libraries: libphonon.so.4: cannot open shared object file: No such file or directory" Jul 19 08:40:04 my application is called VideoPlayback ;) Jul 19 08:40:12 or better said named :p Jul 19 08:40:19 er, qemu is complaining about that? or your application is? Jul 19 08:40:33 bluelightning: well my application Jul 19 08:40:48 bluelightning: but I'm executing it on the qemu, that's why I said qemu is complaining Jul 19 08:40:53 right, that makes a bit more sense Jul 19 08:41:33 it sounds like it just doesn't know how to find the library, assuming libphonon.so.4 is installed in /usr/lib in your image Jul 19 08:42:05 bluelightning: I did a search in my layers and I couldn't find a file name which contained phonon :o Jul 19 08:42:11 bluelightning: not even a recipe :/ Jul 19 08:43:57 fenrig: it is mentioned in qt4.inc which is used by the qt4-* recipes Jul 19 08:46:30 Hello people. I'm as fresh n00b as you can get on the yocto project, and I'm currently considering if we should adopt yocto or not. Jul 19 08:46:30 bluelightning: hhhmmm better take a look at it first Jul 19 08:46:52 sveinse: what do u want to do with it? Jul 19 08:47:30 bluelightning: on a side note: I'm also still a noob although I'm playing with it intensively for 3 weeks now Jul 19 08:47:46 bluelightning: that was not meant for you XD Jul 19 08:47:59 sveinse: on a side note: I'm also still a noob although I'm playing with it intensively for 3 weeks now Jul 19 08:49:03 We have a product on the market which runs on omap3 and is Ubuntu based. It's custom HW and we have already kernel in place for that. Since this is Ubuntu, we have gained .deb experience, and have our SW based around that environment. Jul 19 08:50:24 BUT Ubuntu is horrobly slow for our use, and thus we are looking at alternative. Having generic desktop-based Ubuntu to run embedded product that performs one specific task is, well, wasting a lot Jul 19 08:50:30 sveinse: pardon me but what do u exactly mean with .deb experience, you mean compiling and packaging custom packages? Jul 19 08:51:57 fenrig: Both. I took our ppl some time to develop the skill to create deb packages, but also creating the build environment around deb's to be able to build filesystem images usable on target. Jul 19 08:52:26 One example is that Ubuntu (nor Debian) is not created for cross compilation, so thats a major challenge you want to overcome somehow Jul 19 08:53:22 sveinse: okay sounds reasonable, but with yocto I don't think you get to use this experience much :/ as the build system of yocto does this all for you Jul 19 08:53:33 sveinse: from compiling to packaging to creating an image Jul 19 08:55:38 fenrig: Yes. And since we have a working environment for Ubuntu and debs, it will be a larger transition if we changed over to yocto. So we need to gain somthing from adopting yocto Jul 19 08:56:54 So let me dive into the questions, I just saw the screencast by Scott Garman/Intel about yocto. The slides mentiones deb/rpm/ipkg, but he does not mention it. How does/can yocto take use of pkg-systems? Jul 19 08:58:01 sveinse: yes well I'm not really "qualified" to answer that correctly, but I think you have to forget the deb experience completely. Yocto is different, it works with a complete metadata tree that consists of layers Jul 19 08:58:54 sviense: you have machine layers, you have layers with applications (I understand they are seperated in a vendor like way, for instance there is meta-ti from texas instruments or meta-fsl from freescale) Jul 19 08:59:30 the cool thing about yocto is Jul 19 08:59:44 fenrig. Yes, the poky/BB recepies and layers are all fine. That will be a migration, sure. But it seems (from the slides at least) that BB can output binary packages which can be used for later install on target Jul 19 08:59:49 that because of these layers you actually have quite "independend" cross generation tools Jul 19 09:01:03 so when u want to switch to another machine/cpu then you just have to have the correct machine bsp and issue another bitbake command (eg. MACHINE=beaglebone bitbake your-custom-image --> MACHINE=raspberrypi bitbake your-custom-image) Jul 19 09:01:41 Is a BSP more than just a kernel[config]? Jul 19 09:02:03 then there is also the toolchain part of yocto, yocto can actually generate certain cross toolchains for you so you can easily use it for development (MACHINE=raspberrypi bitbake meta-toolchain-qt) Jul 19 09:02:57 sveinse: yocto is quite modular, but in some aspects not feature complete. Don't forget it's a difficult system with a steep learning curve Jul 19 09:03:09 bluelightning: correct? Jul 19 09:03:38 sveinse: and things are constantly evolving and changing Jul 19 09:03:46 Does yocto have sysv only, or does it also have upstart available/ported? Or is perhaps that a Canonical-thing Jul 19 09:04:32 sveinse: that depends on the yocto distro you are using (look at poky, angstrom , ...) but I think linux is evolving to a systemd way of starting services Jul 19 09:05:03 sveinse: and that's also to be seen in yocto, but then again I'm only recently started using yocto Jul 19 09:06:00 JaMa: are you available for some questions about qt4 Jul 19 09:06:50 My point is this: I have downloaded poky and can build a simple qemux86 core-minimal-image. Fine. How do I start from there adopting this to my custom HW? I have a custom kernel Jul 19 09:07:06 Where do I start? Jul 19 09:08:19 ok, I find lots of docs on the web page, so before I bother everyone with my million questions, I'll spend some time there Jul 19 09:09:07 sveinse: start by devising a BSP, look at other BSP's. Can you tell us what hardware you are using, maybe some layers already exist for this hardware? Jul 19 09:10:12 Its omap3 bases, so its not too different from beagleboard. But there are custom hardware on it, and thus custom kernel drivers and config. Jul 19 09:10:37 fenrig: I'll take a look at the beagleboard BSP Jul 19 09:11:58 sveinse: display drivers and stuff? Jul 19 09:13:04 fenrig: No more than whats in omap3; fbdev and the PowerVR/SGX OpenGL drivers Jul 19 09:13:52 fenrig: We're running qt4 app on fbdev, so no X Jul 19 09:14:48 sveinse: directfb? Jul 19 09:15:13 sveinse: oh then look at the meta-ti layers Jul 19 09:15:40 fenrig: I'm not sure of the distinction between directfb and fbdev, if there are any. But we're using /dev/fb0 Jul 19 09:15:41 sveinse: they are quite extensive, and I understand that texas instrumens is quite dedicated to the yocto project Jul 19 09:16:10 sveinse: I think in order to use fbdev you need directfb in Qt, but I'm not quite sure Jul 19 09:16:47 fenrig: qt4 has poor OpenGL support and since there is no 2D accel in OMAP3, we ended up using SW rendering of the graphics. This is all about to change when we migrate to Qt5 Jul 19 09:17:28 sveinse: well with yocto you'll have to wait using Qt5, because it's still a work ongoing ;) Jul 19 09:18:26 fenrig: No worries, There's a large job internally as well, since the QtQuick-scripts needs porting Jul 19 09:19:12 fenrig: But TI has more or less "forgotten" the OMAP3. They don't maintain such stone age tech in any details, it seems Jul 19 09:20:34 sveinse: I think maintaining drivers (Xorg and kernel device drivers) seem like a big job with the current pace of the linux kernel Jul 19 09:21:46 fenrig: Why is Qt5 not available? I believe given a decent cross compiler and the Qt5 source, it should not be problems compiling Qt5. I mean Qt is one of the better suits out there handling cross compilations Jul 19 09:22:12 sveinse: well first of all there is no qt5 toolchain support Jul 19 09:22:22 zibri, Are you around? Jul 19 09:22:39 sveinse: it is possible to create a linux image with qt5 packages Jul 19 09:22:49 fenrig: Oh. What gcc is yocto using? Jul 19 09:22:55 sveinse: but there isn't any toolchain support and I suppose you need a specific qmake Jul 19 09:23:24 sveinse: to develop applications in a cross platform manner Jul 19 09:24:04 sveinse: gcc support is not the problem but generating a cross development sdk with Qt5 is not supported Jul 19 09:24:05 fenrig: Hmm. I'm surprised. qmake is build as a part of the host tools when you build Qt. Unless they've done radical changes to that Jul 19 09:24:38 sveinse: HHHmmm maybe I've said it wrong Jul 19 09:25:07 sveinse: It's completely possible to create a linux image with qt 5.0 packages, so you can run qt 5 applications Jul 19 09:25:34 sveinse: but in order to cross compile (because I don't think you'll be compiling the application on target) you need to generate a cross SDK Jul 19 09:25:50 sveinse: and that cross SDK is not implemented yet ;) Jul 19 09:26:18 Ah, so its yoctos adoption of the Qt development scheme. Good luck with that. Jul 19 09:26:56 sveinse: well they are busy implementing it, but Qt5.1 support is given more importance at the moment Jul 19 09:26:56 stygia: yes Jul 19 09:27:22 I think we've spent a few dozen hours on getting Qt tools to work seamless into our build system. A real trial, and pain at times. Jul 19 09:27:58 zibri, You said something about a recipe providing the libraries for perl, perl-libs or something? There is nothing like that, although perl PROVIDES perl-module-libs, is that what you meant? Jul 19 09:28:06 sveinse: I have too, but only with the yocto system :/ I'm still a student and I have much to learn Jul 19 09:28:14 zibri, If I didn't have to make a bbappend just to get basic perl features that'd be pretty sweet. :) Jul 19 09:29:33 stygia: i think it's called perl-lib Jul 19 09:29:37 JaMa: Can you answer some questions concerning Qt4 and phonon when you have time? Jul 19 09:30:45 zibri, Ah well, I get "nothing provides perl-lib", is it supposed to be in oe-core? Jul 19 09:31:01 fenrig: "They" <-- where are this effort being discussed? yocto (at) yoctoproject (dot) org? Jul 19 09:31:14 stygia: yes, it's supposed to be provided by the perl recipe.. :/ Jul 19 09:31:48 sveinse: I reccomend that you first review yocto before making any descisions. Some things are awesome about yocto and somethings are a pain in the ass. Jul 19 09:32:10 sveinse: I think they do that at the mailing list, but I thought that JaMa in this channel is the responsible maintainer Jul 19 09:32:25 sveinse: https://www.yoctoproject.org/tools-resources/community/mailing-lists Jul 19 09:32:28 zibri, Ah yes, right, I grepped for it and it's in there. Jul 19 09:33:01 fenrig: I don't think I can review yocto without getting my feet wet. So some head-on approaches is needed :) Jul 19 09:33:19 sveinse: Indeed. Try to setup some basic goals Jul 19 09:33:48 sveinse: I've started with generating a custom linux image for my beaglebone Jul 19 09:33:59 sveinse: but then ran into some GFX driver issues Jul 19 09:34:44 sveinse: then I tried generating a cross sdk for qemuarm and integrated the sdk into qtcreator Jul 19 09:35:37 sveinse: and at this moment I'm trying to enable video playback with Qt (and phonon) on my qemuarm image Jul 19 09:36:15 sveinse: take a look at the official documentation, but don't fixate yourself on it. Some parts are a bit old and things rapidly change in yocto. Jul 19 09:37:19 sveinse: may I ask from where your company is ? Jul 19 09:42:28 bluelightning: Indeed phonon should have to be supported :/ maybe I'm doing something wrong in my application Jul 19 09:42:58 bluelightning: but then again I couldn't find a file on the qemu machine that contains phonon Jul 19 09:42:59 so Jul 19 09:43:13 stygia: but still doesn't work? :/ Jul 19 09:43:53 zibri, Hmm well, I can't build or depend on perl-lib, and the result is that crucial modules are not included. Jul 19 09:44:02 zibri, However I've made a perl.bbappend to include them. Jul 19 09:44:51 fenrig: erm, so is libqtphonon4 installed on your target system? Jul 19 09:45:59 Stygia: is this it? (ignoring the erroneous DESCRIPTION value): http://git.yoctoproject.org/cgit/cgit.cgi/meta-security/tree/recipes-security/perl/lib-perl_0.63.bb Jul 19 09:47:28 bluelightning: the perl recipe within oecore builds a 'perl-lib' package, containing all the core modules. Jul 19 09:47:50 ah, right Jul 19 09:47:55 bluelightning, I'm not quite sure, but I don't think so, URI.pm is one of the files but not all of them Jul 19 09:48:20 zibri, Yes, I saw that. However, building the vanilla perl, which provides that, still leaves several modules lacking (From what I saw) Jul 19 09:48:29 bluelightning: is libqtphonon4 a recipe? because then I can check with the dependency tree tool Jul 19 09:48:33 bluelightning, zibri, the recipe Bluelightening provided does _Some_ of it. Jul 19 09:48:49 fenrig: no, it's a package built as part of Qt itself Jul 19 09:49:39 Stygia: I thought the description was incorrect... Jul 19 09:49:57 bluelightning, It's quite possible it provides more files? I don't know. Jul 19 09:50:02 bluelightning: I couldn't find any reference of phonon on the rootfs :o so I guess not Jul 19 09:50:13 This is my current bbappend, of all the core files I noticed missing from the perl distribution: http://pastebin.com/NEvMCnQY Jul 19 09:50:31 RDEPENDS on just "perl", anyway, does not include this. Maybe lib-perl, or something, I haven't tried that one. Jul 19 09:51:02 bluelightning: which is quite odd because it's a part of qt4-x11-free Jul 19 09:51:04 fenrig: ok, so assuming you're building your application separately and deploying it to the target manually (as opposed to building it via a recipe -> a package and installing that) you'll need to manually ensure all the appropriate Qt libraries are installed Jul 19 09:51:26 fenrig: which in this case would mean adding libqtphonon4 to your IMAGE_INSTALL Jul 19 09:51:33 bluelightning: and qt4-x11-free is included in the image with image_install Jul 19 09:51:40 bluelightning: so it is a recipe? Jul 19 09:51:52 fenrig: qt4-x11-free is a recipe, libqtphonon4 definitely is not Jul 19 09:52:25 fenrig: and yes if you have explicitly installed qt4-x11-free I don't know how you could not have libqtphonon4 brought in as a dependency unless for some reason it never got built Jul 19 09:52:56 bluelightning: but then how does adding libqtphonon4 to image_install help me? I thought that image_install only accepts recipes? Jul 19 09:53:15 fenrig: no, it's the opposite, IMAGE_INSTALL expects package names Jul 19 09:53:44 fenrig: it just happens that in ~95% of cases the main package for a recipe has the same name as the recipe (i.e. ${PN}) Jul 19 09:54:04 bluelightning: oh, but in the other 5% I should have an error about it? Jul 19 09:54:21 fenrig: yes Jul 19 09:54:33 bluelightning, I will try and build with the lib-perl recipe and see if any of the files I included in my bbappend are lacking Jul 19 09:55:00 fenrig: could you please check if libqtphonon4* exists in tmp/deploy/// ? Jul 19 09:55:00 bluelightning, I think if they are still missing then it'll be a bug in the OE recipe for perl... which I honestly already consider buggy for not including all this on when "perl" is depended on. Jul 19 09:55:21 bluelightning: okay will do Jul 19 09:55:50 Stygia: but if that were the case then wouldn't it be impossible to have a perl installation containing only the bits your application needs? Jul 19 09:56:04 bluelightning, Good point. Jul 19 09:56:18 bluelightning, But I'm not sure we should be removing core parts of perl. That seems like an invitation to trouble. Jul 19 09:56:34 bluelightning, Perl gets kinda bloated, I suppose, but the standard library IMHO should always be included. Jul 19 09:56:54 Stygia: it's possible we have things packaged incorrectly, so if you do see something that looks wrong please file a bug Jul 19 09:57:20 bluelightning: " cd build/deploy " " find | grep libqtphonon4" doens't return anything :/ Jul 19 09:57:26 bluelightning: so it's not a part of it Jul 19 09:57:39 fenrig: ok then you'll need to look at log.do_configure for qt4-x11-free to find out why not Jul 19 09:57:51 bluelightning, It _may_ be a question of preference, I suppose - Do we want a full but bloated perl, or just the core language? Jul 19 09:58:09 bluelightning, As for me, I feel that removing standard library componets is a mistake, disk space be damned. Jul 19 09:58:09 bluelightning: and where again can I find these log's? Jul 19 09:58:17 Stygia: ideally we provide people with the option to have either Jul 19 09:58:27 Stygia: assuming that is practical Jul 19 09:59:00 fenrig: tmp/work//qt4-x11-free//temp/log.do_* Jul 19 09:59:26 bluelightning, Hmm. Perhaps your current recipe could be renamed something like perl-minimal and I could put in a patch to add the corelib files to the regular perl recipe? Jul 19 10:00:18 Stygia: erm... well, surely if there were a specific package containing all the core libs that could be the dependency and it would work without needing an additional recipe? Jul 19 10:00:37 http://www.debian.org/doc/packaging-manuals/perl-policy/ch-perl.html#s-base Jul 19 10:00:38 bluelightning: thx ;) Jul 19 10:00:55 Stygia: s/containing/depending on/ Jul 19 10:00:58 bluelightning, I'm not quite sure I understand. Jul 19 10:00:59 bluelightning: debian style or Gentoo's style... Jul 19 10:01:08 bluelightning, Ah, right. Jul 19 10:01:41 bluelightning, Hmm well, that isn't what I did, the core libs aren't recipes as such, they're just files build by perl that aren't included in FILES by the perl recipe by default. Jul 19 10:01:44 stygia: the way it's packaged now is very similar to the way debian packages it, with the interpreter in the perl package and the core modules in the "perl-modules" package Jul 19 10:02:20 Stygia: yes but they aren't being thown away, they do get packaged somewhere - right? Jul 19 10:03:03 bluelightning, I don't think so. When I build perl and included it in my image, they just weren't there. Jul 19 10:03:46 Stygia: I don't mean they go into the main perl package, I mean they go into another package that you can simply install additionally Jul 19 10:03:50 bluelightning, Grepping all the recipes I have here for one of the files I added in my .bbappend shows nothing. Jul 19 10:04:03 bluelightning, I'm not sure, but presumably nothing in oe-core, my grep returns nothing. Jul 19 10:04:16 Stygia: I would be more inclined to look at the packages-split directory of the perl workdir Jul 19 10:04:36 bluelightning: by adding libqtphonon4 to my image recipe and rebuilding the image I got phonon.so files but libqtphonon4* does still nog exist in tmp/deploy/// Jul 19 10:04:45 Stygia: since it may not be pulled in explicitly by name but instead by path or by glob (/*.pm) Jul 19 10:04:48 bluelightning: though my application now doens't complain about a missing lib ;) Jul 19 10:04:57 bluelightning: THANK YOU! Jul 19 10:05:31 bluelightning: does still not exist in tmp/... Jul 19 10:07:13 fenrig: ah I may have misled you; because of debian style renaming the package file itself ends up called libphonon4 (based upon the main .so filename) rather than libqtphonon4 Jul 19 10:07:53 fenrig: but note that you always use the name prior to any debian renaming in IMAGE_INSTALL (which is what you did, so it worked) Jul 19 10:11:02 stygia: look at e.g. tmp/work/mipsel-nf-poky-linux/perl/5.14.3-r1/packages-split Jul 19 10:11:10 bluelightning, I'll report back in a while to see if the lib-perl recipe you send me solves these issues in question. Jul 19 10:11:24 Stygia: ok Jul 19 10:11:29 zibri, Yes, I did have a look there, some of the modules do appear to be present without my bbappend, but I need to do a (lengthy) build to be sure. Jul 19 10:11:44 Stygia: which modules are you looking for? Jul 19 10:12:17 khem: ping? Jul 19 10:13:07 bluelightning, Not modules as such, but some of the core libs, including simple things like warnings.pm, strict.pm or Carp did not appear to be included in just the "perl" recipe. Jul 19 10:13:36 [Question]I have fetch the linux source code using git manually, but I don't know where to place it? Can sb. tell me ? Jul 19 10:14:43 stygia: i'm not quite sure how to make sure that all core modules gets installed though... :/ Jul 19 10:15:21 bluelightning: okay cool ;) Jul 19 10:15:30 I search my old yocto project, It seems just location at build/tmp/work/bockw-poky-linux-gnueabi/linux-yocto/3.4-r1/git/ Jul 19 10:16:25 stygia: ah, looking at the perl recipe, i see that they create a perl-modules "recommending all the other perl packages" Jul 19 10:16:38 stygia: try rdepending on that one instead of perl-lib Jul 19 10:18:14 Stygia: what zibri said ^ Jul 19 10:18:51 TonyHo: there's no way to fetch it automatically? Jul 19 10:19:25 zibri, I'll give it a shot. Jul 19 10:19:52 The bblayer prints a warnning : WARNING: No bb files matched BBFILE_PATTERN_bockw '^/home/hexiongjun/yocto-719/meta-renesas-20130719/meta-bockw/' Jul 19 10:19:58 Is this Matter? Jul 19 10:21:34 TonyHo: does that directory contain any .bb files? Jul 19 10:22:18 TonyHo: or rather, are there any .bb files in the expected path underneath that directory (as specified by BBFILES)? Jul 19 10:24:56 bluelightning: ^/home/hexiongjun/yocto-719/, why there is a ^ in the path? Jul 19 10:25:22 TonyHo: it's a regular expression, the ^ anchors it to the beginning for matching Jul 19 10:26:40 bluelightning: There is two .bb files in the meta-renesas-20130719/meta-bockw subdirectory Jul 19 10:26:59 TonyHo: what is the exact path to them? Jul 19 10:27:36 bluelightning: meta-bockw $ find -name *.bb 2>/dev/null ./recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb ./recipes-kernel/linux/linux-yocto_3.4.bb Jul 19 10:28:29 bluelightning: in meta-bockw I input ` find -name *.bb 2>/dev/null ` Jul 19 10:28:33 TonyHo: ok, what is the BBFILES line in the layer.conf file for the layer? Jul 19 10:29:51 bluelightning: /home/hexiongjun/yocto-719/meta-renesas-20130719/meta-bockw \ Jul 19 10:30:22 bluelightning: And extra relative line: /home/hexiongjun/yocto-719/meta-renesas-20130719 \ Jul 19 10:31:32 TonyHo: I meant the BBFILES line in meta-bockw/conf/layer.conf Jul 19 10:32:11 fenrig: Sorry, was away. I'm from Norway Jul 19 10:32:34 sveinse: cool, belgium here ;) Jul 19 10:33:55 bluelightning: BBFILES += "${LAYERDIR}/recipes*/*/*.bb \ ${LAYERDIR}/recipes*/*/*.bbappend" Jul 19 10:34:02 fenrig: I'm working in a medical company, and the device I'm working on is a ipad-ish control device running (Ubuntu) linux+Qt4 fullscreen Jul 19 10:34:59 bluelightning, Alright, I've compiled an image that RDEPENDS on lib-perl now. Jul 19 10:35:20 bluelightning, However, I'm still prone to conclude that there is a need for a patch to perl itself, as re.pm is still not included (pretty crucial IMHO). Jul 19 10:35:41 bluelightning, The bbappend file I posted earlier contains all the files I've concluded are missing from the perl recipe. Jul 19 10:35:48 bluelightning, I'll go file a bug report after lunch. :) Jul 19 10:36:02 Stygia: the thing is they are not missing, they're just packaged in a more fine-grained manner Jul 19 10:37:04 bluelightning, Hmm, how exactly do you mean? From what I can see, they aren't included my any of the recipes in oe-core, or the meta-security one you published lately? Jul 19 10:38:42 Stygia: strict.pm is in perl-module-strict; Carp.pm is in perl-module-carp; warnings.pm is in the main perl package (at least in master) Jul 19 10:40:39 Stygia: (as determined by find filename.pm in tmp/work/i586-poky-linux/perl/5.14.3-r1/packages-split/ on my build machine) Jul 19 10:45:03 The yocto clone the linux source code is not locate in downloads directory? Where is it? Jul 19 10:55:27 stygia: and as i mentioned, perl-modules recommends them all Jul 19 11:01:38 TonyHo: it is - first it clones it under downloads/git2/ and then it creates a tarball under downloads called git2_git.server.name.path.to.repo.tar.gz Jul 19 11:19:53 sveinse: ah cool. Is it meant for controlling some sort of machinerie or surgery equipment? Jul 19 11:21:03 fenrig: It for training medical personel in respect of CPR and other trauma. It's not a medical device, its a consumer device, but used by medical personel. Jul 19 11:22:15 sveinse: nice, we do more industrial appliances. Like for instance controllers for industrial washmachines Jul 19 11:22:35 fenrig: Cool Jul 19 11:43:27 cristianiorga: any luck with the MBR? Jul 19 11:48:50 anybody here have experience with Python on their images? Jul 19 12:03:05 RichBayliss: I have used Python a few times in image Jul 19 12:08:27 uhm how do I include gstreamer with codecs? Jul 19 12:08:39 I already tried packagegroup-fsl-gstreamer Jul 19 12:09:03 and gst-plugins-good gst-plugins-bad gst-plugins-ugly Jul 19 12:10:15 ah yes fsl is freescale -.- Jul 19 12:18:04 hhhmm Jul 19 12:18:08 cristianiorga: I was able to boot an image with generated disk signature in VMware Player that I converted with qemu-img from hdddirect to vmdk. I will try creating a build appliance image to try to reproduce the issue you had. Jul 19 12:18:10 :o there are no packagegroups for gstreamer? Jul 19 12:18:28 cristianiorga: if you could provide the disk signature hex id that failed, it would be useful Jul 19 12:24:25 I can't even install ffmpeg -.- Jul 19 12:24:36 or do I have to adress it using another name? Jul 19 12:29:38 fenrig: is it ffmpeg separately that you are looking for or gst-ffmpeg? Jul 19 12:30:35 bluelightning: as much codecs as I can include actually nothing specific Jul 19 12:30:50 bluelightning: including gstreamer-ffmpeg Jul 19 12:32:33 fenrig: there is a gst-ffmpeg recipe and gst-plugins-* recipes Jul 19 12:32:53 bluelightning: put it in image_install Jul 19 12:33:00 bluelightning: or image_features? Jul 19 12:33:00 fenrig: and the gst-plugins-* recipes all create a gst-plugins-xyz-meta package which pulls in all of the submodules Jul 19 12:33:42 bluelightning: it's image_features, right? Jul 19 12:34:38 fenrig: IMAGE_INSTALL Jul 19 12:35:55 bluelightning: i get an error about an unbuildable dependency chain Jul 19 12:36:08 bluelightning: unbuildable dependency chain was: ['edna-image-minimal', 'ffmpeg'] Jul 19 12:36:25 bluelightning: and 'edna-image-minimal' is my custom image -.- Jul 19 12:36:41 bluelightning: so strange I can even find the recipes for it Jul 19 12:36:57 fenrig: what is the error before that Jul 19 12:36:58 ? Jul 19 12:37:23 "nothing provides 'ffmpeg' Jul 19 12:39:45 fenrig: that means that no such recipe exists Jul 19 12:40:02 or rather nothing provides a package with that name Jul 19 12:40:39 bluelightning: okay but I do think I have the package :/ Jul 19 12:40:49 fenrig: what makes you think that? Jul 19 12:40:53 bluelightning: well recipe :/ Jul 19 12:41:09 bluelightning: I'm nog doing a find on my dir for ffmpeg Jul 19 12:41:12 *now Jul 19 12:43:24 AFAIK, there is gst-ffmpeg in OE-Core/Poky; there are some ffmpeg standalone packages kicking around but meta-oe provides libav as a replacement (and in fact we want to pull that into the core - see bug 4748) Jul 19 12:43:26 Bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=4748 enhancement, Medium, 1.5, paul.eggleton, NEW , Add libav and gst-libav to OE-Core Jul 19 12:43:44 er, ffmpeg standalone recipes I meant Jul 19 12:44:03 bluelightning: so that means it should build? Jul 19 12:44:13 fenrig: which should? Jul 19 12:44:24 bluelightning: ffmpeg gst-ffmpeg? Jul 19 12:44:34 gst-ffmpeg should yes Jul 19 12:45:56 bluelightning: same story with gst-ffmpeg Jul 19 12:46:15 and I have "/meta/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bb" Jul 19 12:46:17 fenrig: could you please pastebin the full error log, thanks Jul 19 12:46:20 so I think it's quite odd Jul 19 12:46:42 forgot to prepend the . XD Jul 19 12:46:51 yes I will :) Jul 19 12:48:00 bluelightning: woops, I forgot something :o Jul 19 12:48:10 bluelightning: there is an error about the restricted license Jul 19 12:48:30 bluelightning: ERROR: gst-ffmpeg was skipped: because it has a restricted license not whitelisted in LICENSE_FLAGS_WHITELIST Jul 19 12:48:41 fenrig: ah right, I figured that might be the case Jul 19 12:49:03 fenrig: add LICENSE_FLAGS_WHITELIST = "commercial" in your local.conf Jul 19 12:49:08 bluelightning: sorry -.- Jul 19 12:49:22 fenrig: on the understanding that you need to check yourself if you ever use this in a commercial product whether you can legally do so ;) Jul 19 12:49:38 oh okay, will add that note Jul 19 12:58:18 bluelightning: though we don't produce end products, we just produce products for use in end products of clients Jul 19 12:59:11 fenrig: sure... in which case you'd just pass that understanding of requirement onto them I guess Jul 19 12:59:31 bluelightning: yes indeed Jul 19 13:00:37 it's just a prompt to act as a reminder; it's the user's responsibility to actually take care of the issue if it is an issue Jul 19 13:00:59 (well, user meaning the one developing the product) Jul 19 13:01:22 bluelightning: they actually hired me because more and more clients started requesting sexier UI's and stuff, they are even willing to pay a lot more for it Jul 19 13:01:46 bluelightning: I thought so, good way of fixing that problem Jul 19 13:04:27 bluelightning: that certainly fixed the issue, thank you Jul 19 13:16:14 If I were to backpatch the patch set at the following URL (https://codereview.appspot.com/5461043) to gcc 4.8.1 how could I confirm that this is the final version of the patchset, i.e., the one eventually applied to development version of gcc 4.9.0? Jul 19 13:23:49 cristianiorga: ping Jul 19 13:23:51 mulhern: better ask Khem when he's around Jul 19 13:25:57 ant_work: OK. Anyhow, I just found a more recent patch set. Jul 19 13:27:16 is anyone else getting "Missing operating system" trying to boot a generated build appliance image in vmware player from master 3dee534f1e25109e0bdb681de0746c336f4b8840 or later? https://bugzilla.yoctoproject.org/show_bug.cgi?id=4859 Jul 19 13:27:17 Bug 4859: major, High, 1.5 M3, cristian.iorga, IN PROGRESS DESIGN , Build Appliance does not boot in vmWare Player Jul 19 13:33:11 Net147: did you try to reproduce it on any recent poky? Jul 19 13:33:44 cristianiorga: I am using c6b09377d47d1a0a0fb6a71cf0e93482d2282867 Jul 19 13:33:56 Net147: I have added all the details in YB4859 Jul 19 13:35:25 cristianiorga: waiting for build appliance image to finish generating. I have tested using the build appliance vmx, vmxf files and an .hdddirect image generated with the patch that I converted using qemu-img to vmdk using same steps as the vmdk class Jul 19 13:35:38 cristianiorga: boots fine for that Jul 19 13:37:04 cristianiorga: do you have an .hdddirect image that corresponds to the build appliance? Jul 19 13:49:11 I noticed that ubuntu contains a phonon-backend-gstreamer Jul 19 13:50:10 and because my Qt app is outputting warnings about "WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded " Jul 19 13:51:09 So I think I'm still missing something, but I didn't work trying to add phonon-backend-gstreamer to image_install Jul 19 13:54:29 I think qt4-plugin-phonon-backend-gstreamer fixed it Jul 19 14:04:48 okay it fixed the error, but now the backend can't initialize because I don't seem to have the base GStreamer plugins installed, when they are clearly in the image_install part Jul 19 14:04:50 :o Jul 19 14:10:09 Net147: yes Jul 19 14:10:37 Net147: but it would be hard to send it to you Jul 19 14:21:04 cristianiorga: if you copy the .hdddirect image to another filename and run qemu-system-i386 copy.hdddirect, does syslinux boot? Jul 19 14:53:53 ndec: are you around? Jul 19 15:16:57 bluelightning: yes. Jul 19 15:17:50 ndec: I'm finally looking at http://lists.openembedded.org/pipermail/openembedded-core/2013-June/080299.html Jul 19 15:18:21 ndec: it looks to me that a patch has been removed that shouldn't be for the backport, could you double check that? Jul 19 15:18:39 (apologies for the delay on this) Jul 19 15:19:19 bluelightning: what do you mean by removed? Jul 19 15:21:17 ok. i think i see. but i don't remember all the details, right now. is that ok if i look into this on Mon? i am about to leave now, and that will take me some time to (re)think through this ;-) Jul 19 15:21:38 ndec: sure, that would be fine Jul 19 15:22:00 iirc, the new patch is a replacement for the old one which was broken... but i can't certify that now. Jul 19 15:22:29 OK; the comment just sounded like it was appropriate to remove only because of the uprev to 9.1.3 but if it's a replacement then that would be OK (but we'd want to clarify the commit msg I think) Jul 19 15:23:32 bluelightning: i will look into that Mon morning, and ping you back. Jul 19 15:23:53 ndec: thanks Jul 19 17:02:18 Hi, I'm building my own image based upon image-minimal and I'd like to remove dbus and avahi completely. What would be the best way to do it? DISTRO_FEATURES don't seem to provide necessary framework. Jul 19 17:04:20 check for dependencies. something is likely depending on one or both of those Jul 19 17:04:25 bitbake -g core-image-minimal may be informative Jul 19 17:04:34 see also bitbake -u depexp -g core-image-minimal Jul 19 17:05:02 Ok ... then I have another question. How the hell render the resulting .dot into something small enough to be able to read it :) Jul 19 17:05:17 (Last time I tried this the graph was complete mess and scaled down to about 0.05) Jul 19 17:06:04 Ah! depexp! Jul 19 17:06:08 kergoth: Thanks alot! Jul 19 17:08:23 np Jul 19 17:08:28 Nice, nice. And now if I identify the packages, how is the best way to remove them? After a day of tracking (and two weeks of heavy duty with yocto) I didn't find any other way than to list all the packages that are gonna be installed into image, remove any packagegroups and manually list only those packages I need. Jul 19 17:08:59 there's no magic way. if somethign depends on something else, it does so for a reason. forcing that to not be included would just make the thing that depend son it not function correctly Jul 19 17:09:17 you'd need to inspect the htings which depend on it and check why. see if it obeys *_FEATURES to let you control the dependency Jul 19 17:11:07 That makes sense... I'm going to actually traverse at least one dependency path including .bb files before asking something stupid. Jul 19 17:11:10 Thank you again. Jul 19 17:13:07 could be that we need to add DISTRO_FEATURES for these (although "zeroconf" should control the avahi dependencies, a patch was just sent to do that for pulseaudio I think) Jul 19 17:13:37 bbl Jul 19 18:20:07 Happy Friday everybody! I'd like to NOT use busybox and use the proper tools. Any pointers? Jul 19 18:31:09 Hi, Any solution for github.com/raspberrypi/firmware.git checkout issue Jul 19 19:12:36 Hi! Jul 19 19:12:48 Got some new firmware from LG today. Jul 19 19:13:12 As it seems I have no bootloader-prompt when breaking boot with ESC. Jul 19 20:52:21 Regarding licensing, I'm packaging linphone which has an optional G729 codec "bcg729". This codec is GPLv2 but requires a patent license for use in a product, I suspect I should make a user aware of this before attempting to include binaries from such a recipe in an image? If so, how? Jul 19 20:53:12 LICENSE_FLAGS = "non-commercial" is likely what you want Jul 19 20:56:16 kergoth, ahh look at that. Nice, will take a closer look and add that to the recipe Jul 19 21:08:03 kergoth: surely it's "commercial" ? at least it's the same situation for ffmpeg & co... Jul 19 21:22:36 bluelightning, that was my conclusion as well from reading the relevant chapter in the manual. So I'll add that to the recipe Jul 19 22:04:10 bluelightning: indeed, yes, oops Jul 19 23:27:48 Gooood afternoon everybody, best strategy to replace busybox with full versions of tools? Jul 19 23:27:51 proper-tools? **** ENDING LOGGING AT Sat Jul 20 02:59:57 2013