Vdash - dashboard for Autonomi nodes

Apps
264

Hey I’m trying to install on windows 11 but when I enter the cmd cargo install vdash I get an error output " Compiling futures-channel v0.3.30
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 windows_x86_64_msvc (build script) due to 1 previous error
error: could not compile serde (build script) due to 1 previous error
error: could not compile proc-macro2 (build script) due to 1 previous error
error: could not compile windows_x86_64_msvc (build script) due to 1 previous error
error: could not compile syn (build script) due to 1 previous error
error: could not compile rustversion (build script) due to 1 previous error
error: could not compile winapi (build script) due to 1 previous error
error: failed to compile vdash v0.17.8, intermediate artifacts can be found at C:\Users\MINE\AppData\Local\Temp\cargo-installxqLWZH.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path."

anyone know why this is?

1 Like
265

Can you look above this line and see what the “previous error” is.

1 Like
266

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.

267

I found a link here so you could try installing this:

https://aka.ms/vs/17/release/vs_buildtools.exe

If you try please let me know how it goes.

2 Likes
268

Hmmm I installed it and still get the same error:

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.

Compiling icu_properties_data v1.5.0
Compiling equivalent v1.0.1
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 windows_x86_64_msvc (build script) due to 1 previous error
error: could not compile windows_x86_64_msvc (build script) due to 1 previous error
error: could not compile rustls (build script) due to 1 previous error
error: could not compile serde (build script) due to 1 previous error
error: could not compile proc-macro2 (build script) due to 1 previous error
error: could not compile syn (build script) due to 1 previous error
error: could not compile crossbeam-utils (build script) due to 1 previous error
error: could not compile parking_lot_core (build script) due to 1 previous error
error: could not compile rustversion (build script) due to 1 previous error
error: could not compile httparse (build script) due to 1 previous error
error: could not compile winapi (build script) due to 1 previous error
error: failed to compile vdash v0.17.8, intermediate artifacts can be found at C:\Users\MINE\AppData\Local\Temp\cargo-installjEkCQY.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.

269

hey bud any update on how I can get this to install?

270

Sorry, I’ve not been able to look into it. You can pick out one of those error messages and search the web. That’s what I would do but I’m not on Windows so not easy for me to test out.

I’m pretty busy so hopefully you Windows folk can figure it out together, posting on discord might help.

Also, filing an issue at GitHub - happybeing/vdash: A Dashboard for Autonomi Nodes that runs in the terminal is always useful and can get a response.

271

Did you install the cargo correctly? Select number 1-1-1

272

For the avoidance of doubt…

In the latest versions, ‘R’ works as advertised to refresh the nodes that are scanned.

thanks @happybeing

273

I’ve not made any changes that could affect that so I think the issue is probably about context, such as number of nodes being run.

Thanks for the report as always and welcome home!

1 Like
274

I can confirm that it works on windows 11 and windows server 2022 even with higher number of nodes (tested with 40 nodes).

1 Like
275

Any idea how to fix this?

276

Sure it is missing ms c++ build tools.

277

I suggested that: Vdash - dashboard for Autonomi nodes - #267 by happybeing

278

Had that issue on ws2022 build tools solved issue for me. On my w11 didn t had that issue cause i had there installed complete adk for w11 for custom windows 11 image creation. He probably didn’t installed visual studio on his pc but let’s wait for his feedback.

279

He’s already replied above.

280

I read it, as I said visual studio is missing, because with visual studio you get the adk and c++ redistributable, but with visual studio code you don’t.

281

yea I have visual studio on my computer and I’m pretty sure I installed the correct tools maybe I should try to uninstall everything and reinstall it fresh does anyone know what the cmds are to uninstall everything?

and also I am doing this out of the cmd window I dont need to be doing it in powershell right maybe thats the issue?

282

Just re-initiate rustup-init installation and choose 1 (default) when prompts, but run rustup init as an administrator.

1 Like
283

Hmm I have build tools installed Im looking at it on my vs installer rn lol and its giving me this error:

Rust Visual C++ prerequisites

Rust requires the Microsoft C++ build tools for Visual Studio 2013 or
later, but they don’t seem to be installed.

You can acquire the build tools by installing Microsoft Visual Studio.

Download Visual Studio Tools - Install Free for Windows, Mac, Linux

Check the box for “Desktop development with C++” which will ensure that the
needed components are installed. If your locale language is not English,
then additionally check the box for English under Language packs.

For more details see:

MSVC prerequisites - The rustup book

Install the C++ build tools before proceeding.

If you will be targeting the GNU ABI or otherwise know what you are
doing then it is fine to continue installation without the build
tools, but otherwise, install the C++ build tools before proceeding.

Continue? (y/N)

I do have some containers running in docker for the io.net project could this be interfering in anyway?