Version 7 (modified by Sal, on Nov 13, 2018 at 8:22:15 PM) (diff)

fix and improve format

RTEMS ConfigKit



Status: Uninitiated.

Introduction: Traditionally applications write their own configuration parsers. Users would benefit from having established and supported configuration solutions that they can import into their application.

Candidate configuration parsers:

The fields in this table are as follows:

  • Project - name of project with hyperlink to it.
  • License - software license used. May need to link to license text if dual-licensed or "other".
  • Language - what programming language is this written in?
  • Active - is the project active?
  • OK w/RTEMS Static - Is the license compatible with a statically linked proprietary RTEMS application?
  • OK w/RTEMS Technical - Does the code appear to be feasible to run on RTEMS? Does the code make assumptions that would render it unable to run on RTEMS?
  • Notes - Anything else
Candidate License Language Active OK w/RTEMS Static OK w/RTEMS Technical Notes
libConfuse LGPLv3 C 2012-02-21 / 2010-12-10 TBD None
liblcfg GPLv2 C (C99) 2012-04-05 / 2012-04-05 TBD None
rudeconfig GPLv3 C++ 2007-02-01 / ? TBD None

We will need to investigate what are viable and license-compliant solutions.

Goal: Create a package that allows for users to import a configuration parser to use with their application. The configuration parsing code must comply with the RTEMS license. This project may also be related to ApplicationConfigurationGUI

Requirements: This project is mainly about integrating another project with RTEMS. Familiarity with RTEMS build system, cross-compilation, and the ability to create good documentation are all must-haves.



Miscellaneous Sections

As the project progresses, you will need to add build instructions, etc and this page will evolve from a project description into a HOWTO.


Other sections: If you have more to say about the project that doesn't fit in the proposed sections of this template, feel free to add other sections at will.