Changes between Version 378 and Version 379 of Developer/OpenProjects


Ignore:
Timestamp:
Feb 13, 2015, 5:01:20 PM (4 years ago)
Author:
Joel Sherrill
Comment:

Add details about adding package recipes to RSB

Legend:

Unmodified
Added
Removed
Modified
  • Developer/OpenProjects

    v378 v379  
    5050   *  Use gcov output as generated by covoar to generate useful reports.  This leverages work by [wiki:GSoC/2011/gcov  support for gcov output] to so tools like gcov and lcov can be used to generate standard coverage reports for RTEMS ([wiki:Projects/GCOVSupport another page here])'' This type of reporting is important for safety certification reviews.
    5151   *  Use gprof output as generated by covoar to generate useful reports.  This is based on the previous project [wiki:GSoC/2011/gprof  Add support for gprof output to covoar]
    52  *  [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] improvements such as building host tools, building a GUI, and improving configuration management and creation.   
     52 *  General [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] improvements such as building more host tools, building a GUI, and improving configuration management and creation.
     53 * Implement recipes in [wiki:TBR/UserManual/RTEMS_Source_Builder RTEMS Source Builder] for all packages in RTEMS [http://git.rtems.org/rtems-addon-packages/ Add on packages], [http://git.rtems.org/rtems-graphics-toolkit/ RTEMS Graphics Toolkit], and packages with just howtos like Lua and LWIP.
    5354 *  Improvements in the [wiki:Developer/Eclipse/Information RTEMS Eclipse Integration].
    5455 *  Compiling RTEMS with [wiki:Projects/CLANG CLANG].
     
    5758 *  [wiki:Projects/ArgoUML  ArgoUML RTEMS Support]
    5859 *  [wiki:Projects/GDB_Python GDB Python] Script support for RTEMS
    59 
    6060
    6161= RTEMS Run-Time Oriented =
     
    119119 *  '''RTEMS Toolkits''' - We are defining collections of libraries and support programs which make it easier to get started for certain types of applications.  We haven't identified all potential toolkits or components.  Each potential component must be evaluated for license and appropriateness for use in an embedded environment like RTEMS.  We also should define some guidelines about creating and maintaining toolkits in general. The eventual goal is to have these toolkits buildable by the RTEMS Source Builder. Here are the toolkits areas identified so far:
    120120  *  Define a generic (RTEMS Source Builder based) infrastructure for building and maintaining toolkits.
    121   *  RTEMS Add ons - [http://git.rtems.org/rtems-addon-packages/ Add on packages] for RTEMS.
    122121  *  [wiki:Projects/BenchmarkKit RTEMS BenchKit] - benchmark programs for RTEMS
    123122  *  [wiki:Projects/ApplicationConfigurationKit RTEMS ConfigKit] - configuration file parsing libraries