You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Avoid dirtying the source directory during libc build #1401
I'm not sure how we fix this. Polluting source tree with generated files is obviously bad but we need a stable location for c guests that have no access to hashed rust target dir.
One way of improving this would be to use the existing HYPERLIGHT_GUEST_TOOLCHAIN_ROOT mechanism for c guests. We could copy generated headers to HYPERLIGHT_GUEST_TOOLCHAIN_ROOT/include and set the env when building c guests. Then we can prepend the headers from that dir to clang calls.
I believe a proper fix would be to replace just script and cargo with polyglot build system.
changed the title [-]Avoid ditying the source directory during the libc build[/-][+]Avoid dirtying the source directory during the libc build[/+]on Apr 21, 2026
changed the title [-]Avoid dirtying the source directory during the libc build[/-][+]Avoid dirtying the source directory during libc build[/+]on Apr 21, 2026
Activity
[-]Avoid ditying the source directory during the libc build[/-][+]Avoid dirtying the source directory during the libc build[/+][-]Avoid dirtying the source directory during the libc build[/-][+]Avoid dirtying the source directory during libc build[/+]