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
The primary version [from zigcc-wrapper] available in sokol-d provides only native targeting, unlike the abs implementation (which supports multiple targets1).
According to #49, it is shown that the importC used in the dcimgui module allows ldc2 to process C code (call the C compiler) by using mixed accesses. However, the wasm32 target can't give emcc direct access to ldc2. So cc is not available2 for processing C files.
Here zig cc is starred in importC, making it easily accessible regardless of platform!
For the Windows case (MSVC), ldc2 prefers clang-cl (if available) by default, -gcc=$CC is used with importC.
However, if use D files this will be ignored. Only -linker=$LD can be called.
The primary version [from
zigcc-wrapper
] available in sokol-d provides only native targeting, unlike the abs implementation (which supports multiple targets1).Previous, on windows (wasm32 target) was called msvc (it's wrong!!): https://github.com/kassane/sokol-d/actions/runs/12775927090/job/35613419304#step:10:157
According to #49, it is shown that the importC used in the
dcimgui
module allows ldc2 to process C code (call the C compiler) by using mixed accesses. However, the wasm32 target can't give emcc direct access to ldc2. Socc
is not available2 for processing C files.Here zig cc is starred in importC, making it easily accessible regardless of platform!
Footnotes
https://github.com/kassane/anotherBuildStep/blob/0457a46f52c6151b754437c5b5e0b01856d34fa4/toolchains/zigcc.zig#L41-L153 ↩
https://github.com/kassane/sokol-d/actions/runs/12831642586/job/35782559123?pr=49#step:10:33 ↩
The text was updated successfully, but these errors were encountered: