# at once one spatch process can take around 2.5 GiB of RAM, which can easily eat up all available RAM
# when paired together with parallel
#
- # 2) Make sure spatch can find our includes via -I <dir>, similarly as we do when compiling stuff
+ # 2) Make sure spatch can find our includes via -I <dir>, similarly as we do when compiling stuff.
+ # Also, include the system include path as well, since we're not kernel and we make use of the stdlib
+ # (and other libraries).
#
# 3) Make sure to include includes from includes (--recursive-includes), but use them only to get type
# definitions (--include-headers-for-types) - otherwise we'd start formating them as well, which might be
parallel --halt now,fail=1 --keep-order --noswap --max-args=10 \
spatch --cache-prefix "$CACHE_DIR" \
-I src \
+ -I /usr/include \
--recursive-includes \
--include-headers-for-types \
--undefined SD_BOOT \