Bug 166

Summary:	wrong include directories listed in Yocto SDK project template
Product:	[Yocto Project Subprojects] Eclipse Plugin	Reporter:	Lianhao Lu <lianhao.lu>
Component:	eclipse-plugin	Assignee:	Jessica <jessica.zhang>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	minor
Priority:	Low	CC:	kevin.tian, lianhao.lu, liping.ke, sgw, yongkang.you, yp.ep.watcher, yp.watcher
Version:	1.0
Target Milestone:	Future
Hardware:	All
OS:	x86
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Lianhao Lu 2010-07-29 19:26:41 UTC

After we new a Yocto SDK project, in the "project explorer" view of C/C++ perspective, if we click the "+" beside the "Includes" under the newly created project to expand the list, it will display the native include directories like /usr/include, /usr/local/include, etc. It should display the include directories matched to the target architecture, like /opt/poky/sysroots/i586-poky-linux/usr/include, etc.

It looks though that this kind of error would not cause the cross compiler to search for fault include directory for the "hello world" project, since the cross compiler has correct built-in include directories. This is mis-leading to the users any how.

I'm not sure whether this kind of project include information will be used in compiling. If so, this would cause a problem.

Comment 1 Jessica 2010-08-03 22:27:15 UTC

The Include is added by GNU autotools project type which Yocto project type is based on.  But it seems it's not taking effect, if you right click on the Includes directory the property menu is not implemented and you can't do anything with them.  After existing from the workspace, next time opened the workspace, and for the same project, it'll be gone.  This seems a bug of GNU autotools project.  Investigating how re-open workspace can make them disappear and try to use the same mechanism during the project creation.

Comment 2 Jessica 2010-09-13 23:28:57 UTC

Filed an upstream bug against GNU Autotools project: https://bugs.eclipse.org/bugs/show_bug.cgi?id=325194

Comment 3 Yongkang You 2010-12-09 17:38:02 UTC

Still wait for upstream fixing.

Comment 4 Jessica 2011-12-20 11:37:59 UTC

lower the priority since even though it's mis-leading but the bug won't cause any real issue in our cross development setup

Comment 5 Jessica 2012-08-14 21:46:06 UTC

Seems there still no upstream fix for this and this is really has no impact to our plugin function besides misleading.