Closed ikskuh closed 1 year ago
I didn't understand what the change was for to split some of the functions into a seperate
freestanding
library, what was that for?
It's for making ziglibc work on freestanding targets (???-freestanding-???
) which don't expose any I/O functionality, as no OS is present. freestanding is also a libc profile that should be supported in general (as it's specced by the C standard).
This is reqiured to use ziglibc on a non-standard target like a microcontroller, a custom OS and so on
Superseeded by #12
I've split this PR into 2 commits and merged them to main, one to update the build files (I also made all the build files work) and one to add the
relpath
trick inziglibcbuild.zig
.I didn't understand what the change was for to split some of the functions into a seperate
freestanding
library, what was that for?