The C standard library provides string manipulation (string.h), basic I/O (stdio.h), memory allocation (stdlib.h), and other basic functionality to C programs. The interface is described in the C standard, with further additions described in POSIX as well as vendor extensions. On Unix platforms, the library is named libc and is linked automatically into every executable.
You need a C standard library implementation with the necessary features to run C programs on your operating system. C++ programs can usually use the C standard library as well and the C++ implementation is normally built on top of libc. It is possible to use the C standard interface in a kernel if the library implementation supports this.
Freestanding and Hosted
There are two flavors of the C compilation environment: Hosted, where the standard library is available; and freestanding, where only a few headers are usable that contains only defines and types. The hosted environment is meant for user-space programming while freestanding is meant for kernel programming. The hosted environment is default, but you can switch to the freestanding by passing -ffreestanding to your compiler.
The __STDC_HOSTED__ macro expands to 1 on hosted implementations, or 0 on freestanding ones. The freestanding headers are: <float.h>, <iso646.h>, <limits.h>, <stdalign.h>, <stdarg.h>, <stdbool.h>, <stddef.h>, <stdint.h>, and <stdnoreturn.h>. You should be familiar with these headers as they contain useful declarations you shouldn't do yourself. GCC also comes with additional freestanding headers for CPUID, SSE and such.
There are several open-source C library packages available, and using one may be a viable solution for you. All of them will require some degree of modification to suit your needs.
There is a comparison table of some of these.
- Main article: Creating a C Library
The best option, in terms of code quality and integration with your operating system, is to write your own C library. You can aim for making a clean and high-quality implementation that follows standards well. It will integrate cleanly with your kernel as no portability layer is needed. You can be secure and robust. You can surpass the limits of what you can do with existing implementations. You can add vendor-extensions that replace bad interfaces and do things better. You can break a lot of code because you followed the standards and applications didn't, then fix the applications as well. It can be better than the competition if you make that your goal.
This is the idealist path and most in the osdev spirit. It has a lot of advantages, but has the steep price of requiring a lot of effort. This may very well be worth it if your goal is to make a good operating system, not just a operating system. You don't have to be a libc expert when starting out, but you'll be one when you're done. You might just realize much of the competition out there isn't very good.
Creating your own minimal C library is relatively easy. Providing all the primitives needed by real program is a much larger task, but straightforward as you can attempt to cross-compile the software and implement all the missing features causing compilation errors.
- GPL license
- Should be absolutely complete (even has all the bloat)
- Supports almost every architecture
- Generates large programs
- MIT license
- No kernel portability layer, uses the Linux system calls directly. You can add your own layer between musl and the kernel to translate Linux system calls into native system calls, which is the method used by midipix.
- A full set of math and printf functions
- Support for about 1200 functions
- Many system calls needs to be implemented as it assumes you are a full Linux
- The license is unrestricted (not GPL or LGPL), but each file likely has a different copyright notice.
- Requires threading, so is more appropriate for a runtime library
- About 400 functions supported
- Creative Commons Zero license (public domain)
- Under active development, and not at full working release 1.0 yet
- Good for linking into kernels
- Support for about 120 functions, currently
- 10 (plus one optional) required syscalls need to be implemented
- No ASM -- should be fully portable
- LGPL license
- GPL 2 license
- Optimized for small size
- Many features missing
- BSD license
- No support for locales
- No libthread_db or libm implementation
- Its own smallish implementation of pthreads based on Linux futexes
- Support for x86, ARM and ARM thumb CPU instruction sets and kernel interfaces
- ISC license.
- Implements large parts of the C and POSIX standards.
- Subset can be built as the kernel standard library libk.
- Supports over 70 pieces of third party software.
- The source code is well organized and fairly straightforward.
- Static linking only at this time.
- Part of Sortix and assumes the Sortix system call ABI, which makes it cleaner.
- Some modification is required to support other system call ABIs depending on how similar the ABI is.
- Public domain
- Written for the new C11 standards.
- Under development since November 2014. Currently still severely lacking in functionality.
Especially if you want to roll your own C lib, you may want to buy the ISO/IEC 9899 specification to work from. It is not free. Expect a PDF to cost somewhere around $250 (US) or 250 Swiss Francs, depending on currency conversions.
On the other hand, the INCITS republishes these standards for a lot less: INCITS/ISO/IEC 9899-2011 can be purchased for about $60 (US) from the ANSI web store or from TechStreet.
The older standards (C89/C90, C99) are not commercially available anymore. To find the current standard, go to one of the following sites and search for document "ISO/IEC 9899".
By the way, you can use latest draft of standard, it's publicly available for free and exactly the same as approved version. This is a path chosen by most open-source software, especially GCC and GLIBC relies on drafts published by ISO/IEC. Latest version of C2011 draft has the name ISO/IEC 9899 N1570 and can be downloaded here (PDF)