Summary: I've noticed one problem is that the user includes `stdint.h` the compiler will do `#include_next <stdint.h>` potentially into a conflicting implementation on systems with multiple headers installed. The `clang` header is standards compliant and works with `clang` and `gcc` which are both of our targets, so I simply copied it here. This has the effect of including `stdint.h` on clang / LLVM libc behaving the same as `-ffreestanding`.
19 lines
449 B
Plaintext
19 lines
449 B
Plaintext
set(TARGET_PUBLIC_HEADERS
|
|
libc.include.ctype
|
|
libc.include.fenv
|
|
libc.include.errno
|
|
libc.include.float
|
|
libc.include.stdint
|
|
libc.include.inttypes
|
|
libc.include.math
|
|
libc.include.stdckdint
|
|
libc.include.stdbit
|
|
libc.include.stdlib
|
|
libc.include.string
|
|
libc.include.strings
|
|
libc.include.search
|
|
|
|
# Disabled due to epoll_wait syscalls not being available on this platform.
|
|
# libc.include.sys_epoll
|
|
)
|