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
Hello and first of thank you for this awesome toolchain!
In order to use this zig toolchain approach for embedded development it would be very helpful to be able to target arm-none-eabi, or I guess in zig targets arm-freestanding-eabi.
I have then downloaded the zig 0.11 toolchain and ensured that the abi and cpus which would be targeted have support via the output of zig targets; support for the abi eabi and the target processors in my case (cortex_m4 and cortex_m7) is present.
I looked through the addition of the wasm target: #165 and the current codebase to see what would need to be done.
Are there any plans to add support for arm and/or freestanding targets?
Are the wrappers strictly necessary or would it be feasible to skip using the wrappers in order to be able to specify more targets such as arm-freestanding-eabi with different values for -mcpu?
Thank you in advance,
Daniel Gunzinger
The text was updated successfully, but these errors were encountered:
Hello and first of thank you for this awesome toolchain!
In order to use this zig toolchain approach for embedded development it would be very helpful to be able to target
arm-none-eabi
, or I guess in zig targetsarm-freestanding-eabi
.I see
arm
has Tier 1 support in the zig ecosystem: https://ziglang.org/download/0.11.0/release-notes.html#Tier-1-SupportI have then downloaded the zig 0.11 toolchain and ensured that the abi and cpus which would be targeted have support via the output of
zig targets
; support for the abieabi
and the target processors in my case (cortex_m4
andcortex_m7
) is present.I looked through the addition of the wasm target: #165 and the current codebase to see what would need to be done.
Are there any plans to add support for arm and/or freestanding targets?
Are the wrappers strictly necessary or would it be feasible to skip using the wrappers in order to be able to specify more targets such as
arm-freestanding-eabi
with different values for-mcpu
?Thank you in advance,
Daniel Gunzinger
The text was updated successfully, but these errors were encountered: