Yes, for compile crystal program to windows binary, you need to install VS Build Tools.
But after the executable binary is compiled then it can run without any dependencies. I think the later is more important for a window program.
I gave the exes to my users and none of them had any problem running it.
For development currently WSL is still the best way to run crystal in windows.
> WSL is still the best way to run crystal in windows.
WSL is never the best way to do anything, unless the question is "what is the best way to emulate Linux on Windows?". In all other cases, WSL is literally the worst way to do anything.
Re:Crystal Programming Language
by beta-ziliani on Friday September 02, 2022 @10:06AM
(#32691041)
It just requires the build tools. If you use scoop, that entails to:
> run `scoop install vs_2022_cpp_build_tools`
(from the "required libraries" link in https://crystal-lang.org/install/on_windows/)
That just installs Visual Studio:
https://github.com/neatorobito/scoop-crystal/blob/main/bucke...
no thank you.
Re:Crystal Programming Language
by EpicBlackCrayon on Friday September 02, 2022 @06:54PM
(#32696641)
This specifically installs the Visual C++ Compiler and the Windows headers so that you can get a command prompt with all that in your PATH. It is not a full-fat VS install. The difference is something like 20-30GBs for the full VS install vs 1-2GB for these specific components.
Meanwhile, LLVM-MinGW is 108 MB:
now you are just arguing for the sake of argument. unzip the file and it will expand to a 400MB folder.
This isn't really a genuine statement. Currently Crystal Requires a full installation of Visual Studio on Windows:
https://github.com/crystal-lang/crystal/issues/6170