kassane / anotherbuildstep Goto Github PK

verilator(perl) ≠ verilator_bin

References

• https://veripool.org/guide/latest/verilating.html
• https://manpages.org/verilator
• https://veripool.org/guide/latest/exe_verilator.html
• https://github.com/djg/verilated-rs/blob/main/verilator/src/gen.rs
• https://github.com/verilator/verilator/blob/master/verilator-config.cmake.in

Follow

• ziglang/zig#20327
• ziglang/zig#20042
• ziglang/zig#18018
• ziglang/zig#14286
• ziglang/zig#20235
• ziglang/zig#20129
• ziglang/zig#19725
• ziglang/zig#19859
• ziglang/zig#18877
• ziglang/zig#18450
• ziglang/zig#18439
• ziglang/zig#17472
• ziglang/zig#17895
• ziglang/zig#19684
• ziglang/zig#20580
• ziglang/zig#19570

During some tests on #3 it was noticed that when building a binary with rustc + zig cc for cross-compilation, the final binary is not built. Only the host target works!

Why not use cargo-zigbuild?

Currently, no have cargo-support in ABS (AnotherBuildStep) - TODO

Currently, after the first build with zigcc-wrapper getting the target, this value becomes fixed.
Making it necessary to remove the binary in the zig-out/tools folder on each rebuild. (If the target has been changed)

It would be interesting to make zcc reconfigurable by making each execution corresponding to the chosen target.

@import("builtin") get only native target.

tested in ldc2-druntime/gist

---

This is a workaround for a previous problem with Darwin target support.
Note that when using the -mtriple flag, except for Darwin targets, ldc2 does not set the -target flag to CC.
Thus, zig cc will assume that the target is native (which is the default), and will not recognize a specific triple-target.
Likewise, looking at ldc2 internally, it appears that, like rustc, it calls the CC (like arm-none-eabi-gcc) of the selected target.

Reference

• kassane/sokol-d#1

Currently, the available example, it can be seen that non-native build only -betterC mode is supported. (This is not on purpose - I'm not anti-GC).

Based on an experiment using meson (by @denizzzka). I ported to zig-build (with ABS), however the version used did not yet support cross-compilation in D, which had already been corrected previously.

• ldc2-druntime - zig build/gist

To guarantee this possibility, you would need to obtain access to the source code of Druntime and Phobos2, both standalone.
In the case of fortran-runtime (current release already available) is builded using zig c++ and included on:

Consider adding support for the new flang ( taking benefit of the compatibility in some clang flags).

References

• kassane/ffi-flang-zig#1 (build flang-runtime + Fortran_main static/shared for any [llvm] targets)
• Flang.LLVM doc
• mesonbuild/meson#12306
• Flang.cmake

Based on sokol-d/sokol-zig

• floooh/sokol-zig#71