| Summary: | Orphaned/missing toolchain borks eclipse plugin | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | subwooferbone |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | blocker | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
subwooferbone
2016-04-13 12:21:38 UTC
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. |