vx version
0.9.31
Operating system
Windows
Rust version (if building from source)
No response
Steps to reproduce
Steps to reproduce
Create a project folder and add vx.toml:
toml
[tools]
ninja = "latest"
vcpkg = "latest"
clang-cl = "latest"
cl = "latest"
[settings]
auto_install = true
cache_duration = "7d"
Run vx setup and vx dev.
Inside vx dev, run cl --version and clang-cl --version.
Questions
Is vcpkg supposed to be managed by vx, or is it considered a "system tool" that should be installed separately?
Should clang-cl be installed via the llvm tool instead of directly?
Is the PATH issue a bug or a limitation of vx on Windows?
Shell: CMD\
Additional context
This is my first issue on GitHub, so please let me know if I should post this elsewhere (Discussions, etc.)
Expected behavior
After entering vx dev, I expect all tools defined in vx.toml to be available directly in the terminal (i.e., added to PATH), so I can run cl --version or clang-cl --version without the vx prefix.
Additional issues
vx lock fails for clang-cl and vcpkg. I get an error saying it can't resolve them.
vcpkg not visible in vx list — after running vx install vcpkg, it doesn't appear in the list of installed tools, but I can still use it via vcpkg --version.
Multiple exit needed — I can enter vx dev multiple times and need to type exit twice to fully leave the shell. Is this expected behavior?
Actual behavior and logs/traceback
ninja --version works without vx prefix - work
vcpkg --version works without vx prefix - work
cl --version → "cl" is not recognized as an internal or external command - not work
clang-cl --version → same error - not work
However, running vx cl --version and vx clang-cl --version inside vx dev works and shows the correct version.
Checklist
vx version
0.9.31
Operating system
Windows
Rust version (if building from source)
No response
Steps to reproduce
Steps to reproduce
Create a project folder and add vx.toml:
toml
[tools]
ninja = "latest"
vcpkg = "latest"
clang-cl = "latest"
cl = "latest"
[settings]
auto_install = true
cache_duration = "7d"
Run vx setup and vx dev.
Inside vx dev, run cl --version and clang-cl --version.
Questions
Is vcpkg supposed to be managed by vx, or is it considered a "system tool" that should be installed separately?
Should clang-cl be installed via the llvm tool instead of directly?
Is the PATH issue a bug or a limitation of vx on Windows?
Shell: CMD\
Additional context
This is my first issue on GitHub, so please let me know if I should post this elsewhere (Discussions, etc.)
Expected behavior
After entering vx dev, I expect all tools defined in vx.toml to be available directly in the terminal (i.e., added to PATH), so I can run cl --version or clang-cl --version without the vx prefix.
Additional issues
vx lock fails for clang-cl and vcpkg. I get an error saying it can't resolve them.
vcpkg not visible in vx list — after running vx install vcpkg, it doesn't appear in the list of installed tools, but I can still use it via vcpkg --version.
Multiple exit needed — I can enter vx dev multiple times and need to type exit twice to fully leave the shell. Is this expected behavior?
Actual behavior and logs/traceback
ninja --version works without vx prefix - work
vcpkg --version works without vx prefix - work
cl --version → "cl" is not recognized as an internal or external command - not work
clang-cl --version → same error - not work
However, running vx cl --version and vx clang-cl --version inside vx dev works and shows the correct version.
Checklist