Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316526 - An executable's .attrs.rtsName should be null when .attrs.cfgScript is a legacy .tcf script
Summary: An executable's .attrs.rtsName should be null when .attrs.cfgScript is a lega...
Status: CLOSED WONTFIX
Alias: None
Product: RTSC
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Dave Russo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-10 15:51 EDT by Chris Ring CLA
Modified: 2010-07-15 18:06 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Ring CLA 2010-06-10 15:51:41 EDT 
In the build model, XDC should default "myExe.attrs.rtsName = null" when it sees the executable is a BIOS 5 executable.  I.e., when "myExe.attrs.cfgScript" is a .tcf, it should default myExe.attrs.rtsName to null.

Currently, to avoid a dependency on xdc.runtime, the user must explicitly set .attrs.rtsName to null - which is almost certainly what they want, but easy to forget.
Comment 1 Dave Russo CLA 2010-07-06 18:36:32 EDT 
Rejected since this will be a compatibility break.
File a new bug where usage of legacy tcf is documented in a wiki page.
Comment 2 Dave Russo CLA 2010-07-15 18:06:22 EDT 
Bug is rejected