mirror of
https://github.com/FreeRTOS/FreeRTOS-Kernel.git
synced 2025-10-14 00:37:44 -04:00
a9680a54cf
* Recently the prototypes for the application hook functions were moved out of the kernel .c files and into the .h files. That changes results in compile time warnings for projects that provide hook functions with a slightly different prototype - in particular where signed char * is used in place of just char * as an older FreeRTOS coding convention required chars to be explicitly qualified as signed or unsigned. This checkin fixes the warnings by ensuring the signature of implemented hook functions matches the signature of the prototypes. |
||
|---|---|---|
| .. | ||
| Demo | ||
| License | ||
| Source@805b15a022 | ||
| Test | ||
| History.txt | ||
| links_to_doc_pages_for_the_demo_projects.url | ||
| readme.txt | ||
Directories: + The FreeRTOS/Source directory contains the FreeRTOS source code, and contains its own readme file. + The FreeRTOS/Demo directory contains a demo application for every official FreeRTOS port, and contains its own readme file. + See http://www.freertos.org/a00017.html for full details of the directory structure and information on locating the files you require. The easiest way to use FreeRTOS is to start with one of the pre-configured demo application projects (found in the FreeRTOS/Demo directory). That way you will have the correct FreeRTOS source files included, and the correct include paths configured. Once a demo application is building and executing you can remove the demo application file, and start to add in your own application source files. See also - http://www.freertos.org/FreeRTOS-quick-start-guide.html http://www.freertos.org/FAQHelp.html