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
Currently we manually copy over the str.zig file to any platform written in zig. In the long term we'd want to use some sort of package manager to distribute zig platforms. But in the medium term it would be ideal if we could use a build.zig to reuse the str.zig we use for bitcode generation in the platforms as well, reducing the duplication.
For full context: we can't import the compiler's str.zig directly: zig normally does not allow imports with an arbitrary path.
However, there seems to be no current way to replicate the behavior of zig build-obj with a build.zig file. Our best attempt so far is
Currently we manually copy over the
str.zig
file to any platform written in zig. In the long term we'd want to use some sort of package manager to distribute zig platforms. But in the medium term it would be ideal if we could use abuild.zig
to reuse thestr.zig
we use for bitcode generation in the platforms as well, reducing the duplication.For full context: we can't import the compiler's
str.zig
directly: zig normally does not allow imports with an arbitrary path.However, there seems to be no current way to replicate the behavior of
zig build-obj
with abuild.zig
file. Our best attempt so far isThere are two problems
exe.install
runs into linker issuesobj.install
runs into aunreachable
in the zig std libThis issue seems to ask about something related, but the
emit_bin
flag does not do anything (at least not that I can tell).The text was updated successfully, but these errors were encountered: