Bug 12097 - Eclipse plugin uses (wrong) host include pathes
Summary: Eclipse plugin uses (wrong) host include pathes
Status: RESOLVED WORKSFORME
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: 5.99
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.4 M4
Assignee: Arno Steffens
QA Contact: Libertad
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-09-18 12:50 UTC by Arno Steffens
Modified: 2017-11-30 16:27 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arno Steffens 2017-09-18 12:50:38 UTC
I gave the Eclipse Plugin a try. It works so far at a first glance - so compilation was fine.
But: The include pathes are all set to the PC (0x86) instead of ARM. This seems to be a bug.

Is there someone out there, that can solve this?

Also, oxygen is out now for quite a while, but no plugin for this version. Are there expected problems to use previous plugin (neon) for oxygen?

Thanks
Arno
Comment 1 brian avery 2017-09-21 19:44:36 UTC
Questions:
1) were you using a build dir of your own? or a built sdk ? or downloaded sdk?
2) if you built it what was your machine setting?
3) on the Window->Yocto Preferences page what does the architecture dropdown show?


On the oxygen comment, I pushed an oxygen branch and it should be released as part of 2.4.
Comment 2 Arno Steffens 2017-10-25 12:21:49 UTC
Sorry for late answer.
The SDK is build with Yocto. The plugin was written for neon, but works for oxygen too (somehow).
Unfortunatly I don't have the Eclipse with this plugin anymore. 
The documentation/help for this plugin was out of date and very limited.
As it compiles for ARM I guess this Architecture selection was right.
Sorry I would help more, but im am out of office in the next weeks.
I will give the oxygen a new chance :), maybe with a few lines of help in manual.
Comment 3 brian avery 2017-11-30 16:27:54 UTC
tried and failed to reproduce this. Issues with help docs are valid and we now have someone working on the plugin so those will be brought up to date.