Both SDK and mega manual should probably refer to a more Eclipse release neutral installation method, as the documented steps only works if the URL points to the latest Eclipse version. Impacted URLs: * http://www.yoctoproject.org/docs/latest/sdk-manual/sdk-manual.html#neon-installing-eclipse-ide * http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#neon-installing-eclipse-ide It seems that only Eclipse installer for the latest release is accessible from the website, I've filed upstream bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=528472 , until this is fixed we probably need to update SDK/mega manual to use a installation method that is immutable over Eclipse releases.
We only support Neon.2, so I tried to download Eclipse installer for Neon.2 however post-installation I see a Neon.3 splashscreen/installation instead. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=528472#c1 For Eclipse Poky to properly release againsts a fixed Eclipse Neon point release, we might want to drop the Eclipse installer approach and instead go with tar.gz installation method: 1. Go to https://www.eclipse.org/downloads/packages/all and click "Neon 2" 2. Find "Eclipse IDE for C/C++ Developers" and click "Linux 64-bit" 3. Click "Download" to get the tgz from one of the mirrors 4. Untgz and run ./eclipse/eclipse
I'd be inclined to just drop the Eclipse installation section from our documentation entirely and point to the eclipse docs as an "use these to install the necessary Eclipse version".
Brian, what do you think if I update with a release neutral installation instructions for Eclipse that points out to the Eclipse docs with an included example that is updated with the latest version? This keeps one Eclipse section in the YP docs and eliminates the need to continuously update two sections with latest minus one.
It is currently not possible to use Eclipse installer to install different releases, as it always install up to the latest point release, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=528472#c2 Waiting for response from upstream to see if we can reference their documentation on Eclipse package installation.
Chin - I'm not sure I completely understand everything you are referring to, but it sounds like I need to wait for the installation to settle down, whether it be from a tarball or an Eclipse Yocto Project plugin, or something else. Once it's settled down, then we can document it, correct? Right now, we provide steps to install the Eclipse Yocto Project plugin for Mars and Neon Eclipse releases. Thanks! Kristi
Hi, Right now, the chapter 5 and Appendix D of the sdk-manual are written to assume installation and use of the Oxygen and Neon, respectively, versions of Eclipse. Final download areas do not work and will not work until the actual 2.5 version of YP is released. Right now we also cannot verify any of the steps from running QEMU forward for both Oxygen and Neon. These steps do not work. I believe Chin Huat has submitted a patch to fix this issue as it has to do with the setup script for the YP Eclipse Plug-in. Scott See the yoctoproject.org/docs/2.5/sdk-manual/sdk-manual.html manual chapters 5 and Appendix D to see the state of the docs.
Once the 2.5 release officially goes, we will run through these Eclipse steps and verify things. Scott
Currently, the manual chapters are accurate for Oxygen and Neon, and they work. We understand that this doesn't satisfy the purpose of this bug, which was to document some release neutral installation method. In order to do that, we need someone to create that installation method for us, and then we can complete it. Leaving the bug open and moving to NEED INFO. Thanks!
It looks like the instructions on Eclipse installation wiki page [1] might be too brief or high-level to be included in YP manual. Anyway, the "Installing the Neon Eclipse IDE" section seems to be updated to refer to download the "Eclipse IDE for C/C++ Developers" Neon 3 tarball instead of the Eclipse installer, so the only thing left is to make sure the "Setting Up the Oxygen Version of the Eclipse IDE" section is also updated to use "Eclipse IDE for C/C++ Developers" Oxygen 3a. It is also worth pointing out that Eclipse Foundation recommends using the installer, however the downside of this approach is that it defaults to installs the latest release (and also up to the latest update) that's available at the time the installer is executed, the actual Eclipse release/update required by (and officially tested with) eclipse-yocto plugins might be slightly behind, which would cause the installer to either install a newer update or newer release which might not be QA'ed. Using the tarball approach effectively eliminates this problem, at least until the installer supports an easier way to install older release/update. [1] http://wiki.eclipse.org/Eclipse/Installation [2] http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-yocto/log/?h=oxygen/sumo
It appears the current question has been answered. If you still have a question, please ask it and place the bug back into NEEDINFO.
Documentation changes were merged in 9f6b874740b98c5b3eed1c06dcf5fbe687279ca8.
Marking RESOLVED and setting the doc flag to "done" on this one. Scott