Comment 1 Corey Ashford 2011-08-03 18:00:05 EDT

I think I've discovered what the problem is.

The extensions for the the GNU project types had their name fields blank, so I think the CDT managed project system didn't know what to do with them, and just left them out of the list.

I've also found that the names from from the plugin.properties file that were intended to go in those fields had the shared and static library names switched.

I think I can develop a patch to fix both of these errors.  Stay tuned.  I want to make sure that the projects look legit after all of this.

Comment 2 Corey Ashford 2011-08-03 18:17:18 EDT

Created attachment 200863 [details]
Makes GCC project types visible in the Remote C/C++ project creation dialog

This patch:

* Adds the name field to the GCC project types, which is necessary for
the project types to show up in the project type selection dialog when creating
a Remote C/C++ project.

* Adds a new project type name for GCC executables, and fixes the labels for the shared and static library project types (they were reversed).

* Makes it so that the project types are applicable all host OSes and architectures, so that any host type (Windows, Linux, etc.) can create GCC
projects on remote machines (typically Linux or Unix).

Comment 3 Greg Watson 2011-08-04 16:43:52 EDT

This patch works for me. Applied to ptp_5_0 and HEAD.

Do remote projects using these toolchains work correctly?

Comment 4 Corey Ashford 2011-08-04 16:55:37 EDT

(In reply to comment #3)
> This patch works for me. Applied to ptp_5_0 and HEAD.

Thanks!

> 
> Do remote projects using these toolchains work correctly?

Yes, I tried it on a POWER machine with gcc, and it worked without any noticeable (by me) problems.

- Corey

Comment 5 Greg Watson 2011-08-04 17:03:49 EDT

Closing as fixed.