[RTEMS Project] #4963: New build configuration option RTEMS_QUALIFIED

[RTEMS trac]

#4963: New build configuration option RTEMS_QUALIFIED
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  enhancement      |      Status:  assigned
 Priority:  normal           |   Milestone:  7.1
Component:  build            |     Version:  7
 Severity:  normal           |  Resolution:
 Keywords:  qualification    |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------

Comment (by Joel Sherrill):

 Looking forward long term, the qualified source will be a superset of what
 is allowed per different profiles. For example, ESA's Space Profile has
 little overlap at the API level with the various POSIX profiles in the
 FACE Technical Standard. NASA is likely to have their own allowed profile.

 How does this correspond to the subsets?

 Is the plan to have a "full" qualified build versus builds that are
 tailored to specific subsets? Or to have both?

 This appears to correspond to what I see from other RTOS vendors as their
 qualified product where everything that is qualified (to whatever degree)
 is all that is included in the build. But if this is putting the burden on
 RTEMS to ensure it has nothing beyond a specific user's profile, that may
 not be the best approach. The FACE Consortium has a Conformance Test Suite
 to check user code conformance to the FACE profiles. The OS can have much
 more available. Looking at this another way, it is not our responsibility
 to ensure conformance to some profile that we did not define.

--
Ticket URL: <http://devel.rtems.org/ticket/4963#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project