**** BEGIN LOGGING AT Tue Mar 25 02:59:58 2014 Mar 25 08:16:10 Hello, Can anyone help me build qt environment on yocto build core-image-sato? Mar 25 08:17:08 I want to run qt application on yocto build which actually runs on a atom-arch machine Mar 25 08:17:25 shadow_ShangHai: which version of Qt? for Qt5 you can use meta-qt5 which is hosted on github Mar 25 08:17:53 Can you point out some steps to do it? Mar 25 08:18:03 I am still new to yocto project Mar 25 08:18:33 qt5 is an priority option Mar 25 08:20:02 shadow_ShangHai: https://github.com/meta-qt5/meta-qt5 Mar 25 08:20:11 shadow_ShangHai: you clone it and add it to your bblayers.conf Mar 25 08:20:22 shadow_ShangHai: then you can do things like bitbake qtbase Mar 25 08:22:08 What result can I get by doing bitbake qtbase Mar 25 08:23:19 shadow_ShangHai: You will build qtbase. To end in your image it needs to be installed. Either by you modifying an image/packagegroup Mar 25 08:25:05 how can I install it? Mar 25 08:26:42 shadow_ShangHai: is that a university project? Maybe look at how core-image-sato works and then figure out how to add more packages to the images? Mar 25 08:27:45 Ok, I've read the reference mannual, but didn't quite understand Mar 25 08:28:20 yes, I am a student working on it recently. Mar 25 08:28:54 shadow_ShangHai: then read and study the recipes. There is nothing like learning by yourself Mar 25 08:30:17 Thanks. I will dig the answer out. Mar 25 09:14:31 good morning Mar 25 10:03:01 hello everyone, why is the '\n' put in files like 'meta-yocto/conf/distro/poky.conf' when refering to things like SANITY_TESTED_DISTROS or MIRRORS? Mar 25 13:06:37 Moin Mar 25 13:17:37 is it possible to define a defconfig inside ${S} if I use kernel-yocto? Mar 25 13:29:41 looks like do_kernel_configme_prepend isn't executed Mar 25 13:56:42 Hi. I am trying to build an image with the kernel 3.14 on the nitrogen6x board. For this I editet the local.conf and added PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev". But the kernel version was still 3.0.35. Can someone point me in a direction? Mar 25 14:03:22 anda, maybe you need to check if PREFERRED_VERSION is set correctly Mar 25 14:03:29 see u later Mar 25 14:16:18 fsdun: linux-yocto-dev won't run on nitrogen6x Mar 25 14:37:06 alexVaduva: \n is required as the separator for things like MIRRORS because spaces are allowed, and required, within a single mirror entry, so using whitespace as an entry separator wouldn't make any sense. newline makes sense, and is a character we know won't be used within a mirror entry Mar 25 15:00:16 YPTM Jefro is here Mar 25 15:00:31 YPTM: Bruce is on the call.' Mar 25 15:00:38 Dial-in number: 1.972.995.7777 US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x42001078# Mar 25 15:00:43 YPTM: Dial-in number: 1.972.995.7777 US Toll Free number: 1.877.561.6828 BlackBerry users, click this link to join your conference as a participant: 1.972.995.7777x42001078# Mar 25 15:00:48 YPTM: Valentin Cobelea is in on the call Mar 25 15:01:01 YPTM: Beth Flanagan is on Mar 25 15:01:08 YPTM: Ross on Mar 25 15:01:11 YPTM: Jeff Polk is on Mar 25 15:01:18 YPTM: Richard is on Mar 25 15:01:19 YPTM: Tom Z on Mar 25 15:01:25 YPTM: Stephen is on. :) Mar 25 15:01:50 YPTM: hi all, michael on Mar 25 15:03:59 YPTM: Michael is on the call. Mar 25 15:04:10 YPTM: Belen is on the call Mar 25 15:06:14 YPTM: only on chat, no audio Mar 25 15:06:23 alex d joined Mar 25 15:14:00 YPTM: Mark is here now Mar 25 15:14:18 YPTM nitin joined the call Mar 25 15:14:35 link to those performance metrics? Mar 25 15:14:49 s/metrics/tuning guide/ Mar 25 15:14:56 michael_e_brown: its on the wiki Mar 25 15:15:19 michael_e_brown, The general tips at https://wiki.yoctoproject.org/wiki/Build_Performance are a good start. Mar 25 15:16:27 hi there. i'm trying to build meta-qt/qtwebkit 5.2.1 which requires "ruby-native" - which project/layer provides that? Mar 25 15:20:37 guys, I have problem with kernel build (1.5.1 = dora). kernel-modules ipk does not contain any modules for some reason. Any clues what could have gone wrong? Mar 25 15:20:44 YPTM: hello guys! Mar 25 15:20:54 or is it provided by meta-openembedded/recipes-devtools/ruby and only the dependency name "ruby-native" can't be resolved due to my mix of */dora but meta-qt/master Mar 25 15:22:41 Xz: kernel-modules ipk just depends on all the individual kernel-module-* ipks, i doubt it was ever expected to contain any modules itself Mar 25 15:24:35 kergoth: my problem is that during core-image... rootfs doing - opkg complains about 'opkg_install_cmd: Cannot install package kernel-module-stmmac' and others Mar 25 15:25:21 no idea. your kernel will only emit the modules which are enabled its in config. make your defconfig emits the modules your machine requires to boot Mar 25 15:26:53 hi Mar 25 15:27:10 kergoth: well, my defconfig contains all modules required to boot :( Mar 25 15:27:39 kergoth: it used to work well on 1.4 - now I bumped to 1.5.1 and that problem occured Mar 25 15:28:15 I try to use "bootimg" with core-image-minimal. So I added it to USER_CLASSES in conf/local.conf. Now I get the error that global name 'oe' is not defined when expanding EFI_CLASS Mar 25 15:28:32 ok just forget my blafoo, pebkac Mar 25 15:29:33 khem: Mar 25 15:29:36 qemumips64 login: root Mar 25 15:29:36 root@qemumips64:~# uname -a Mar 25 15:29:36 Linux qemumips64 3.14.0-rc8-yocto-standard #1 PREEMPT Tue Mar 25 09:47:10 EDT 2014 mips64 GNU/Linux Mar 25 16:03:33 ouch.. meta-qt5/qtwebkit_5.2.1 depends on qtlocation which depends on qt3d which is only a preview Mar 25 16:12:04 linux dependency hell Mar 25 16:42:26 I'm giving up. I went into kernel workdir and apparently there are no .ko files - so no modules were built Mar 25 16:45:34 which would mean Yocto took other config file than mine? Mar 25 16:57:55 ok Yocto is using different config than mine, proved. Mar 25 16:58:08 Now it looks like Yocto is looking for a file explicitly called 'defconfig' Mar 25 16:58:33 Xz, this sounds like kernel issues Mar 25 16:58:41 Xz, something I can help with? Mar 25 16:58:50 (only saw your last to lines) Mar 25 17:00:33 dvhart: well, yeah Mar 25 17:00:53 dvhart: I just bumped the layer from 1.4 to 1.5.1 and top level problem is: "opkg_install_cmd: Cannot install package kernel-module-stmmac" Mar 25 17:01:14 dvhart: then I started digging and I figured out that kernel builder took different config file than mine Mar 25 17:01:27 and there are no modules at all Mar 25 17:03:12 ok, some context: MACHINE? kernel recipe? Mar 25 17:04:14 dvhart: on top of that log do_kernel_configcheck says: Mar 25 17:04:16 DEBUG: WARNING: Can't find any BSP hardware or required configuration fragments. Mar 25 17:04:16 WARNING: Looked at .meta/cfg/standard/quark/hdw_frags.txt and .meta/cfg/standard/quark/required_frags.txt in directory: .meta/cfg/standard/quark Mar 25 17:04:41 dvhart: the .meta looks suspicious as well :| Mar 25 17:05:41 Right, so it built a dummy one for you as it couldn't find a MACHINE KTYPE match for your configuration Mar 25 17:05:50 which is surely not going to have what you want Mar 25 17:06:03 again, MACHINE and kernel-recipe? is this galileo stuff? Mar 25 17:06:14 dvhart: yeah, let me put it to pastebin Mar 25 17:10:14 http://pastebin.com/7WHhH36k Mar 25 17:11:41 dvhart: kernel recipe is recipes-kernel/linux/linux-yocto-quark_3.8.bb Mar 25 17:12:04 dvhart: it's basically copy&paste from iotdevkit with clanton->quark rename Mar 25 17:14:05 OK, did you change the name of the KMACHINE also? Mar 25 17:14:25 if so, did you also add the quark-standard.scc in the meta data? Mar 25 17:15:02 I see, yes, you did change KMACHINE Mar 25 17:15:14 so did you also provide the necessary meta-data to support the new KMACHINE? Mar 25 17:15:58 if not, why did you change KMACHINE - what were you trying to accomplish? Mar 25 17:16:15 ah... sorry sorry, too hasty in my review of your paste bin Mar 25 17:16:56 can you also paste your linux-yocto-quark please? Mar 25 17:43:16 dvhart: kernel recipe: inherit kernel Mar 25 17:43:17 require recipes-kernel/linux/linux-yocto.inc Mar 25 17:43:17 # Override SRC_URI in a bbappend file to point at a different source Mar 25 17:43:17 # tree if you do not want to build from Linus' tree. Mar 25 17:43:17 SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.8.y" Mar 25 17:43:19 SRC_URI += "file://quark.cfg" Mar 25 17:43:22 SRC_URI += "file://quark-standard.scc" Mar 25 17:43:24 LINUX_VERSION ?= "3.8" Mar 25 17:43:27 LINUX_VERSION_EXTENSION ?= "-clanton" Mar 25 17:43:29 # Override SRCREV to point to a different commit in a bbappend file to Mar 25 17:43:32 # build a different release of the Linux kernel. Mar 25 17:43:34 SRCREV = "531ec28f9f26f78797124b9efcf2138b89794a1e" Mar 25 17:43:37 SRCREV_machine_quark = "531ec28f9f26f78797124b9efcf2138b89794a1e" Mar 25 17:43:39 PR = "r0" Mar 25 17:43:42 PV = "${LINUX_VERSION}" Mar 25 17:43:44 # Override COMPATIBLE_MACHINE to include your machine in a bbappend Mar 25 17:43:47 # file. Leaving it empty here ensures an early explicit build failure. Mar 25 17:43:49 COMPATIBLE_MACHINE = "quark" Mar 25 17:43:52 RDEPENDS_kernel-base="" Mar 25 17:43:54 SRC_URI += "file://0001-tty-don-t-deadlock-while-flushing-workqueue-quark.patch" Mar 25 17:43:57 SRC_URI += "file://0002-driver-core-constify-data-for-class_find_devic-quark.patch" Mar 25 17:44:00 SRC_URI += "file://0003-TTY-mark-tty_get_device-call-with-the-proper-c-quark.patch" Mar 25 17:44:03 SRC_URI += "file://0004-pwm-Add-sysfs-interface-quark.patch" Mar 25 17:44:05 SRC_URI += "file://0005-drivers-pwm-sysfs.c-add-export.h-RTC-50404-quark.patch" Mar 25 17:44:08 SRC_URI += "file://0006-core-Quark-patch-quark.patch" Mar 25 17:44:10 SRC_URI += "file://0007-Quark-Platform-Code-quark.patch" Mar 25 17:44:13 SRC_URI += "file://0008-Quark-UART-quark.patch" Mar 25 17:44:15 SRC_URI += "file://0009-EFI-capsule-update-quark.patch" Mar 25 17:44:18 SRC_URI += "file://0010-Quark-SDIO-host-controller-quark.patch" Mar 25 17:44:20 SRC_URI += "file://0011-Quark-USB-host-quark.patch" Mar 25 17:44:23 SRC_URI += "file://0012-USB-gadget-serial-quark.patch" Mar 25 17:44:26 SRC_URI += "file://0013-Quark-stmmac-Ethernet-quark.patch" Mar 25 17:44:28 SRC_URI += "file://0014-Quark-GPIO-2-2-quark.patch" Mar 25 17:44:30 SRC_URI += "file://0015-Quark-GPIO-1-2-quark.patch" Mar 25 17:44:33 SRC_URI += "file://0016-Quark-GIP-Cypress-I-O-expander-quark.patch" Mar 25 17:44:36 SRC_URI += "file://0017-Quark-I2C-quark.patch" Mar 25 17:44:38 SRC_URI += "file://0018-Quark-sensors-quark.patch" Mar 25 17:44:41 SRC_URI += "file://0019-Quark-SC-SPI-quark.patch" Mar 25 17:44:43 SRC_URI += "file://0020-Quark-IIO-quark.patch" Mar 25 17:44:44 dude, what the hell Mar 25 17:44:46 SRC_URI += "file://0021-Quark-SPI-flash-quark.patch" Mar 25 17:44:48 damn :| Mar 25 17:44:51 http://pastebin.com/pcgFqkF2 Mar 25 17:44:53 :) Mar 25 17:45:40 I got copy&paste wrong Mar 25 17:46:06 it's always either middle click or ctrl-c/ctrl-v Mar 25 17:46:26 Xz: http://www.nongnu.org/autocutsel/ Mar 25 17:46:36 syncs the multiple X clipboards Mar 25 17:46:38 much less painful Mar 25 17:47:02 multiple clipboards is cool! Mar 25 17:47:09 * kergoth twitches Mar 25 17:47:23 kergoth: nice stuff Mar 25 17:49:26 gah, now this build dir is rebuilding everything. the only difference between this and the other build dir where it's pulling its sstate from, is the differing TOPDIR/TMPDIR Mar 25 17:49:30 * kergoth growls Mar 25 17:53:01 dvhart: what do you mean by providing some special meta data for KMACHINE? Mar 25 17:53:29 dvhart: I had to change the name, since 'clanton' is codename, quark is product name Mar 25 17:54:22 Xz, hrm... you may need KMACHINE_quark="quark" defined in linux-yocto-quark Mar 25 17:54:32 although I thought it defaulted to that Mar 25 17:55:22 also, your COMPATIBLE_MACHINE should have a machine override: COMPATIBLE_MACHINE_quark="quark" Mar 25 17:56:25 try the KMACHINE thing and let me know if you still get the missing meta data errors Mar 25 17:56:43 Xz, re the meta data - you are providing that with the quark-standard.scc Mar 25 17:57:09 if that fails - please send email to the linux-yocto mailing list with these details provided here so zeddii and I can work with you on it there Mar 25 17:57:37 It's possible you've hit a bug in the recipe-space kernel meta-data mechanism Mar 25 18:08:48 sigh, not getting sstate reuse between two bulid directories with identical configs and layers (other than SSTATE_DIR/SSTATE_MIRRORS) Mar 25 18:08:50 * kergoth grumbles Mar 25 18:11:46 dvhart: so just adding KMACHINE_quark = "quark" does not fix anything Mar 25 18:12:30 dvhart: the most interesting stuff is that I took it from iotdevkit and apparently iotdevkit works perfectly fine :| Mar 25 18:14:02 but you also bumped the base poky/oe-core version too right? Mar 25 18:14:19 that changes the kernel tooling, which I suspect is what you are hitting. Mar 25 18:14:34 Xz, ^ Mar 25 18:19:30 dvhart: I bumped: meta-oe/, meta-intel/ and poky/ Mar 25 18:19:36 dvhart: three things in my bblyers.conf Mar 25 18:19:51 meta-oe is just 'dora' branch, the rest is 1.5.1 tag Mar 25 18:20:05 what was working before? was it 1.3 ? Mar 25 18:20:10 dvhart: 1.4 Mar 25 18:20:20 dvhart: 1.4.1 actually Mar 25 18:20:59 dvhart: but again - I took kernel recipe from iotdevkit which normally works on 1.5 Mar 25 18:21:10 OK, I suspect you hit a change in the kernel tooling or the kernel recipe - let's take this to the linux-yocto list. We need to get this fixed and ensure the documentation reflects the proper usage. Mar 25 18:21:20 Xz, ah OK - good datapoint Mar 25 18:21:54 is your layer available somewhere that zeddii and I could attempt to build it? Mar 25 18:22:02 if so, please include that in your linux-yocto email Mar 25 18:22:07 * dvhart handles SIGFOOD Mar 25 18:46:20 EFI = "${@base_contains("MACHINE_FEATURES", "efi", "1", "0", d)}" runs without any problems, EFI_CLASS = "${@base_contains("MACHINE_FEATURES", "efi", "grub-efi", "", d)}" complains about namerror for "oe" Mar 25 18:46:24 anyone knows why? Mar 25 19:15:58 volker-, what is the specific error? Mar 25 19:21:58 dvhart: ExpansionError: Failure expanding variable EFI_CLASS, expression was ${@base_contains("MACHINE_FEATURES", "efi", "grub Mar 25 19:22:02 -efi", "", d)} which triggered exception NameError: global name 'oe' is not defined Mar 25 19:22:06 ERROR: Unable to parse bootimg: Failure expanding variable EFI_CLASS, expression was ${@base_contains("MACHINE_FEATURE Mar 25 19:22:09 S", "efi", "grub-efi", "", d)} which triggered exception NameError: global name 'oe' is not defined Mar 25 19:22:28 I think actually the error happens on the "inherit ${EFI_CLASS}" Mar 25 19:22:39 dora git, meta/classes/bootimg.bbclass Mar 25 19:27:40 volker, sounds like it is trying to inherit "" - does your MACHINE_FEATURES contain efi? Mar 25 19:30:57 voller, I wonder if it needs some inline python to set it to grub-efi it is empty Mar 25 19:31:08 volker even ^ Mar 25 19:39:24 dvhart: no, MACHINE_FEATURES is not defined Mar 25 19:40:42 dvhart: def base_contains(variable, checkvalues, truevalue, falsevalue, d) (meta/classes/utils.bbclass), so unless the variable-naming is screwed, it should be "" Mar 25 19:41:10 dvhart: if MACHINE_FEATURES cointains efi, it will be grub-efi, else it will be "" Mar 25 19:42:17 I don't know how to fix it, I am confused enough that just trying to build an ISO fails with dora Mar 25 19:42:28 which machine? Mar 25 19:42:52 genericx86-64 + qemux86-64 Mar 25 19:43:41 OK, so MACHINE_FEATURES should be defined, it may not contain efi, but it should be defined - is that what you meant? Mar 25 19:44:11 MACHINE_FEATURES = "" in my local.conf does not fix this Mar 25 19:44:33 dvhart: take the default local.conf and add bootimg to USER_CLASSES Mar 25 19:44:53 MACHINE_FEATURES is defined in the machine config Mar 25 19:45:05 MACHINE_FEATURES="alsa bluetooth usbgadget screen x86 rtc" Mar 25 19:45:10 that's the default for that machine Mar 25 19:45:17 now you said dora Mar 25 19:45:29 hrm Mar 25 19:45:42 dvhart: if I clone poky and use the dora branch and do this modification it fails. Mar 25 19:46:00 I'm not familiar with USER_CLASSES Mar 25 19:46:06 what are you trying to accomplish? Mar 25 19:46:16 dvhart: gettign an ISO as output Mar 25 19:46:34 Ah, isn't that just a matter of disabling the NOISO setting? Mar 25 19:46:36 * dvhart tries... Mar 25 19:48:26 what is NOISO set to in your environment? Mar 25 19:48:37 dvhart: not set by me Mar 25 19:48:56 not what I asked :-) Mar 25 19:49:05 bitbake core-image-minimal | grep NOISO= Mar 25 19:49:10 bitbake core-image-minimal -e | grep NOISO= Mar 25 19:49:16 the second one Mar 25 19:49:28 dvhart: no return Mar 25 19:49:30 this will tell you what value of the variable bitbake is using for the build Mar 25 19:49:47 you will need to disable your USER_CLASSES setting first as that is breaking parsing before we can print the environment Mar 25 19:51:48 dvhart: I start from the basic example distribution and make one modification Mar 25 19:51:56 dvhart: you can reproduce it by running git clone -b dora git://git.yoctoproject.org/poky dora;cd dora;source oe-init-build-env; sed -i 's/^USER_CLASSES .*/USER_CLASSES ?= "buildstats image-mklibs image-prelink bootimg"/' conf/local.conf; bitbake core-image-minimal Mar 25 19:53:31 Yup, OK, well I have a dozen things cooking at the moment, was just trying to help you out. If you can't get the info, I'd suggest trying with NOISO=0 and see if that gets you what you want. The info requested above would help me determine if that's the right fix, but I'll leave it to you. Mar 25 19:53:49 even when disabling USER_CLASSES by commenting it out in conf/local.conf the bitbake command does not produce a NOISO output Mar 25 19:55:28 dvhart: when I put NOISO=0 into conf/local.conf bitbake prints out an ParseError Mar 25 19:56:08 hem, indeed - digging a moment Mar 25 19:56:40 I believe it needs "" Mar 25 19:56:46 NOISO="0" Mar 25 19:57:16 yeah, that works, running it without bootimg + NOISO="0 Mar 25 19:57:20 yup, that passes, running Mar 25 19:58:42 volker-, there is some coverage of this in the bootimg.bbclass section of the reference manual and NOISO in the glossary: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html Mar 25 19:58:54 it probably isn't as clearly spelled out as it could be Mar 25 19:59:09 suggestions on how to improve the manual are welcome Mar 25 19:59:30 dvhart: thats where I found bootimg.bbclass, but it fails as soon as you but the bootimg into it Mar 25 20:01:10 volker-, where did you get the idea to add booting to the USER_CLASSES ? Mar 25 20:01:27 * dvhart isn't finding that in the manual... Mar 25 20:01:41 dvhart: the default USER_CLASSES is "buildstats image-mklibs image-prelink", same section as bootimg.bbclass Mar 25 20:03:10 volker-, are you referring to chapter 8? Mar 25 20:03:15 dvhart: yes Mar 25 20:03:50 and USER_CLASSES is commented as "Additional image features", I would assume getting an ISO as output is a image feature Mar 25 20:04:00 OK... I guess I'm still not seeing any connection between USER_CLASSES and bootimg.bbclass in there. I'm trying to understand how you made the connection so I can remove it ;-) Mar 25 20:04:10 Ah Mar 25 20:04:14 that I can understand Mar 25 20:04:28 wrong sort of image feature.... but yes, I can see why you would arrive at that Mar 25 20:05:23 booting isn't used in that way Mar 25 20:05:51 dvhart: so where/how do I use it and where can I find more about it to not run into similar issues the next time? Mar 25 20:06:18 booting is automatically parsed and used for live images and iso images Mar 25 20:06:37 it is the IMAGE_FSTYPES that specifies if these will be built Mar 25 20:07:27 dvhart: so I don't need to load classes but define the variables used by the classes? Mar 25 20:07:40 In this case, that's right Mar 25 20:07:54 I've never in >3 years used USER_CLASSES :-) Mar 25 20:08:15 but IMAGE_FSTYPE is part of image.bbclass, and nothing in the reference manual says anithing about ISO Mar 25 20:08:36 I pointed you to two sections about ISO... Mar 25 20:08:36 dvhart: so how should I know when to use what? Mar 25 20:08:46 http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-NOISO Mar 25 20:09:01 I agree there should be something more task specific here Mar 25 20:09:11 wonder if the dev manual is helpful here... Mar 25 20:09:30 dvhart: nothing about ISO in the devmanual. I was reading through it yesterday Mar 25 20:09:51 yeah, you're correct Mar 25 20:09:54 a clear gap Mar 25 20:10:07 we have folks that are dedicated to docs Mar 25 20:10:27 I would suggest opening a bug describing what you were trying to do and how the docs organization and content failed you Mar 25 20:11:01 Any suggestions on how you might do it differently would be welcome too Mar 25 20:11:12 so how do I know if I can set a variable and it will automatically find the class? Mar 25 20:11:17 sure, I can open a ticket Mar 25 20:11:39 volker-, I think you might be focused too much on the class thing Mar 25 20:11:50 variables drive the way things are built by bitbake Mar 25 20:11:51 I am new to yocto and its a painful learning curve right now Mar 25 20:12:10 volker-, heh... you should have tried it 3 years ago before all these docs were around ;-) Mar 25 20:12:27 but yes, there is a lot to learn, and not everything is a clearly spelled out as it could be Mar 25 20:12:45 we have been working hard on improving this over the last few years and continue to do so Mar 25 20:13:36 If you can't find what you want to accomplish in the devmanual or the ref manual (by task), then I suggest asking on the yocto mailing list, or here Mar 25 20:13:46 the mailing list if you don't get a quick response here Mar 25 20:13:59 that's why I asked this twice here ;-) Mar 25 20:14:08 yup, and that's fine Mar 25 20:14:19 but opening the bug is how things improve over time Mar 25 20:14:29 otherwise you are just one person with tribal knowledge Mar 25 20:14:33 one more person Mar 25 20:15:03 what I miss is a more comprehensive walk through Mar 25 20:15:30 Have you been through the various labs and videos we've prepared? Mar 25 20:15:34 sure, I know how to clone and do a basic build, the dev-manual shows me how to create sample recipes, but the world is bigger as that :) Mar 25 20:15:56 nope, I assume documentation is more comprehensiv (and I found more itneresting features there) Mar 25 20:16:11 zeddii: great Mar 25 20:16:37 volker-, you said you wanted a walkthrough - the labs are just that Mar 25 20:17:38 volker-, for example: https://www.yoctoproject.org/tools-resources/training Mar 25 20:19:51 Hi pidge, I am interested in applying to Yocto's OPW internship. I notice that the YP internship page still refers to Spring, are you still looking for proposals concerning documentation for the Autobuilder? Mar 25 20:20:08 there are others I'm not finding - if you send me an email volker- I can forward you the links when our webmaster gets back to me with where they are Mar 25 20:21:29 dvhart: thanks, that would be great. Mar 25 20:21:32 Queeniebee: Yes, please, feel free to email me Mar 25 20:21:54 pidge: great, I will. Thank you. Mar 25 20:22:00 Queeniebee: We close applications on Friday though, so, not much time Mar 25 20:23:32 volker-, your NOISO build still building? Mar 25 20:27:22 dvhart: yes Mar 25 20:27:54 another painpoint to use prebuilds. unclear how to use them (there is documentation how to download them), but I deffer this task for now ;-) Mar 25 20:28:05 s/deffer/defer/ Mar 25 20:30:49 dvhart: do you know in which documentation the operators are defined? Like ?=, ??= and how they are used? Mar 25 20:33:35 volker-, that is in the bitbake manual Mar 25 20:34:20 volker-, poky/bitbake/doc/manual Mar 25 20:34:33 dvhart: thanks Mar 25 20:34:50 yup, definitely a good one to read... every few months Mar 25 20:34:52 :) Mar 25 20:44:19 dvhart: NOISO="0" spit out an iso Mar 25 20:44:22 dvhart: thanks a lot :) Mar 25 20:44:33 you're welcome :-) Mar 25 20:44:42 sorry that was such a painful process Mar 25 20:44:44 please file the bug Mar 25 20:44:51 dvhart: did already :) Mar 25 20:45:01 great Mar 25 20:46:14 iirc we turned off iso by default as very few people used them... Mar 25 20:46:37 rburton, yup - and then never documented clearly how to turn them back on Mar 25 20:46:40 :-) whoops Mar 25 20:48:20 something else, dora (seems to be the reference distribution) can be downloaded as tar.gz (good for build systems) and git. Now there seems to be a diff between the version you download and git. E.g. the downloaded one does not support Ubuntu 13.10, while the git version does. Therefore my understanding of "stable" version / code source is unclear to me. Mar 25 20:51:34 it will just depend on whether or not you are using the exact git tag that matches the tarball Mar 25 20:51:51 HEAD of the dora branch will be ahead of the 1.5 tar ball for example Mar 25 20:52:04 see the tags and match them up with the tar ball you are using Mar 25 20:52:11 (or just use the latest stable from git) Mar 25 20:52:29 ok, my understanding was that dora is the stable name Mar 25 20:52:36 it is Mar 25 20:52:43 stable doesn't mean it doesn't change Mar 25 20:52:53 it means it only gets very carefully selected back ports from the master branch Mar 25 20:53:01 to address important bugs Mar 25 20:53:08 and that in turn feeds into th estimable point releases Mar 25 20:53:13 1.5.1 1.5.2, etc Mar 25 20:53:28 ugh, autocorrect Mar 25 20:53:37 "feeds into the stable point releases" Mar 25 20:57:17 ok, thanks a lot again, dvhart. :) I have to leave now. Mar 25 20:58:54 ;-) Good luck Mar 25 21:00:43 I didn't know I need luck for yocto ;-) Mar 25 21:02:13 pretty sure that's documented too... Mar 25 21:28:54 Hi all Mar 25 21:29:03 I am new to yocto project Mar 25 21:29:49 can any one help me for some link or material for how to write recipe Mar 25 21:30:12 gubadi, see the developers manual Mar 25 21:30:16 because on the website it is not give nice material Mar 25 21:30:46 I suggest starting here: http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html Mar 25 21:31:19 ohk Mar 25 21:31:21 thanks Mar 25 21:31:55 Please raise issues with the website on the yocto list so we can discuss/track/fix them Mar 25 21:32:03 * dvhart isn't thrilled with it himself Mar 25 21:32:18 i have download x-chat, what do i need to enter in network field to get conntectd to this IRC chat Mar 25 21:32:20 ? Mar 25 21:33:24 press "Enter" Mar 25 21:33:48 ah Mar 25 21:33:55 you are connected via webchat Mar 25 21:34:01 yes Mar 25 21:34:04 irc.freenode.net shoudl do it Mar 25 21:34:25 * dvhart signs off for some dev time Mar 25 21:34:29 I thought the question was funny for someones already here :) Mar 25 21:38:36 lol Mar 25 21:38:41 i was thinking same thing Mar 25 21:38:49 but i mentioned for x-chat Mar 25 21:38:57 not for web base Mar 25 21:56:49 i have a recipe for a package and i want to build it Mar 25 21:57:28 i use following variable IMAGE_INSTALL_append /conf/local.conf but it failed with following messages: Nothing RPROVIDES 'packagegroup-iosxe-baseltP' (but /nobackup/dvasadia/ea2/meta-iosxe/recipes-images/iosxe/iosxe-devel-image.bb RDEPENDS on or otherwise requires it) Mar 25 21:57:54 any pointer? Mar 25 21:59:48 no reply Mar 25 21:59:48 wow Mar 25 22:12:10 dv__: either you tried to add a package that doesn't exist, or you missed the needed leading space. IMAGE_INSTALL_append = " foo", not IMAGE_INSTALL_append = "foo" Mar 25 22:22:22 Jefro: I have only recipe file which is .bb and i have put space before package name Mar 26 02:55:03 hi guys Mar 26 02:55:19 can someone explain me the commit message to https://github.com/openembedded/meta-oe/commit/c8aa4b10b2ab341bbcb163d041c44c1a20172ee1 this ? Mar 26 02:55:31 I don't quite understand the reason from the high-quality commit message ;-) Mar 26 02:55:41 * Marex gives JaMa an evil eye ;-) **** ENDING LOGGING AT Wed Mar 26 02:59:59 2014