Difference between revisions of "Latest LDC binaries for Windows"
m |
m (LLVM upgraded to v5.0.1) |
||
| Line 5: | Line 5: | ||
* Use the executables <tt>bin\ldc2.exe</tt> and/or <tt>bin\ldmd2.exe</tt>. | * Use the executables <tt>bin\ldc2.exe</tt> and/or <tt>bin\ldmd2.exe</tt>. | ||
| − | LDC is built with <tt>Release</tt> CMake configuration, assertions enabled, with a [https://github.com/ldc-developers/llvm/releases/tag/ldc-v5.0. | + | LDC is built with <tt>Release</tt> CMake configuration, assertions enabled, with a [https://github.com/ldc-developers/llvm/releases/tag/ldc-v5.0.1 pre-built LLVM 5.0.1] (<tt>Release</tt> CMake configuration, LLVM assertions enabled) and Visual Studio 2017. |
For linking, you'll need MS Visual C++ 2015 or 2017, either by installing [https://www.visualstudio.com/downloads/ Visual Studio] or the stand-alone [http://landinghub.visualstudio.com/visual-cpp-build-tools Visual C++ Build Tools]. | For linking, you'll need MS Visual C++ 2015 or 2017, either by installing [https://www.visualstudio.com/downloads/ Visual Studio] or the stand-alone [http://landinghub.visualstudio.com/visual-cpp-build-tools Visual C++ Build Tools]. | ||
Revision as of 12:19, 21 January 2018
As of August 2015, LDC has got support for Windows CI (Continuous Integration) via AppVeyor. As convenient side effect, successful jobs publish the LDC installation directory (as compressed 7-Zip archive) as GitHub release artifact, downloadable for you guys and thus saving you the hassle of building LDC yourselves:
- Head over to the GitHub CI release and download a Windows .7z artifact.
- Extract it somewhere.
- Use the executables bin\ldc2.exe and/or bin\ldmd2.exe.
LDC is built with Release CMake configuration, assertions enabled, with a pre-built LLVM 5.0.1 (Release CMake configuration, LLVM assertions enabled) and Visual Studio 2017.
For linking, you'll need MS Visual C++ 2015 or 2017, either by installing Visual Studio or the stand-alone Visual C++ Build Tools.
