Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357711

Summary: [RDT] Local toolchains should not be selectable for a Remote C/C++ project
Product: [Tools] PTP Reporter: Corey Ashford <cjashfor>
Component: RDTAssignee: Project Inbox <ptp-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: g.watson, recoskie
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Toolchain fix for any Remote Projects none

Description Corey Ashford CLA 2011-09-14 20:15:27 EDT 
Build Identifier: I20110613-1736

When I create a Remote C/C++ project, why are the local toolchains (e.g. Linux GCC, XL C/C++) visible?  I think the only toolchains that should be visible are all of the Remote variants.


Reproducible: Always

Steps to Reproduce:
1. File->New->Remote C/C++ Project
2. Open up Remote Makefile Project
3. Select "Empty Project"
4. Notice all of the local toolchains that are visible.
Comment 1 Ginger CLA 2011-11-15 13:08:36 EST 
Created attachment 207041 [details]
Toolchain fix for any Remote Projects

This fixes the problem of having all toolchains being displayed on "Empty Makefile" Remote Makefile Projects.  Only Toolchains with the word "Remote" will be in the toolchains.

Added braces and one line of code.

The test is the same as the steps to reproduce, and a check of the other projects as well.
Comment 2 Chris Recoskie CLA 2011-11-15 13:34:28 EST 
(In reply to comment #1)
> Created attachment 207041 [details]
> Toolchain fix for any Remote Projects
> This fixes the problem of having all toolchains being displayed on "Empty
> Makefile" Remote Makefile Projects.  Only Toolchains with the word "Remote"
> will be in the toolchains.
> Added braces and one line of code.
> The test is the same as the steps to reproduce, and a check of the other
> projects as well.

Unfortunately that won't work, as the toolchain names are translated for the various language packs.
Comment 3 Greg Watson CLA 2014-05-29 15:18:31 EDT 
Assuming this will not be fixed.
Comment 4 Corey Ashford CLA 2014-05-29 15:34:46 EDT 
Hi Greg,

Is the RDT being shut down as an active project?  I'm just curious.
Comment 5 Greg Watson CLA 2014-05-29 15:48:07 EDT 
The last fix to RDT was committed over a year ago, so I'm assuming no one is working on it any more. I'm happy to be proved wrong :-).
Comment 6 Corey Ashford CLA 2014-05-29 15:50:13 EDT 
(In reply to Greg Watson from comment #5)
> The last fix to RDT was committed over a year ago, so I'm assuming no one is
> working on it any more. I'm happy to be proved wrong :-).

Oh, that's a shame.  It is a nice facility and deserves some TLC.
Comment 7 Chris Recoskie CLA 2014-05-30 07:43:14 EDT 
(In reply to Greg Watson from comment #5)
> The last fix to RDT was committed over a year ago, so I'm assuming no one is
> working on it any more. I'm happy to be proved wrong :-).

I'm still around but resources are limited, and we're on Eclipse 4.2 so we're not really actively looking at the latest stuff unless something explodes.
Comment 8 Chris Recoskie CLA 2014-05-30 07:44:09 EDT 
(In reply to Corey Ashford from comment #6)
> Oh, that's a shame.  It is a nice facility and deserves some TLC.

Show me the money.  Committers aren't free.  Someone has to pay their salaries.
Comment 9 Greg Watson CLA 2014-05-30 07:45:39 EDT 
If you think any of these bugs have been closed prematurely, please feel free to reopen.
Comment 10 Corey Ashford CLA 2014-05-30 12:41:01 EDT 
(In reply to Greg Watson from comment #9)
> If you think any of these bugs have been closed prematurely, please feel
> free to reopen.

No, I was mostly just curious about what was going on.  I thought maybe RDT was going to be replaced by something else.