**** BEGIN LOGGING AT Fri Sep 20 02:59:57 2019 Sep 20 07:07:06 Good morning: I try to setup an eclipse IDE, whereas I can cross-compile for my target architecture, and remote debug on my target device. For this, I used oe to built the eSDK following this guide: https://www.yoctoproject.org/docs/latest/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer Sep 20 07:09:14 the output of the job "-c populate_sdk_ext" are two shell scripts. poky-glibc-x86_64-core-image-base-aarch64-raspberrypi4-64-toolchain-ext-2.7+snapshot.sh and x86_64-buildtools-nativesdk-standalone-2.7+snapshot-20190919.sh Sep 20 07:10:20 I installed the first, but it seems there is no cross toolchain included?? Sep 20 07:12:39 thomasd13: you ran the .sh which is an installation script. How did you check for the toolchain? Sep 20 07:13:13 When I set the "Toolchain Root Location" in Eclipse Plugin "Yocto Project SDK" to the installation path of the first script, Eclipse gives me the error "Specified toolchain directory does not contain a toolchain generated with "bitbake meta-ide-support"." Sep 20 07:13:50 likewise: So I assume there is a lack of toolchain. Sep 20 07:14:46 Or I did something wrong, which I think. But I have not even a glue where to start looking for my mistake.. Sep 20 07:15:26 Ah, I'm not familiar with meta-ide-support. Sep 20 07:16:53 I thought the task "populate_sdk_ext" will produce me all I need to create and debug application against my specific image. Why should "meta-ide-support" play any role here? Sep 20 07:19:22 I thought the Eclipse plugin was deprecated Sep 20 07:19:32 it is Sep 20 07:20:04 thomasd13: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/meta/meta-ide-support.bb?h=master Sep 20 07:20:06 there was a recent report of somebody making it work for his usecase on the ML, but generally it should be considered as "not usable until you maintain and fix it yourself" Sep 20 07:20:40 Okay, nice to know :) So what might the best way to achieve building and remote debugging my code on the target? Sep 20 07:21:01 meta-ide-support seems to make sure the *build* directory contains all required tools for IDE support. Sep 20 07:21:28 whereas (e)SDK installs separately from the BitBake build; i.e. creates a stand-alone (extensible) SDK Sep 20 07:21:50 LetoThe2nd, I did find this though: https://lists.yoctoproject.org/pipermail/yocto/2018-January/039790.html Sep 20 07:22:25 okay likewise, thank you Sep 20 07:23:19 kroon: that has been superses in april, see https://wiki.yoctoproject.org/wiki/2019_Yocto_Project_Weekly_Status_Archive Sep 20 07:23:28 kroon: status of april, 16th Sep 20 07:24:03 LetoThe2nd, ah Sep 20 07:24:29 thomasd13: I'm trying to figure out where the tools get installed in the build directory; http://cgit.openembedded.org/openembedded-core/tree/meta/classes/toolchain-scripts.bbclass Sep 20 07:37:56 likewise: I figured it out. Within the eSDK installation path, its under tmp/sysroots/x86_64/usr/bin/aarch64-poky-linux/ in my case Sep 20 07:38:32 So I was wrong. There are build tools included, but the eclipse plugin seems not to work properly Sep 20 07:40:07 thomasd13: I am aware of the e(SDK) but I think meta-ide-plugin might not use it Sep 20 07:41:27 thomasd13: on the other hand it might, I am just familiar with the e(SDK) and not with the meta-ide-plugin. Sep 20 07:42:29 thomasd13: In all cases, you should be able to use Eclipse with the GDB cross debugger even without meta-ide-support. Sep 20 07:43:48 likewise: Okay thank you very much for your effort. I try to setup eclipse somehow to cross-compile and find/use all headers which are available on my target. Sep 20 07:47:27 Just a basic question: In eSDK/sysroots are two folders. "x86_64" (architecture of my development machine) and "aarch64" (architecture of my target). Why is there a x86 sysroot? My assumption was that I only need the target sysroot to have all the header files from the libs which are on my target image Sep 20 07:48:52 thomasd13: For setting up Eclipse, there are ample pages describing how to set up a cross toolchain in Eclipse (not using specific plugins other than the C/C++ support), for example: https://github.com/awesomebytes/xenorasp/wiki/Crosscompile-a-program-from-your-computer-to-your-Raspberry-Pi Sep 20 07:50:42 thomasd13: the host machine stuff mostly contains the support files for the cross GDB, but probably also the headers to develop further GDB plugins against. Sep 20 07:51:00 thomasd13: I see python support scripts for cross GDB in x86_64 Sep 20 07:52:28 Thats a good starting point, thanks likewise Sep 20 07:55:18 thomasd13: good luck. BTW, what was your latest reference doc for the Eclipse plug-in support? Sep 20 07:58:59 It was for version 2.1. https://www.yoctoproject.org/docs/2.1/sdk-manual/sdk-manual.html#eclipse-overview Sep 20 07:59:50 I figured out that the last Eclipse version for Yocto Plugin was 4.7 (June 2017). I thought I could try that Sep 20 08:00:06 Eclipse Oxygen Sep 20 08:02:14 Oh wait, I have another (newer) link opened where Eclipse Plugin is referenced: https://www.yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html#neon-configuring-the-eclipse-yocto-plug-in Sep 20 08:25:17 morning mckoan Sep 20 08:42:31 morning likewise **** BEGIN LOGGING AT Fri Sep 20 09:14:43 2019 Sep 20 10:25:19 effem: hi there, long time no see Sep 20 21:04:31 OktoberFest time **** ENDING LOGGING AT Sat Sep 21 03:00:00 2019