Re: [yocto] how many meta-toolchain-* targets are there?
toolchain-gmae is exactly the toolchain-sdk. qte is for embedded qt Robert P. J. Day rpj...@crashcourse.ca编写： something that could be cleared up a bit in the docs ... how many toolchain-related targets are there? for instance, running bitbake suggests that common targets include meta-toolchain and meta-toolchain-sdk. on the other hand, the ADT manual makes no reference to meta-toolchain-sdk but *does* mention meta-toolchain-gmae (without explaining to the reader what that represents but nonetheless recommends to the reader that if he needs GMAE, he should build that, whereupon the poor reader is left wondering what the heck GMAE is and whether it's important). and a search of the source shows a meta-toolchain-qte, for which i can see no mention whatever in *any* of the docs. thoughts? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to build 32-bit x86 host 32-bit powerpc target cross compiler, on a 64-bit x86 host
Please set SDKMACHINE to i686 in your local.conf when you building the cross canadian compiler. Best Regards, Lianhao From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Elvis Dowson Sent: Tuesday, June 12, 2012 11:15 PM To: Yocto Discussion Mailing List Subject: [yocto] How to build 32-bit x86 host 32-bit powerpc target cross compiler, on a 64-bit x86 host Hi, I am running Ubuntu 12.04 LTS 64-bit. I have a colleague who doesn't have a 64-bit linux installation. What I'd like to be able to do is to build a 32-bit host 32-bit powerpc target cross compiler, on my 64-bit machine. How can I configure Yocto to do this? At the moment, I've already generated a meta-toolchain SDK, which installs into : /opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/ppc440-poky-linux/ How can I generate a the 32-bit hosted cross compiler on my 64-bit yocto build machine? I really didn't quite understand the term canadian-cross compiler, until now!! ;-) Now I know!! Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Broken SDK
Navani Srivastava wrote on 2012-05-28: Hi, I am working with poky-bernerd-5.0. I have built cross-toolchain for qt with bitbake -v meta-toolchain-qte for arm1136 architecture. I got the tool chain poky-eglibc-i686-arm-toolchain-1.0.tar.bz2 under build/tmp/deploy/sdk/ directory. On untaring this Toolchain I found that cross gcc wasn't included in the SDK. Can anyone please help me in recognizing the problem? I think the meta-toolchain-qte was not workable in benard. You might need to cherry-pick other patches for the recipe meta-toolchian-qte. http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/meta/recipes-qt/meta/meta-toolchain-qte.bb Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Connecting to target using eclipse/ADT
Emirelkholy, If the program is successfully transferred to the target by the Eclipse then I assume the tcf-agent is already running. However please doublecheck the followings: - When you create connections, make sure you choose type TCF. - Try to goto Remote system explorer(RSE) perspective, and see if you can open a terminal to your target through tcf - make sure gdbserver is installed on your target Best Regards, -Lianhao emirelkh...@gmail.com wrote on 2012-05-23: Hello, I can ping my target with no problem, and when I tried to debug a hello world program it transferred the hello world file the target. The connection just timed out so I was unable to debug through eclipse. How can I check to verify the tcf agent is running on thr target? Do you have instructions? Thanks, Emir On May 22, 2012, at 4:23 PM, Zhang, Jessica jessica.zh...@intel.com wrote: So do you have access to your target at all? Can you verify that the tcf-agent is up running on the target device? -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Emir Elkholy Sent: Tuesday, May 22, 2012 11:58 AM To: yocto@yoctoproject.org Subject: [yocto] Connecting to target using eclipse/ADT When connecting to my CRB that is running off a usb drive that has yocto on it I am trying to connect to the CRB from my host in order to debug using TCF agent. Through eclipse I am entering the IP address of the target, and attempting to debug from the debug configurations menu. Using a simple helloworld as an example, the file is actually transferred to the target CRB, but the debugging fails. Eclipse gives me a connection timing out error (not allowing me to debug). Is there a link that describes how to connect to a physical target using eclipse and the ADT? Is there anything that must be done on the target side first before attempting to debug? I only enter the IP address of the target under debug configurations, I don't setup anything on the target side, maybe this is the problem? I followed the same procedure as connecting to the QEMU (which works) as I did with the physical hardware. I can't find anything online about a connection time out either. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to launch core-image-minimal built upon poky-tiny
Hi Darren, Do you know how to use qemu to launch the core-image-minimal image build upon the poky-tiny distribution? I tried the following command but ended up in Kernel panic - not syncing: No init found. tmp/sysroot/x86_64-linux/usr/bin/qemu -kernel /tmp/deploy/image/bzImage-qemux86.bin -append console=ttyS0, 115200 root=0800 -nographic tmp/deploy/images/core-image-minimal-qemux86.ext2 Best Regards -Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] error: runqemu command not fonund, when $ runqemu qemux86 bzImage-qemux86.bin core-image-lsb-qt3-qemux86.ext3 THx!
jack wrote on 2012-04-14: hi,all! I Use a pre-built image and run it in the QEMU emulator. I have downloaded and installed poky-eglibc-i686-i586-toolchain-gmae-1.1.1.tar.bz2, then I downloaded bzImage-qemux86.bin and core-image-lsb-qt3-qemux86.ext3 but when $ runqemu qemux86 bzImage-qemux86.bin core-image-lsb-qt3-qemux86.ext3 error like below: error: runqemu command not fonund You may need to source /opt/poky/1.1.1/environment-setup-i586-poky-linux first before you runqemu. Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ADT Manual v1.1.1 Issues - 2 of 3
Andy, I checked the config.log. I think you might set the incorrect sysroot directory in Eclipse. The /opt/poky/1.1.1/sysroots/ is incorrect, in your case it should be /opt/poky/1.1.1/sysroots/x86_64-poky-linux/. Please select your helloworld project, then select Project - Change Yocto Project Settings. Make sure you've set the correct sysroot directory. Then select Project - Reconfigure Project to regenerate the configure sciprt. I also recommend you pointing your sysroot location to where you've extracted core-image-sato-sdk. The sysroot under /opt/poky/1.1.1/sysroots/ x86_64-poky-linux/ contains only very limited header files and libraries. -Lianhao Andy Gikling wrote on 2012-04-10: Lianhao, Attached is the config.log and the environment setup file. I hope this gives us some insight. Thank you for your time. ~Andy Gikling -Original Message- From: Lu, Lianhao [mailto:lianhao...@intel.com] Sent: Tuesday, April 10, 2012 12:08 AM To: Andy Gikling; yocto@yoctoproject.org Subject: RE: ADT Manual v1.1.1 Issues - 2 of 3 Andy, Could you please attach both the config.log file and the environment file under the directory /opt/poky/1.1.1/ ? Andy Gikling wrote on 2012-04-10: All, I've had very mixed results during the three or four times I've run through the ADT manual from scratch. There seems to be a real problem I keep encountering that I'd like to describe to the community with the hope that someone understands why I keep getting stuck. I'm running a 32bit Ubuntu 11.10 VM and trying to build for a x86_64 sugarbay target machine. The issue is that no matter which route I take to setup my toolchain (be it via the installer script or a premade toolchain I've downloaded) I always get configure: error: C compiler cannot create executables when I try to use Project-Reconfigure Project after starting a new HelloWorld example in Eclipse. The ADT manual explicitly steps the user through to this point but using the Reconfigure Project feature (that puts together your Makefile for you) never completes. When looking closer at the config.log I always find something that looks like this: configure:3285: $? = 0 configure:3274: x86_64-poky-linux-gcc -v 5 Using built-in specs. COLLECT_GCC=x86_64-poky-linux-gcc COLLECT_LTO_WRAPPER=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/li bex ec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.6.3/lto-wra pper Target: x86_64-poky-linux Configured with: /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build /bu ild/tmp/work-shared/gcc-4.6.2+svnr181430-r17/gcc-4_6-branc h/configure --build=x86_64-linux --host=i686-pokysdk-linux --target=x86_64-poky-linux --prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr --exec_prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr --bindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-po ky- linux --sbindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-p oky -linux --libexecdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libexec/x 86_ 64-poky-linux --datadir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share --sysconfdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/etc --sharedstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/com --localstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/var --libdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/lib/x86_64-po ky- linux --includedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include --oldincludedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/includ e --infodir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/info --mandir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/man --disable-silent-rules --with-libtool-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-sla ve/ nightly-x86-64/build/build/tmp/sysroots/i686-pokysdk-linux-nativ esdk --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix --disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=x86_64-poky-linux- --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp --disable-libmudflap --enable-cheaders=c_global --with-local-prefix=/opt/poky/1.1.1/sysroots/x86_64-poky-linux/usr --with-gxx-include-dir=/usr/include/c++ --with-build-time-tools=/srv/home/pokybuild/yocto-autobuilder/yocto-sl ave /nightly-x86-64/build/build/tmp/sysroots/x86_64-linux/usr/x86_ 64-poky-linux/bin --with-sysroot=/opt/poky/1.1.1/sysroots/x86_64-poky-linux --with-build-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave /ni ghtly-x86-64/build/build/tmp/sysroots/qemux86-64 --disable-libunwind-exceptions --disable-libssp --disable-libgomp --disable-libmudflap --with-mpfr=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly- x86 -64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk --with-mpc=/srv/home/pokybuild/yocto-autobuilder
Re: [yocto] autobuilder failure http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433
Saul Wold wrote on 2012-04-11: On 04/10/2012 08:16 AM, Lu, Lianhao wrote: Hi Saul, I think I might have some clues why the python-nativesdk failed at http://autobuilder.pokylinux.org:8010/builders/nightly-x86/builds/433. It's due to the commit http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=stage/ma ster_under_testid=a1f1cc4c27b5091870b1dbd9ede7c24c38d 765dd. I guess the above commit which changed eglibc-nativesdk to version 2.15 has some conflict to the sstate-cache the autobuilder used, which might contains content from old eglibc-nativesdk 2.13. Yes, that would do it, I will hit the sstate reset button and do a build that should clear this, but will cause problems for most people, I wonder if we need a PR bump in eglibc also? I think theoretically the PV change from 2.13 to 2.15 has the same effect of PR bump. I guess maybe some -nativesdk packages(other than eglibc-nativesdk) which was built upon eglibc-nativesdk 2.13 didn't get rebuilt somehow and went from sstate-cache directly into sysroot. Since I can't reproduce this compile failure on my local build, do we have the failure environment on autobuilder which I can log on and check? Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ADT Manual v1.1.1 Issues - 2 of 3
Andy, Could you please attach both the config.log file and the environment file under the directory /opt/poky/1.1.1/ ? Andy Gikling wrote on 2012-04-10: All, I've had very mixed results during the three or four times I've run through the ADT manual from scratch. There seems to be a real problem I keep encountering that I'd like to describe to the community with the hope that someone understands why I keep getting stuck. I'm running a 32bit Ubuntu 11.10 VM and trying to build for a x86_64 sugarbay target machine. The issue is that no matter which route I take to setup my toolchain (be it via the installer script or a premade toolchain I've downloaded) I always get configure: error: C compiler cannot create executables when I try to use Project-Reconfigure Project after starting a new HelloWorld example in Eclipse. The ADT manual explicitly steps the user through to this point but using the Reconfigure Project feature (that puts together your Makefile for you) never completes. When looking closer at the config.log I always find something that looks like this: configure:3285: $? = 0 configure:3274: x86_64-poky-linux-gcc -v 5 Using built-in specs. COLLECT_GCC=x86_64-poky-linux-gcc COLLECT_LTO_WRAPPER=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libex ec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.6.3/lto-wra pper Target: x86_64-poky-linux Configured with: /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/bu ild/tmp/work-shared/gcc-4.6.2+svnr181430-r17/gcc-4_6-branc h/configure --build=x86_64-linux --host=i686-pokysdk-linux --target=x86_64-poky-linux --prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr --exec_prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr --bindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-poky- linux --sbindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-poky -linux --libexecdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libexec/x86_ 64-poky-linux --datadir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share --sysconfdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/etc --sharedstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/com --localstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/var --libdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/lib/x86_64-poky- linux --includedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include --oldincludedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include --infodir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/info --mandir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/man --disable-silent-rules --with-libtool-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/ nightly-x86-64/build/build/tmp/sysroots/i686-pokysdk-linux-nativ esdk --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix --disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch --program-prefix=x86_64-poky-linux- --enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp --disable-libmudflap --enable-cheaders=c_global --with-local-prefix=/opt/poky/1.1.1/sysroots/x86_64-poky-linux/usr --with-gxx-include-dir=/usr/include/c++ --with-build-time-tools=/srv/home/pokybuild/yocto-autobuilder/yocto-slave /nightly-x86-64/build/build/tmp/sysroots/x86_64-linux/usr/x86_ 64-poky-linux/bin --with-sysroot=/opt/poky/1.1.1/sysroots/x86_64-poky-linux --with-build-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/ni ghtly-x86-64/build/build/tmp/sysroots/qemux86-64 --disable-libunwind-exceptions --disable-libssp --disable-libgomp --disable-libmudflap --with-mpfr=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86 -64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk --with-mpc=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86- 64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk --enable-nls --enable-__cxa_atexit Thread model: posix gcc version 4.6.3 2017 (prerelease) (GCC) configure:3285: $? = 0 configure:3274: x86_64-poky-linux-gcc -V 5 x86_64-poky-linux-gcc: error: unrecognized option '-V' x86_64-poky-linux-gcc: fatal error: no input files compilation terminated. configure:3285: $? = 1 configure:3274: x86_64-poky-linux-gcc -qversion 5 x86_64-poky-linux-gcc: error: unrecognized option '-qversion' x86_64-poky-linux-gcc: fatal error: no input files compilation terminated. I've tried to figure out what this error means but haven't had any luck. People have made some suggestions that I've tried and they haven't worked either. So, I've been told to file a bug about this but I wasn't sure which category it goes under and I've never filed a bug in the Yocto project before. I'll try to get to it this week. In the meantime, if anyone has tried to get through the ADT manual and is cross compiling I'd love
Re: [yocto] ADT Manual v1.1.1 Issues - 3 of 3
Hi Beth, Looks like the 1.1.1 rootfs on adtrepo was populated into a wrong URL. It should be http://adtrepo.yoctoproject.org/1.1.1/rootfs/ instead of http://adtrepo.yoctoproject.org/1.1.1/adt-ipk/rootfs/. Hi Andy, Please file a bug against 1.1.1. Before we got that fixed, you may tweak the adt-installer to work around the issue. 1. Open adt-installer script, find the function download_file 2. Find the last statement: wget $YOCTOADT_REPO/rootfs/$1 ..., and change that to wget $YOCTOADT_REPO/adt-ipk/rootfs/$1. Best Regards, Lianhao From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Andy Gikling Sent: Tuesday, April 10, 2012 12:43 PM To: yocto@yoctoproject.org Subject: [yocto] ADT Manual v1.1.1 Issues - 3 of 3 All, I ran through the ADT manual and ran into some goofynees in section 2.1.1.2. Configuring and Running the ADT Installer Script. My adt_installer.conf contains: YOCTOADT_REPO=http://adtrepo.yoctoproject.org/1.1.1; YOCTOADT_TARGETS=x86_64 YOCTOADT_QEMU=Y YOCTOADT_NFS_UTIL=Y YOCTOADT_ROOTFS_x86_64=minimal YOCTOADT_TARGET_SYSROOT_IMAGE_x86_64=minimal YOCTOADT_TARGET_SYSROOT_LOC_x86_64=$HOME/Desktop/ADT_Try2/sysroot Which should all be just fine. When you run the installer script with these settings you will come to a 404 Not Found Error. The image that was supposed to be downloaded to the /download_image/ folder is not there and eventually you will get an error from the script when it tries to extract the sysroot image it thought it downloaded. I've found the sysroot file it's looking for in the Yocto downloads and put it in /download_image/ folder manually. Once that's done the ADT installer script will then complete successfully. There's a broken link there. Does the YOCTOADT_REPO=http://adtrepo.yoctoproject.org/1.1.1; need to contain a more exact path. I'll try again with YOCTOADT_REPO=http://adtrepo.yoctoproject.org/1.1.1/adt-ipk/x86_64/; or something like that... Just an FYI, ~Andy Gikling LasX Industries Inc. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse-ADT-build-error
Huaming, Could please include the following in your description, so we can have a clear context for your problem? Thanks! 1. Host OS? 2. Which version of eclipse? 3. Which version of Yocto eclipse plugin? 4. Which image do you use as sysroot? core-image-sato or core-image-sato-sdk? 5. Which version of metadata do you use to build the image? 6. How do you install the toolchain? Using adt-installer or extracting meta-toolchain tarball? If using meta-toolchain tarball, which version do you use? b.t.w. Could you check the /home/shm/workspace/test1/config.log file? It should have more detailed information. -Lianhao 沈华明 wrote on 2012-04-05: I have installed the ADT and configured the Eclipse. When build my first project,it comes the error. The console shows these: enerating Makefile in build directory: /home/shm/workspace/test1 Command-line environment variables: CFLAGS= -g -O0 -m32 -march=i586 --sysroot=/home/shm/qemux86-sato CXXFLAGS= -g -O0 -m32 -march=i586 --sysroot=/home/shm/qemux86-sato LDFLAGS= --sysroot=/home/shm/qemux86-sato CPPFLAGS= -m32 -march=i586 --sysroot=/home/shm/qemux86-sato sh /home/shm/workspace/test1/configure --with-libtool-sysroot=/home/shm/qemux86-sato --host=i586-poky-linux --build=i686-linux --target=i586-poky-linux configure: loading site script /opt/poky/1.1.1/site-config-i586-poky-linux checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for i586-poky-linux-strip... i586-poky-linux-strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i586-poky-linux-gnu checking how to print strings... printf checking for style of include used by make... GNU checking for i586-poky-linux-gcc... i586-poky-linux-gcc checking whether the C compiler works... no configure: error: in `/home/shm/workspace/test1': configure: error: in `/home/shm/workspace/test1': configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Configuration failed with error Build of configuration Build (GNU) for project test1 make all make: *** No rule to make target `all'. Stop. Build Finished Thank you for you help~ ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ref manual, ch 5, claims that toolchain should be installed under /opt/poky
Robert P. J. Day wrote on 2012-03-26: currently, ch 5 of the reference manual claims that a generated meta-toolchain tarball should be unpacked under /opt/poky, which might be *historically* correct but i just baked a meta-toolchain and its tarball contents are all prefixed with ./usr/local/, which seems inconsistent with that. Did you include the meta-yocto layer when you bake the meta-toolchain? /opt/poky is the default settings for the toolchain generated using meta-yocto layer, while oe-core uses /usr/local. I don't know why your prefix is ./usr/local. The location of toolchain should be configurable by the value of variable SDKPATH, but we didn't test it with other values in the context of meta-yocto layer. I don't think you can untar the meta-toolchain to any arbitrary place and have it work correctly. -Lianhao is the toolchain tarball relocatable these days? rday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Deleting layers in Hob
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Xu, Dongxiao
Sent: Tuesday, March 27, 2012 2:49 PM
To: yocto
Subject: [yocto] Deleting layers in Hob
When using Hob in Yocto Project, I found a issue when deleting layers. I
think I ever raised this problem before.
Let me briefly introduce how layer removal works in Hob. When user
changes a layer, it will following the below steps
1) init the cooker.
2) set new layers to cooker.
3) parse configuration files.
4) get available machines, distros, SDKs, etc.
As we know, if we source oe-init-build-env in Yocto project environment,
we will have DISTRO=poky set in local.conf by default, where the
poky DISTRO comes from the meta-yocto layer. If user deletes
meta-yocto in Hob, and then error will happen when bitbake parsing the
local.conf, since it could not find where the poky DISTRO is defined.
Even if we are able to successfully removed the meta-yocto layer by
removing the DISTRO definition in local.conf, system will report another
issue that:
Your configuration is using stamp files including the sstate hash but
your build directory was built with stamp files that do not include
this.
To continue, either rebuild or switch back to the OEBasic signature
handler with BB_SIGNATURE_HANDLER = 'OEBasic'.
This is because BB_SIGNATURE_HANDLER = OEBasic is also defined in
meta-yocto layer (poky.conf).
Meta-yocto is using OEBasicHash as default signature handler(ABI_VERSION=8, see
${TMPDIR}/abi_version), while oe-core is still using the
OEBasic(ABI_VERSION=7). This means the oe-core can not reuse the stamp files
generated by meta-yocto.
So it seems that in certain environment (e.x, Yocto Project), certain
layer (e.x, meta-yocto) should not be removed?
Or any idea on how to solve this problem?
Thanks,
Dongxiao
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] perfer older version of lttng-ust in poky distro
Hi Saul, How about this patch's merging status? Best Regards, Lianhao Lu, Lianhao wrote on 2012-03-14: Set the PREFERRED_VERSION of lttng-ust to use lttng-ust instead of lttng2-ust in poky distro. This fixed yocto bug #2062. The lttng2 is very different in terms of architecture and usage model, compared to lttng. The eclipse upstream lttng plugin won't be able to support lttng2 until the eclipse Juno release(Jun 27th, 2012). The following changes since commit 8e9f6fc77ac4763f4ed1f6e7b720420c220ba6e2: Richard Purdie (1): dates: Fix unpackaged files warning are available in the git repository at: git://git.pokylinux.org/poky-contrib llu/bug2062 http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=llu/bug2062 Lianhao Lu (1): poky.conf: Prefer lttng-ust instead of lttng2-ust. meta-yocto/conf/distro/poky.conf |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] host libGL incompatible with eglibc-nativesdk in meta-toolchain
Hi guys, During the root causing of bug #1968(http://bugzilla.pokylinux.org/show_bug.cgi?id=1968), we find that on certain distributions, i.e. FC16 x86-64 and FC15 x86-64, the host libGL is asking for glibc 2.14. But the eglibc we provided in meta-toolchain is 2.13. This would prevent the user to launch the qemu-nativesdk from meta-toolchains. The qemu-native can be launched successfully on those platform thanks to that we don't have eglibc-native, so the host libGL will finally find the host libc which is compatible. I tried launching the qemu-nativesdk by LD_PRELOAD host libc, but it seems that the host libc is NOT compatible with our ld-linux-x86-64.so.2 either. I also tried launching the qemu-nativesdk by using the host dynamic linker with --inhibit-rpath options to keep the preconfigured RPATH from being used, but it seems that this option didn't have any effect. Any thoughts of how to work-around this? Best Regards, -Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] The sysroot location in eclipse plugin?
Ni Qingliang wrote on 2012-02-17: thanks! another question: why I must specify the sysroot location in eclipse plugin? the environment-setup has it already. In case you need another target sysroot which is different from the sysroot defined in the environment files. Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] The sysroot location in eclipse plugin?
Ni Qingliang wrote on 2012-02-17: the environment-setup file in build tree had defined CFLAGS and CXXFLAGS which include the sysroot argument(build_tree/tmp/sysroots/machine). Do we must specify the sysroot location in the eclipse plugin? after specify it, I found the CFLAGS CXXFLAGS in project property follow it, and dropped the sysroot defined in environment-setup file. and I have another sysroot running on target (qemu) unzipped from the image. If I specify the target sysroot in eclipse-plugin, I can't compile my code, because there is no any header file in /usr/include. If I specify the build_tree/tmp/sysroots/machine, I can't running the qemu machine in eclipse, because there is no 'init'. The eclipse-plugin by default assumes the user using the same target sysroot for both cross compiling and qemu launching. So this requires the target sysroot having the libraries and header files. You might have 2 options here: 1. build a new image with the dev-pkgs image feature(you can set that in conf/local.conf in variable EXTRA_IMAGE_FEATURES) and use that image as target sysroot in eclipse. 2. launch the qemu in console terminal, out of eclipse, using a different target sysroot. Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to find Log
James W. wrote on 2012-02-14:
How to locate Log file while a error occur.
It's under the directory ${WORKDIR}/temp/. Actually when an error occurs, you
can find the specific log file in the output, something like.
ERROR: Logfile of failure stored in:
/intel/poky/builds/toolchain/tmp/work-shared/gcc-4.6.2+svnr181430-r22/temp/log.do_patch.15156
Best Regards,
Lianhao
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse Plugin: ADT Version too old
Jack Mitchell wrote on 2011-10-25: Hi Jessica, I just did a full fresh re-build from scratch and now my environment variables are as follows: http://ix.io/1Wf My current git status is: # On branch edision # Untracked files: # (use git add file... to include in what will be committed) # # ../bitbake/lib/bb/pysh/pyshtables.py #../conf/ #./ # ../qemuarm-toolchain/ nothing added to commit but untracked files present (use git add to track) The environment variables are still wrong, can I manually change them, I understand this is bad practice but I can't develop until I fix this. Jack, You may manually change them, but I doubt this suggesting that there might be some mismatch in your local git branch. The bitbake meta-ide-support of Edison branch on my machine could generate the right OECORE_DISTRO_VERSION and OECORE_SDK_VERSION, with the value of 1.1, not 1.1+snapshot. Could you check your file of meta-yocto/conf/distro/poky.conf for the variable DISTRO_VERSION, it should be 1.1'. b.t.w. When you bitbake meta-ide-support, there will be some configuration information on the console which might help you identify the version and configurations, e.g. OE Build Configuration: BB_VERSION= 1.13.3 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = qemuarm DISTRO= poky DISTRO_VERSION= 1.1 TUNE_FEATURES = armv5 dsp thumb arm926ejs TARGET_FPU= soft meta meta-yocto= (nobranch):1924f52cc894d4dd6b9d9c1a2248b32fc0a24c8c Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse Plugin: ADT Version too old
Jack Mitchell wrote on 2011-10-24:
I am trying to use the new eclipse plugin, which I have had working
fine for the past couple of weeks until I switched from the master branch to
edison.
I performed a fresh build using the stable edison branch, installed
the new 1.1 eclipse plugin and now whenever I try to setup the Yocto
eclipse environment I receive the following error:
Yocto Preferences Configuration Error!
OECORE related items are not found in envrionement setup files.
The ADT version you're using is too old.
Please upgrade to our latest ADT Version!
This pops up in a message box, not the eclipse console. I have
followed the ADT Setup guide to the letter and it's not playing ball -
could someone confirm this as working or point me towards a reason why I may
be getting this error?
Hi Jack,
How did you install your ADT? You can check the ADT version by cat the file
/opt/poky/${version}/version-, where is your target sys architecture.
-Lianhao
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse Plugin 1.1-M4
Hi Jack, -Original Message- From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Jack Mitchell Sent: Friday, September 23, 2011 10:13 PM To: yocto@yoctoproject.org Subject: Re: [yocto] Eclipse Plugin 1.1-M4 On 23/09/2011 15:02, Jack Mitchell wrote: I am trying to get the latest plugin working with Eclipse Indigo and have followed the instructions listed here: http://permalink.gmane.org/gmane.linux.embedded.yocto.general/2596 The instructions all work fine until I point Eclipse to a local git clone of the EclipsePlugin directory. When I try to install the plugin I recieve this error message: Cannot complete the install because one or more required items could not be found. Software being installed: Yocto Plugin for Eclipse 1.1.0.qualifier (org.yocto.sdk.feature.group 1.1.0.qualifier) Missing requirement: Yocto Plugin for Eclipse 1.1.0.qualifier (org.yocto.sdk.feature.group 1.1.0.qualifier) requires 'org.yocto.sdk.source.feature.group 0.0.0' but it could not be found Could anyone shed any light on the situation? How did you build out the plugin? You many try out using the scripts/build.sh to build the 1.1M4 plugin upon your own Indigo. ECLIPSE_HOME=dir where you installed your Indigo scripts/build.sh 1.1M4 your release name You should find the file org.yocto.sdk-your release name-date-archive.zip after a successful build. Please try install that archive zip file and see if it works. Regards, Jack. Ok, I managed to get it installed by adding the 1.0 repository so that it could find the'group' it was looking for. When installed I then tried to alter the preferences and promtly recieved this message: Do you mean you installed the 1.0 plugin? I don't think 1.0 plugin would work with Indigo. Unable to create the selected preference page. org.yocto.sdk.ide.preferences.YoctoSDKPreferencePage Screenshot: http://i.imgur.com/Ieibg.png If I try to create a project using the yocto plugin it throws a nullPointer error - am I missing something here or are there still issues to be ironed out on the new 1.1 git? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Error Creating Project with Eclipse IDE
Hi Enric, Which version of the Yocto eclipse plug-in did you use? Have you configure the plug-in as mentioned in manual section 4.1.3? Best Regards, -Lianhao Enric Balletbò i Serra wrote on 2011-09-06: Hi all, Following http://www.yoctoproject.org/docs/1.1/adt-manual/adt-manual.htm (chapter 4.2), when I’m creating a New Project I’m getting the message: Error Creating Project Project cannot be created Reason: Internal Error: java.lang.NullPointerException I'm running Eclipse Helios (Version: Helios Service Release 2, Build id: 20110301-1815) on Ubuntu 10.10 machine. Any clue with this ? Thanks in advance, Enric ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Error Creating Project with Eclipse IDE
Enric Balletbò i Serra wrote on 2011-09-06: Hi Lianhao, 2011/9/6 Lu, Lianhao lianhao...@intel.com: Hi Enric, Which version of the Yocto eclipse plug-in did you use? I'm using version 1.0 from http://www.yoctoproject.org/downloads/eclipse-plugin/1.0 with latest yocto mainline from git. I believe the latest changes in Yocto mainline is not compatible with the 1.0 plugin due to some file/variable name changes in the Yocto mainline. -Lianhao Have you configure the plug-in as mentioned in manual section 4.1.3? Yes, I followed these steps I will review the steps to see if I'm missing something ... Cheers, Enric Best Regards, -Lianhao Enric Balletbò i Serra wrote on 2011-09-06: Hi all, Following http://www.yoctoproject.org/docs/1.1/adt-manual/adt-manual.htm (chapter 4.2), when I’m creating a New Project I’m getting the message: Error Creating Project Project cannot be created Reason: Internal Error: java.lang.NullPointerException I'm running Eclipse Helios (Version: Helios Service Release 2, Build id: 20110301-1815) on Ubuntu 10.10 machine. Any clue with this ? Thanks in advance, Enric ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] POKY_DISTRO_VERSION or OECORE_DISTRO_VERSION?
Hi Jessica, I noticed the we still use POKY_DISTRO_VERSION in the environment while some other variables have changed their prefix to OECORE_ (e.g. OECORE_NATIVE_SYSROOT, etc.) Which prefix should we use for those version related variables in the environment files? OECORE_ or POKY_? -Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] where is the Sysroot Location?
Hi Simon,
Since you have run poky-extract-sdk, I assume you already had the rootfs. The
poky-extract-sdk is meant to extract the rootfs from a tarball to a user
specified directory, which should be specified as the sysroot in the plug-in.
To build a rootfs, you may want to run bitbake poky-image-sdk(for yocto 0.9)
or bitbake poky-image-sato-sdk (for current git master), and use the
poky-extract-sdk to extract the corresponding rootfs located in
${TMPDIR}/deploy/images.
Best Regards,
Lianhao
From: Li, Simon
Sent: Wednesday, March 23, 2011 5:27 PM
To: Lu, Lianhao; yocto@yoctoproject.org
Subject: RE: where is the Sysroot Location?
Hi, Lianhao,
Thanks for your replying.
Actually, I already did bitbake meta-ide-support.
And I use poky-extract-sdk to extract the pseudo.
However, when I clicked Run-External Tools-qemu_i586-poky-linux.
After kernel booting up , I got kernel panic because kernel panic - not
syncing, init not Found.
According to the status, I think I setup the wrong Sysroot location.
As the screenshot,
[cid:image001.jpg@01CBE981.C1B0]
Since I did not find any full root file system after finishing the build, could
you tell me where I can make the full root file system?
Thanks very much.
Best Regards,
Simon
From: Lu, Lianhao
Sent: Tuesday, March 22, 2011 6:36 PM
To: Li, Simon; yocto@yoctoproject.org
Subject: RE: where is the Sysroot Location?
Hi Simon,
Before using the poky tree mode, you need to run bitbake meta-ide-support
within the poky tree in a terminal. The eclipse plug-in needs the output of
that to determine several configuration options for cross compilation.
Best Regards,
Lianhao
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Li, Simon
Sent: Tuesday, March 22, 2011 11:48 AM
To: yocto@yoctoproject.org
Subject: [yocto] where is the Sysroot Location?
To whom may concern,
I tried configure the Yocto SDK.
Firstly, I need to config cross compiler options.
I choose Pocky Tree Mode.
I always get the error message, said, Yockto Configuration Error!
Specification Poky Tree Toolchain Root does not contain any toolchain yet.
Please run bitbake meta-ide-support to build the toolchain.
However, I assigned the toolchain directory which gcc resides, I still get this
prompt message.
Could anyone please tell me what I have done wrong.
Thanks.
Simon Li
Intel Software Service Group
B1 #205 Tun-Hwa North Rd, Taipei, Taiwan
Desk
+886-2-2514-4287
Mobile
+886-987-303-523
E-Mail
simon...@intel.commailto:gorden.n...@intel.com
inline: image001.jpg___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] where is the Sysroot Location?
Hi Simon, Before using the poky tree mode, you need to run bitbake meta-ide-support within the poky tree in a terminal. The eclipse plug-in needs the output of that to determine several configuration options for cross compilation. Best Regards, Lianhao From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Li, Simon Sent: Tuesday, March 22, 2011 11:48 AM To: yocto@yoctoproject.org Subject: [yocto] where is the Sysroot Location? To whom may concern, I tried configure the Yocto SDK. Firstly, I need to config cross compiler options. I choose Pocky Tree Mode. I always get the error message, said, Yockto Configuration Error! Specification Poky Tree Toolchain Root does not contain any toolchain yet. Please run bitbake meta-ide-support to build the toolchain. However, I assigned the toolchain directory which gcc resides, I still get this prompt message. Could anyone please tell me what I have done wrong. Thanks. Simon Li Intel Software Service Group B1 #205 Tun-Hwa North Rd, Taipei, Taiwan Desk +886-2-2514-4287 Mobile +886-987-303-523 E-Mail simon...@intel.commailto:gorden.n...@intel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] default dependencies not built in bitbake -b
Hi fellows, Does anyone know why bitbake -b .bbfile fails on a newly cloned poky tree, complaining about the cross-compiler can not be found in the PATH. Does bitbake -b build the default dependencies? Best Regards, -Lianhao Lu ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] bug#565: adding environment files
Hi Saul,
I've fixed and resubmitted the patch. Sorry for not following the patch
submission convention.
Best Regards,
-Lianhao
Saul Wold wrote on 2010-12-14:
On 12/13/2010 04:07 AM, Lianhao Lu wrote:
I rebased the previous patch of adding package of environment files
to be compatible with the new cross-canadian.bbclass
Lianhao,
This may require Richard to look at a little more closely, I do notice
that you are missing the LIC_FILES_CHKSUM, for this on you can use one
similar to recipes-core/tasks/task-base.bb
The first line of the commit message synopsis needs to be more
descriptive, and the bug id needs to be in the commit message so that
we can parse it out later.
Synopsis is normally
recipe | file : Synopsis
Example:
meta-environment: Added package of meta-environment-${TARGET_ARCH} for
environment files.
In the body of the commit message you can add the bug id according to
this format:
[BUGID# NNN], where NNN is the bugid
Please fix these issues and resubmit, also you should use the
p...@yoctoproject.org for bug submissions.
Sau!
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: llu/bug565
Browse:
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=llu/bug565
Thanks,
Lianhao Lulianhao...@intel.com
---
Lianhao Lu (1):
Fix bug #565.
meta/classes/toolchain-scripts.bbclass | 32 ++
meta/recipes-core/meta/meta-environment.bb | 74
meta/recipes-core/tasks/task-cross-canadian.bb |1 + 3 files
changed, 107 insertions(+), 0 deletions(-) create mode 100644
meta/recipes-core/meta/meta-environment.bb
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Best Regards,
Lianhao
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patch] meta-environment
Hi all, The attached patch is to create environment file package used by the ADT installer during ADT installation. This patch should be applied upon my previous pull request of bug#528 fixing (see the following summary of the previous pull request): Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: llu/fix Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=llu/fix Best Regards, -Lianhao Lu meta-environment.patch Description: meta-environment.patch ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse plugin
Gary Thomas wrote on 2010-11-22: On 11/22/2010 02:13 AM, Gary Thomas wrote: I'm interested in trying the Yocto Eclipse plugin with my Poky based builds. That said, I'm a true Eclipse novice :-( Does anyone have some guidance on what packages I might need to install to get a usable Eclipse framework on Fedora (13)? For example, the Yocto page mentions the standard TCF agent to contact the target - how do I make sure this is available and enabled? n.b. the [web] documentation on this plugin is pretty thin. Perhaps once I get this going, I can contribute some meat to put on these bones :-) Thanks I tried to follow the documentation in the Poky manual (still thin...), but it seems I'm now stuck. I get this error: Cannot complete the install because one or more required items could not be found. Software being installed: Yocto Plugin for Eclipse 1.0.0.201010202121 (org.yocto.sdk.feature.group 1.0.0.201010202121) Missing requirement: Yocto Plugin Remote Tools 1.0.0.201010202121 (org.yocto.sdk.remotetools 1.0.0.201010202121) requires 'bundle org.eclipse.rse.terminals.ui 1.0.100' but it could not be found Cannot satisfy dependency: From: Yocto Plugin for Eclipse 1.0.0.201010202121 (org.yocto.sdk.feature.group 1.0.0.201010202121) As far as I can tell, the eclise-rse package on Fedora 13 is version 1.0.1 :-( Also, Fedora is still on Galileo 3.5.2, not Helios 3.6. I guess I'll try the raw install of Helios since Fedora+YUM has failed me. Gary, Sorry for the thin documentation about eclipse plug-in installation. The Yocto eclipse plugin has some dependencies on other eclipse plugins: - C/C++ Development Tools (CDT) (http://download.eclipse.org/tools/cdt/releases/helios if using Eclipse 3.6Helios, or http://download.eclipse.org/tools/cdt/releases/galileo if using Eclipse 3.5Galileo) - Autotools support for CDT (Incubation) (http://download.eclipse.org/technology/linuxtools/update) - Target Management (RSE) (http://download.eclipse.org/dsdp/tm/updates/3.2) To install one of the above eclipse plugins in the IDE, 1. Go to Help Install New Software... to open the Install dialog. 2. Click the Add... button; this will display the Add Site dialog. 3. Enter the corresponding URL in the Location: field and click OK. This will add the corresponding update site to the list of available sites. 4. The corresponding update site should now be selected in the Work with: selection box. If not, you can select it from the list by clicking the down arrow and locating its entry. You can simply collapse the entry for this site to view content available for installation. 5. Check the corresponding box and click Next button, following the wizard to install the plug-in. Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse plugin
Gary Thomas wrote on 2010-11-22: Thanks, I installed Helios directly from the Eclipse site and that's working better now. I also installed the components you mention above. When I try to configure Yocto, I'm trying to use the Poky tree method but it doesn't like my tree :-( I pointed it to my build directory (the one which contains tmp/, sstate-cache/ and conf/) What else am I missing? You need to bitbake meta-ide-support before you can use the poky tree mode. Best Regards, Lianhao ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
