Windows (x64/x86-64; ARM64; IA-32)

[ylluminate]

Please comment with or ask questions about your experience or trouble installing V on Microsoft Windows operating systems.

IMPORTANT: 32-bit / IA-32 / x86 usage is NOT officially supported.

[Wajinn]

1. If attempting Git and clone, Windows users can get the following types of errors.

• Errors because v_win.c doesn't exits (can be downloaded from https://github.com/vlang/vc)

• Errors because the TCC folder doesn't exist or can't be downloaded (https://github.com/vlang/tccbin)

• Errors related to Git, because it's not set in the Path or \cmd\git.exe can't be found

• Path: https://helpdeskgeek.com/windows-10/add-windows-path-environment-variable/

• \cmd\git.exe: Location can depend on the type of Git software a person is using.

2. The version of TCC used by V doesn't contain the full WinAPI, maybe it should or have an alternate that does.

• In various cases compile errors can occur because of missing libraries.

• Note: The full WinAPI can be found here- https://download-mirror.savannah.gnu.org/releases/tinycc/. However, updating TCC to use the full WinAPI can cause errors with the existing TCC used by V. So, the person should know what they are doing.

3. The ZIP version of V doesn't contain the vc folder, that has v.c and v_win.c (https://github.com/vlang/vc)

• This can cause errors when using V's update.

4. V's "install" for modules can fail because the metadata is missing.

• Probably it should be clarified in the documentation that if the metadata is missing that the person has to do a manual install by putting the folder at \vlib or \.vmodules.

[JalonSolov]

Did you run make.bat, per the instructions? That downloads tcc, clones v_win.c, etc.

[medvednikov]

make.bat is always supposed to download all of this and build V correctly.

If it doesn't please submit a bug report.

[Wajinn]

This was the result of helping a friend install V. It could be that their firewall rules or anti-virus (malware protection) were triggered and was blocking the download (particularly a .bat file). Which would make sense. Could be that using Git and clone, since there is no TCC or VC, there would be an attempt to download and something in the process failed or was blocked.

Still, this possibility is good to know, because it could be something to make new users aware of so that they can temporarily disable or make exceptions to various firewall or anti-virus programs during the install process.

[Blackwingxxxx]

i tried to run this(./v run examples/hello_world.v) command but got this error

'.' is not recognized as an internal or external command, operable program or batch file.

then I tried v.exe,
it showed this which i think it means it works

\ \ / / | Welcome to the V REPL (for help with V itself, type exit , then run v help ). \ \/ / | Note: the REPL is highly experimental. For best V experience, use a text editor, \ / | save your code in a main.v file and execute: v run main.v \ / | V 0.2.4 940c78b . Use list to see the accumulated program so far. \__/ | Use Ctrl-C or exit to exit, or help to see other available c

so in v.exe i tried the first command,
thi time it gave this error:

>>> ./v run examples/hello_world.v error: unexpected token /, expecting name 5 | import math 6 | 7 | println(./v run examples/hello_world.v) |

[Blackwingxxxx]

it actually showed this when I ran v.exe ut in the post it came messed up so im sending this screenshot

[JalonSolov]

Please follow these directions for a more enjoyable V experience: https://github.com/vlang/v#symlinking

[satyajitgreat]

when i run v program it gives something like this :-failed CreateProcess: %1 is not a valid Win32 application

[ddkwork]

how to set v http proxy for this?

[Wajinn]

how to set v http proxy for this?

It appears you have posted in the wrong thread about an unrelated matter.

[brvtalcake]

I had an issue when installing V, because git wasn't added to PATH. Make sure to add the bin folder of Git to path

[daddycocoaman]

Old discussion but I thought I would post here since it's relevant. I sometimes work from an Windows ARM64 device, which V does not officially support. I tried to compile V using make.bat -msvc but I got the following error:

 > Attempting to build "./v_win_bootstrap.exe" (from v_win.c) with MSVC
v_win.c
vc/v_win.c(860): fatal error C1189: #error:  "Unknown architecture endianness"

Turns out that _M_ARM64 is not defined in v_win.c, I manually added it to the condition that returns that error and removed tcc download that occurs on build, and successfully compiled V on Windows ARM64. I don't fully understand where tc repo gets auto generated from but maybe someone who knows can add the check.

I ran most of the test suite and everything appears to work (output was similar to the AMD64 tests on Windows), but it's a lot slower (as all the docs and output tell you).

The only slight issue is that the V binaries that are compiled are x64 and not ARM native because the msvc_windows.v file doesn't account for ARM64 host architecture, so that's something that can maybe be added if V devs want to add Windows ARM64 support.

[daddycocoaman]

Also, v-analyzer works as well after running v ls --install.

[daddycocoaman]

Looks like I was able to compile an ARM64 binary on Windows ARM by using the WOA version of clang and X64 version of V, which makes complete sense now that I think about it. 🫠

v -cc clang -prod .\src\windows\test.v

clang version 18.1.2
Target: aarch64-pc-windows-msvc
Thread model: posix
InstalledDir: C:\Users\*\.local\clang\bin