Unable to use Zig cc compiler

[dimaguy]

Describe the bug
I can't point the extension to use Zig's cc compiler because flags are placed after the file and output location are selected

To Reproduce
Steps to reproduce the behavior:

1. Set C-compiler to zig
2. Append cc to the beginning of C-flags
3. (optionally) set Cpp-compiler to zig and append c++ to beginning of Cpp-flags
4. Find that flags are placed after filenames, so it's all in vain

Expected behavior
Extension will invoke Zig's compilers as if they were gcc or clang

Screenshots

Environment

• VSCode Version: 1.76.2
• OS Version: Windows 11 22H2

Additional context
I also attempted to append cc at the end of C-compiler, but that tries to find a binary named "zig cc" instead

[danielpinto8zz6]

Have you tried with gcc?

[dimaguy]

Yes, gcc works fine, but zig cc provides a more smooth cross compiling experience as well as other QoL improvements

[danielpinto8zz6]

what's the command to compile with zig?

[dimaguy]

what's the command to compile with zig?

zig cc (regular gcc flags)
zig g++ (regular clang flags)

[danielpinto8zz6]

have you tried to put "zig cc" on your compiler?

[dimaguy]

have you tried to put "zig cc" on your compiler?

I have, as I mentioned in the additional context, since it uses an exec call instead of a shell command call, it tries to look for a binary named zig cc, even if I renamed it, would make it so argv[0] would be "zig cc", and therefore, not recognized as the cc subcommand

[danielpinto8zz6]

@dimaguy I'll leave the issue open as an improvement for future release

[dimaguy]

@dimaguy I'll leave the issue open as an improvement for future release

Sure, sounds good to me :)
To be fair all that needs to be done is to reorder flags to be before the filename and output dir, but take your time