Community
Participate
Working Groups
Build Identifier: I20100608-0911 After we new a GNU Autotools 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. If I right click on "Includes" the "Properties" implementation is broken. After compile the project and restart Eclipse, the "Includes" will disappear Reproducible: Always Steps to Reproduce: 1.In C/C++ perspective, File->New->C Project->GNU Autotools->Hello World ANSI C Autotools project. 2.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. 3.If I right click on "Includes" the "Properties" window will claims "Unknown element selected" when toggle between "Configure settings" and "General". By pressing "Cancel" or "OK" button, I'll get "element not initialized" error message. 4. If I change the project Autotools configure settings and C/C++ build to point to my cross toolchain, the project can be build with my cross toolchain with no problem. 5. After build the project and restart Eclipse, under the project, the "Includes" will disappear
The issues look like autotools plugin issues. CDT does not provide "Properties" in context menu for "Includes" node, it comes up only after Autotools plugin is installed. Disappearing of includes was reported in bug 312298.
I think you missed the point Andrew. The problem is the Includes disappearing on restart. That's a very common problem at the moment.
(In reply to comment #2) > I think you missed the point Andrew. The problem is the Includes disappearing on > restart. That's a very common problem at the moment. Isn't it the same as bug 312298 problem 1? >1. If the workspace is closed and reopened, the header file resolution is lost > and the file in the editor will show the header files are unknown until the > next build. > The behaviour above does not occur for a ManagedBuild project. That makes it duplicate isn't it. bug 312298 states that it is specific for Autotools. Does it occur without Autotools installed? There are several issues reported in the bug. The other bug related to "Properties" is also legitimate one and should be reported against Autotools.
(In reply to comment #3) > (In reply to comment #2) > > I think you missed the point Andrew. The problem is the Includes disappearing on > > restart. That's a very common problem at the moment. > > Isn't it the same as bug 312298 problem 1? > >1. If the workspace is closed and reopened, the header file resolution is lost > > and the file in the editor will show the header files are unknown until the > > next build. > > The behaviour above does not occur for a ManagedBuild project. > That makes it duplicate isn't it. bug 312298 states that it is specific for > Autotools. Does it occur without Autotools installed? > > There are several issues reported in the bug. The other bug related to > "Properties" is also legitimate one and should be reported against Autotools. The Properties issue is due to missing enabledWhen statements for the Autotools Configure Settings and General property pages. This has been fixed. The missing Includes is not Autotools specific and I will assume it is addressed by another bug. I am marking this as resolved. If the missing Includes issues is not an actual duplicate, then I suggest reopening this or opening a new bug against the CDT.
That's fair. This bug does happen with other setups and I believe it is the same as 312298. I also get it with the commercial build integrations I'm doing but, in the end, is due to the communication gap between the project descriptors and scanner discovery information.
