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.
Originally posted by @andreiltd in #831 (comment)
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_ROOTmechanism for c guests. We could copy generated headers to HYPERLIGHT_GUEST_TOOLCHAIN_ROOT/includeand 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.
Originally posted by @andreiltd in #831 (comment)