I installed Oxygen latest and greatest plus a JDK 1.8.x and I don't want to build the SDK Plugin myself, but use something ready made. from here: http://downloads.yoctoproject.org/releases/eclipse-plugin/2.5.0/oxygen/ But I get Cannot perform operation. Computing alternate solutions may take a while: 15/15 ... and it finally fails
The same happens with Neon! I can not install the 2.5.0 SDK plugin - same problem as with Oxygen.
This seems to be the problem: Cannot complete the install because one or more required items could not be found. Software being installed: Yocto Project SDK Plug-in 1.4.1.201804240009 (org.yocto.sdk.feature.group 1.4.1.201804240009) Missing requirement: Utils 1.4.1.201804240009 (org.yocto.remote.utils 1.4.1.201804240009) requires 'package org.eclipse.rse.internal.terminals.ui 0.0.0' but it could not be found Cannot satisfy dependency: From: Yocto Project SDK Plug-in 1.4.1.201804240009 (org.yocto.sdk.feature.group 1.4.1.201804240009) To: org.yocto.remote.utils [1.4.1.201804240009] What do I need to install?
looks like installing this[1] makes it more happy [1] http://download.eclipse.org/tm/downloads/drops/S-3.6M4-201312162110/index.php
It seems to be enough to install from the bundle above: TM and RSE 3.5 Main Features -> Target Management Terminal Afterwards it's possible to install the Yocto SDK plugin.
*** Bug 12796 has been marked as a duplicate of this bug. ***
Robert, can you tell us how you installed Eclipse? Did you use the "Eclipse IDE for C/C++ Developers" tarball or the graphical Oomph Installer? We are seeing different behavior between the two installation techniques. In the process of releasing Photon, some older artifacts were moved by upstream Eclipse and we suspect this might be the cause, but it is unclear why it would behave differently depending on the Eclipse installation method used.
Hi, I tried Oxygen *) with the installer *) without the installer, simply extracting the CDT tarball I tried Neon *) with the installer *) without the installer, simply extracting the CDT tarball I could not get them to work with the Yocto 2.5 Eclipse plugin Also not when I built the plugin myself. What I have running at the moment is some eclipse.tar.xz.oxygen plus manually installed from org.eclipse.tm.repo-3.6-M4.zip the Terminal. I even managed to make all of this run within a docker container. It's a JDK + a tarball (which contains whatever is needed). -------- The issue might actually be the plugin, since I also could not get it to work with Eclipse Neon and I was able to install a 2.4.x plugin with Neon on the same Eclipse version (where Terminal is available).
This sounds like the Eclipse YP Plug-in is the ultimate problem. Are there plans to fix this? For now I can alter the documentation to include the work-around of Robert's if that is agreeable. It looks like for the work-around it is just installing Eclipse normally and then installing software from the following? http://download.eclipse.org/tm/downloads/drops/S-3.6M4-201312162110/index.php I am not exactly clear on the exact steps needed from that site .. what pieces, etc. Maybe Robert can help me out. * Manually installing TM from org.eclipse.tm.repo-3.6-M4.zip * Installing Eclipse Oxygen as normal from http://www.eclipse.org/oxygen/ Thanks, Scott
@Scott I am __NOT__ an Eclipse expert. Just tried to make it work somehow. In your doc[1] you say this: Expand the box next to "Linux Tools" and select the following: C/C++ Remote (Over TCF/TE) Run/Debug Launcher TM Terminal Expand the box next to "Mobile and Device Development" and select the following boxes: C/C++ Remote (Over TCF/TE) Run/Debug Launcher Remote System Explorer User Actions TM Terminal TCF Remote System Explorer add-in TCF Target Explorer If you try for yourself with Oxygen you will not see the "TM Terminal", which seems to be required by the "Yocto Project SDK Plug-in". So installed the component from[2]. ... but ... Was this bundled with previous Yocto Project SDKs? Was is not a requirement before? What puzzles me is, that Neon + rocko worked without any tricks, but I could not get it to work with sumo. Maybe someone can give it a try and see what happens as well. [1] https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#oxygen-configuring-the-eclipse-ide [2] http://download.eclipse.org/tm/downloads/drops/S-3.6M4-201312162110/index.php
I can no longer reproduce the problem. I tried installing eclipse-yocto 2.5 plugin using both the eclipse installer and eclipse tarball approaches and they both worked. I'm not entirely sure if this is related to discussion on eclipse tm-dev where the TM update sites were moved and restored: https://dev.eclipse.org/mhonarc/lists/tm-dev/msg01313.html Robert, can you confirm that the workaround is no longer required on your end?
I can't reproduce it either. Eclipse must have done something to cause our plug-in to work. Scott
I believe the "fix" is related to this thread: http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg33030.html Essentially, Eclipse DevOps had done some house cleaning and moved the TM/RSE repositories (tm/updates) under a directory called "OLD_STUFF" without asking anybody. They figured if it broke anything they would hear about it. It broke things for CDT as well, not just us. You can see the contents of "OLD_STUFF" in our mirror: https://downloads.yoctoproject.org/eclipse-full/tm/updates/OLD-STUFF/
Closing this as invalid.