New: Orphaned/missing toolchain borks eclipse plugin

https://bugs.busybox.net/show_bug.cgi?id=8846

Bug ID: 8846
Summary: Orphaned/missing toolchain borks eclipse plugin
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: subwooferbone at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

Using latest Buildroot Eclipse plugin.

Importing CDT project from another user, all build targets are gone. Eclipse complains "An error has occurred. See error log for more details. java.lang.NullPointerException".

C/C++ Build and C/C++ General pages of project properties are borked, null pointers galore.

Same behaviour with both Mars and Luna. Uninstalling the plugin makes the C/C++ options pages work again, but it is impossible to select another toolchain for the projects defined with buildroot toolchains. Then complains about orphaned toolchain.

Message sent to stderr: "Managed Build system manifest file error: Option org.buildroot.home.bob.software_PI1509.platform.buildroot.output..toolchain.base.option.path.1204713667 uses a null category that is invalid in its context. The option was ignored."

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8846

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Thomas Petazzoni <[email protected]> --- Thanks for your bug report. However, this bug is not directly related to Buildroot, but rather to its Eclipse plugin. Could you report it to the Buildroot Ecplise plugin issue tracker available at
https://github.com/mbats/eclipse-buildroot-bundle/issues ?

In addition, I am not sure this can work by design. Indeed, a CDT project definition will include a reference to the selected toolchain, which uses an absolute path. This absolute path is relevant on the machine where the project was created, but will not make sense on any other machine. Since I'm not an Eclipse user, I have no idea how this is typically handled in other situations.

You are receiving this mail because:
You are on the CC list for the bug.