Bug 12097

Summary:	Eclipse plugin uses (wrong) host include pathes
Product:	[Yocto Project Subprojects] Eclipse Plugin	Reporter:	Arno Steffens <star>
Component:	eclipse-plugin	Assignee:	Arno Steffens <star>
Status:	RESOLVED WORKSFORME	QA Contact:	Libertad <libertad.gonzalez.de.la.cruz>
Severity:	normal
Priority:	Medium	CC:	brian.avery, ioanax.grigoropol, yp.ep.watcher, yp.watcher
Version:	5.99
Target Milestone:	2.4 M4
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

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.