| 1 | = GCov Reports = |
| 2 | |
| 3 | |
| 4 | [[TOC(Developer/Projects/Open/GCovReports, depth=2)]] |
| 5 | |
| 6 | |
| 7 | '''Mentors:''' Joel Sherrill |
| 8 | |
| 9 | '''Students:''' Past, Present, and Potential Students |
| 10 | |
| 11 | '''Status:''' Uninitiated. |
| 12 | |
| 13 | '''Introduction:''' 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. |
| 14 | |
| 15 | '''Goal:''' Concise statement of the overall goal of the project. Refine this initial statement to include: project deliverables (code, docs, testing), required/suggested methodology, standards of quality, possible goal extensions beyond the main objective. |
| 16 | |
| 17 | '''Requirements:''' List the requirements and level of expertise you estimate are required by the developer tackling this project will have to have: Required level of programming language(s), specific areas of RTEMS or tools, level of familiarity with RTEMS, cross-development, GNU/Linux, etx., development/documentation/testing tools, mathematical/algorithmic background, other desirable skills. |
| 18 | |
| 19 | '''Resources:''' Current RTEMS developers, papers, etc that may help you in this project. |
| 20 | |
| 21 | '''Acknowledgements''' |
| 22 | * who helped and did work |
| 23 | |
| 24 | = Miscellaneous Sections = |
| 25 | |
| 26 | As the project progresses, you will need to add build instructions, etc and this page will evolve from a project description into a HOWTO. |
| 27 | |
| 28 | = References = |
| 29 | * TBD |
| 30 | |
| 31 | '''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. |