C Library: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content deleted Content added
→Implementations: removed extraneous sentence |
Clarification about "freestanding" libraries |
||
| Line 16: | Line 16: | ||
GCC defaults to a hosted implementation, but can switch to a freestanding one with the <tt>-ffreestanding</tt> argument. |
GCC defaults to a hosted implementation, but can switch to a freestanding one with the <tt>-ffreestanding</tt> argument. |
||
===What's the Point of Freestanding?=== |
|||
The point of "freestanding" C libraries is this: all Clib packages are supposed to provide one that contains the listed .h files. If you are writing your kernel in |
|||
C (or C++), you should care about portability. Including these header files in your kernel and '''using''' the provided macros, defines |
|||
and typedefs will dramatically increase the portability of your code, and you probably won't regret it later. |
|||
==Implementations== |
==Implementations== |
||