**** BEGIN LOGGING AT Sun Oct 25 02:59:59 2015 Oct 25 10:37:20 is e.g. bb.utils.contains() considered a stable API? there's a bunch of undocumented but commonly-used stuff in bb it seems. **** BEGIN LOGGING AT Sun Oct 25 14:10:29 2015 Oct 25 15:53:08 Does anybody use the eclipse yocto plugin? I have a problem making it recognize std headers, I added their directory to the project but still the indexer refuses to take them Oct 25 16:02:23 Hi. I'm using latest fido branch and get some problems when trying to use: IMAGE_INSTALL_append " pkgname" within local.conf when building core-image-minimal. I'm quite sure I have used this methid in older releases from local.conf and the documentation describes using this method. Anyone with ideas if this is expected to work or not? It works fine when using: IMAGE_INSTALL_append_pn-core-image-minimal = " pkgname" instead.. But since the documentation says o Oct 25 16:20:08 zerus: your message was cut off after "documentation says o[...]" Oct 25 16:37:00 hey. what is the most recent cmake for yocto master? Oct 25 16:37:33 on daisy it is 2.8.12.2 and i need something like cmake 3.x so i have to backport it and it would be cool to have some pointers Oct 25 16:38:02 i guess when i replace the current cmake with 3.x some other builds won't work anymore (requiring 2.x cmake) Oct 25 16:40:08 qknight: It's 3.3.1 on master Oct 25 16:40:15 qknight: http://layers.openembedded.org/layerindex/recipe/5305/ Oct 25 16:40:38 oh that is a cool site! thanks for pointing that out Oct 25 16:40:56 can yocto handle two cmake parallel installations? Oct 25 16:41:00 like SLOTS on gentoo? Oct 25 16:54:39 neverpanic: Ok, thx for pointing that out here it comes again... Oct 25 16:55:02 Hi. I'm using latest fido branch and get some problems when trying to use: IMAGE_INSTALL_append " pkgname" within local.conf Oct 25 16:55:05 when building core-image-minimal. I'm quite sure I have used this methid in older releases from local.conf and the documentation Oct 25 16:55:08 describes using this method. Oct 25 16:55:23 Anyone with ideas if this is expected to work or not? It works fine when using: IMAGE_INSTALL_append_pn-core-image-minimal = " pkgname" instead.. But since the documentation says othwerwise I'm curious.. Oct 25 17:26:37 _append_pkgname has never worked, so no idea what documentation you're reading, but that has never been supported. pn- is how you manipulate a recipe variable from the configuration metadata Oct 25 17:29:04 kergoth: Thx for this info. Then I know that this is a expected behaviour and that the method I got it working with is the recommended one. Oct 25 17:29:45 it's not just a matter of recommendations, it's a matter of what works and what doesn't Oct 25 17:33:08 kergoth: Sorry a bad choice of words, since like you say it doesn't even work with INSTALL_append in that context. Oct 25 18:00:25 Hi, I've built an image using the yocto project. But now I want to change the machine I built it for. But no matter what I put in my local.conf it keeps building it for the previous target which is: genericx86-64. Can anybody tell me what I'm doing wrong? Oct 25 18:01:37 Do I need to remove previously built images to make it work!? Oct 25 18:15:52 maybe i could add the cmake 3.x as mycmake package and then depend on that Oct 25 18:16:06 so i have two differnet cmake versions and i don't have to touch the cmake which is used to build parts of the image itself Oct 25 18:16:20 would that be an possible way to add a 3.x cmake into a 2.x cmake system? Oct 25 18:16:32 i actually just require cmake 3.x for my own project Oct 25 19:43:56 can somebody help me? Oct 25 20:04:43 well, maybe, ask your question. Oct 25 20:14:11 I've built an image using the yocto project. But now I want to change the machine I built it for. But no matter what I put in my local.conf it keeps building it for the previous target which is: genericx86-64. Can anybody tell me what I'm doing wrong? Oct 25 20:14:54 I'm actual using: MACHINE ?= "intel-corei7-64" in my local.conf Oct 25 20:15:33 but when I build bitbake says: Build Configuration: Oct 25 20:15:36 BB_VERSION = "1.26.0" Oct 25 20:15:38 BUILD_SYS = "x86_64-linux" Oct 25 20:15:40 NATIVELSBSTRING = "Ubuntu-12.04" Oct 25 20:15:42 TARGET_SYS = "x86_64-poky-linux" Oct 25 20:15:44 MACHINE = "genericx86-64" Oct 25 20:15:46 DISTRO = "poky" Oct 25 20:15:48 DISTRO_VERSION = "1.8.1" Oct 25 20:15:50 TUNE_FEATURES = "m64 core2" Oct 25 20:15:52 TARGET_FPU = "" Oct 25 20:16:31 why does it say MACHINE="genericx86-64"? Oct 25 20:16:38 rename the config file and start again? Oct 25 20:16:49 rename? Oct 25 20:16:57 local.conf1 Oct 25 20:17:03 or local1.conf Oct 25 20:17:09 keep it around. Oct 25 20:17:15 okay Oct 25 20:17:51 that's not going to help Oct 25 20:17:56 I am NOT a yocto expert so I bow out now. But that's a general technique for software - renaming the file or folder. Oct 25 20:18:21 the reason it's not working is you are using ?= after a previous assignment... ?= only sets a variable's value if it hasn't already been set Oct 25 20:18:48 either comment out the previous line setting it with ?=, or change it to = and all will be well Oct 25 20:19:16 jozzan: ^ Oct 25 20:19:37 I already tried checking out a clean version of yocto but still no success Oct 25 20:20:00 tried that already, too. Oct 25 20:20:33 The thing with the = sign Oct 25 20:21:19 also cant see why or where the machine variable should have been set!? Oct 25 20:30:38 jozzan: bitbake -e should be able to tell you Oct 25 21:50:46 okay bitbake -e gives lots of output yet I'm not quite sure what the contents are Oct 25 21:57:18 searched the output for MACHINE declerations but I can't even find my MACHINE = "intel-corei7-64" from my local.conf is that typical ? **** ENDING LOGGING AT Mon Oct 26 02:59:58 2015