As I can see Visual Studio is installed correctly the things which missing are:
MS V C++ redistributable latest can be downloaded from ms here
Debug Runtime isn’t mandatory if you will be just running nodes.
I believe step 2c should have installed this from the README.
@Profess I understood that you followed this so if you know what went wrong please let me know in case I can improved the README.
If step 2 installed this than it should be on the list.
It is strange, because according to the instructions 2 times I downloaded and installed MS V C++ is this file VC_redist.x64.exe,So I don’t know why it’s not on the list.
I will install again.
Unfortunately, after another download and installation of the MS V C++ file in the list, nothing has changed, and the error repeats:
PS C:\Users\gggg> Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -match 'Microsoft Visual C*'} | Select-Object DisplayName, DisplayVersion, Publisher, InstallDate | Format-Table -AutoSize
DisplayName DisplayVersion Publisher InstallDate
----------- -------------- --------- -----------
Microsoft Visual C++ 2022 X64 Additional Runtime - 14.40.33810 14.40.33810 Microsoft Corporation 20240712
Microsoft Visual Studio Installer 3.11.2167.20057 Microsoft Corporation 20240712
Microsoft Visual C++ 2022 X64 Minimum Runtime - 14.40.33810 14.40.33810 Microsoft Corporation 20240712
PS C:\Users\gggg> cargo install vdash
Updating crates.io index
Installing vdash v0.17.9
Updating crates.io index
Locking 271 packages to latest compatible versions
(...)
Compiling version_check v0.9.4
error: linker `link.exe` not found
|
= note: program not found
note: the msvc targets depend on the msvc linker but `link.exe` was not found
note: please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option.
note: VS Code is a different product, and is not sufficient.
error: could not compile `windows_x86_64_msvc` (build script) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `proc-macro2` (build script) due to 1 previous error
error: failed to compile `vdash v0.17.9`, intermediate artifacts can be found at `C:\Users\gggg\AppData\Local\Temp\cargo-installVrDwJ8`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
I wonder if the problem is not due to the installation location of the MS V C++ file, which in my case is installed on the E: drive, and in the error description it says:
error: failed to compile `vdash v0.17.9`, intermediate artifacts can be found at `C:\Users\gggg\AppData\Local\Temp\cargo-installVrDwJ8`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
Does it have an impact?
Do you have link.exe under the : C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\bin\Hostx64\x64
Your c drive is not root one?
Please provide infor from (powershell as admin):
write-host $env:systemroot
Please try the following:
Download Build tools for VS 2019 (Visual Studio Older Downloads - 2019, 2017, 2015).
During installation select the C++ tools
Restart the pc.
Try cargo install vdash.
I don’t have link.exe under this location.
The C: drive is the head drive.
PS C:\Users\gggg> write-host $env:systemroot
C:\WINDOWS
Try this than.
I downloaded and installed Build tools for VS 2019 (Visual Studio Older Downloads - 2019, 2017, 2015 ),To do this, I had to uninstall the earlier version, and then installed the Visual C++ Redistribution Package, also successfully, and then restarted the computer.
Unfortunately, after typing the cargo install vdash command, the same error still appears:
error: linker `link.exe` not found
|
= note: program not found
note: the msvc targets depend on the msvc linker but `link.exe` was not found
note: please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option.
note: VS Code is a different product, and is not sufficient.
error: could not compile `windows_x86_64_msvc` (build script) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `proc-macro2` (build script) due to 1 previous error
error: failed to compile `vdash v0.17.9`, intermediate artifacts can be found at `C:\Users\gggg\AppData\Local\Temp\cargo-installfB9GE7`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
Did you During installation selected to install the C++ tools
I installed according to the link this particular file: Azure DevOps Services | Sign In
and Visual C++ redistribution package from this site: Latest supported Visual C++ Redistributable downloads | Microsoft Learn,
I have chosen for Visual Studio 2015, 2017, 2019 and 2022, x64 architecture - this particular file https://aka.ms/vs/17/release/vc_redist.x64.exe
Unfortunately, after two days of struggling, when I finally managed to find the required files (more precisely, 3 files, because Testing tools core features does not appear in the list of C++ Tools), it turned out that I need more than 4 GB of space on the C: drive to install C++ Tools, even though I already changed the target drive to the E: drive during the installation of Visual Studio, since I do not have that much space on the C: drive (and this is probably why Launchpad does not work with me), I cannot install the required tools.
I understand that in this arrangement I have no chance to install vdash?
I think there’s something odd going on because to use vdash you will need to compile, which means you need Rust installed. It is Rust which requires the ‘redistributables’ installed, but they will be quite small.
As far as I can see you’ve tried to install them but they aren’t being found. I don’t know why.
Another way would be for someone who has compiled vdash for Windows to send you the binary. I can’t do that right now but may be able to in the future. Perhaps in the mean time someone else will do so first.
Did you see this:
I don’t remember if you and @R43 considered this? If not I suggest you follow up with @rusty.spork in case he can help.
I just marked what R43 mentioned and for that MSVC version 143 - VS 2022 which is essential and this requires 4.05 GB of space on the C drive:
I’ll take a look, although this bug is recognized by the team, because I ran into it myself in testing, and it has since been determined that in order to install the client and nodes on Windows, it was necessary to install MS Visual C++ Redistributable.
Redistributable is required for rust and any type of compiling. I am providing you with the experience that i gained from my previous installations.
Do you have any idea yet how to install these necessary tools? Happybeing writes that they should be quite small, and in my case about 9.6 GB is required.
Did installing these tools take so much space in your case too?
Mine took much more, i have several sdk’s installed for other purposes.
What i can do is to provision clean win 10 or 11 vm and create step by step tutorial with all information regarding disk space, linker etc.
Total disk space usage for one sdk and build tools (that is what include linker) is 2.47GB of space.
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.40.33807\bin\Hostx64\x64