summaryrefslogtreecommitdiffstats
path: root/posix-compliance (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-02-28waf: Add support for extra and excluded sources.Chris Johns1-1/+2
2019-02-28Add unicode support for commonly used characters like copyright.Chris Johns1-2/+4
- This change makes the copyright character easier to see on editors lacking good unicode rendering support, ie terminals.
2019-02-28waf: Fix python3 issues.Chris Johns1-1/+1
- Found after updating to FreeBSD-12.0 which defaults to Python3.
2019-02-15Use pathto() on the genindex URL to make it relative.Chris Johns1-2/+0
2019-02-13waf: Remove as many sys path hacks as we can.Chris Johns1-11/+7
There are still sys.path hacks in the conf.py files. They cannot be removed because the instance of python running the sphinx-build command does not see our top level path hacks. I looked at using PYTHONPATH but I could not figure out how to set a process environ var for a waf build instance.
2019-02-08build: Prepend project common pathSebastian Huber2-2/+2
This avoids conflicts with standard packages such as PIL (Python Imaging Library).
2019-01-14Reformat and update copyright and license noticesSebastian Huber1-7/+4
For everything before 2015 an OAR copyright is assumed. Later copyright notices are based on Git commits on a best effort basis. The copyright notices of the "RTEMS Software Engineering Handbook" and the "RTEMS CPU Architecture Supplement" are incomplete.
2019-01-11Simplify SPDX-License-Identifier commentSebastian Huber4-4/+4
2019-01-11Remove superfluous "All rights reserved."Sebastian Huber1-1/+0
2019-01-11Use standard format for copyright linesSebastian Huber2-3/+2
2019-01-09Add common header.rst to reduce copy and pasteSebastian Huber1-23/+1
2018-12-09posix-compliance: Change utimes() from sys/times.h to sys/time.hMarçal Comajoan Cara2-8/+8
In the RTEMS POSIX 1003.1 Compliance Guide it says: The following methods and variables in <sys/times.h> are supported: - times() - utimes() But according to the official POSIX Specifications http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_times.h.html, <sys/times.h> only declares times(), and utimes() is decleared by <sys/time.h> (notice that it's time, not times) according to http://pubs.opengroup.org/onlinepubs/9699919799/functions/utimensat.html and http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_time.h.html. This patch fixes this error. This work was part of GCI 2018.
2018-10-19Update the copyright year.Chris Johns1-1/+1
2018-08-21build: Fix indexing so it works on HTML and PDF.Chris Johns2-5/+1
- Remove all genindex.rst files, these are generated and should not exist in our source. - Fix the HTML templates so the local specialisation works. - Add a index link to the sidebar for HTML. Note, there is no TOC entry for the index in the PDF output and I cannot figure out how to add one. Closes #3503
2018-03-09Update the POSIX Compliance Tracking Spreadsheet. Add standards.Joel Sherrill6-1208/+1434
This update adds the following: C11 Programming Language Standard FACE Technical Standard Edition 3.0 (four profiles) Software Communication Architecture Specification 2.2.2 (one profile) Software Communication Architecture Specification 4.1 (three profiles)
2018-03-09posix-compliance: Add description of standardsJoel Sherrill3-5/+84
2017-11-12Add indexes to all documents.Chris Johns2-2/+5
Update #3229.
2017-11-09Change RTEMS version to 5Sebastian Huber1-2/+2
Update #3220.
2017-10-13posix-compliance: Latex does not like an empty glossary.Chris Johns1-0/+5
2017-10-13posix-compliance: Reference the generated content via the include file.Chris Johns5-7/+24
- Move the copyright to the top of the generated file. - Add a glossary and references section.
2017-10-12posix-compliance: Fix the pdflatex file created by Sphinx.Chris Johns1-1/+1
2017-10-12build: Remove the grouping in posix-compliance.Chris Johns1-1/+0
2017-10-12posix-compliance: Add automatic generation of the ReST file from CSV data.Chris Johns3-1/+291
Closes #3177.
2017-10-12New version of POSIX Compliance GuideJoel Sherrill8-0/+1412
This is a replacement of the POSIX 1003.1 Compliance Guide. It will be generated from a .csv file. Updates #3177.