Version 1 (modified by eshan dhawan, on May 10, 2020 at 9:43:02 AM) (diff)


POSIX Compliance

Student(s): Eshan Dhawan.

Mentors: Joel Sherrill, Vaibhav Gupta, Aditya Upadhyay.

Ticket: POSIX Compliance

Development Blog: [TBD]

1) - Introduction to Project

1.1) - Project Description

Portable Operating System Interface (POSIX) is a set of standards that are defined by the IEEE society. It defines various APIs along with command-line interfaces and utility interfaces to maintain software compatibility between various operating systems. POSIX Compliance provides maximum flexibility to write applications that can be executed on various platforms and increases the portability of code. The RTEMS developers community has kept it well compliant with various standards. But with the advancement of time and technology, its up-gradation becomes an interminable task. POSIX Compliance will require to add various APIs and different interfaces as specified by the POSIX IEEE Standard 1003.1TM. They can either be ported from other platforms with a compatible license or will be written from scratch as required. There would be a need to write architecture-specific code as well. In RTEMS, Newlib provides the C library including libm, so for improving POSIX Compliance, we would also be required to add various functions and headers to Newlib as well. Newlib also requires math headers also

1.2) - Project Goal


2) - Project Setup


3) - Project Sandboxing On My System