Status: Uninitiated.

Introduction: Traditionally applications write their own data management, which may include database code or roll-your-own solutions. Users would benefit from having established and supported database solutions that they can import into their application.

Candidate DBs:

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
SQLite Public Domain C TBD TBD None
csql GPLv2 C++ TBD TBD None
cdb Public Domain C TBD TBD None
tinycdb Public Domain C TBD TBD None

We will need to investigate to see which can be viably brought in and for license compliance.

Goal: Create a package that allows for users to import a database to use with their application. The database code must comply with the RTEMS license.

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.


  • TBD

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.

Last modified on Nov 13, 2018 at 8:25:39 PM Last modified on Nov 13, 2018, 8:25:39 PM