RTEMS ScriptKit

Mentors:

Students:

Status: Some work done.

Introduction: Scripting languages provide a powerful, dynamic, programmer-friendly environment to accomplish tasks, and are especially useful for interactive use. Any such effort should include a small tool to embed the scripting language's compiled bytecode into the rtems image to avoid the overhead of an interpreter and make it immutable. Also required are some test applications to make sure that the scripting language and associated tools work.

Candidate scripting languages and packages:

• Python: See Python.
  • CPython
  • TinyPy?
• Lua: See Lua.

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

{| border="1" style="margin: 1em auto 1em auto;text-align: center;" |+

|Candidate | CPython | TinyPy? | Lua: See Lua

License	Language	Active	OK w/RTEMS Static	OK w/RTEMS Technical	Notes
GPL Compatible	C	2012-09-29	TBD	None
MIT	C	2008-05-22	TBD	None
MIT	C	2012-06-14	TBD	None

|} We will need to investigate what are viable and license-compliant solutions. Of interest are the size and amount of customization required to work with RTEMS.

Goal: Create a package that allows for users to import a scripting language to use with their application. Any runtime 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.

Resources:

Acknowledgements

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.

References

• 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.