Difference between revisions of "Latest LDC binaries for Windows"
m |
m |
||
| Line 1: | Line 1: | ||
| − | As of August 2015, LDC has got support for Windows CI (Continuous Integration) via [https://ci.appveyor.com/project/kinke/ldc AppVeyor]. As convenient side effect, | + | As of August 2015, LDC has got support for Windows CI (Continuous Integration) via [https://ci.appveyor.com/project/kinke/ldc AppVeyor]. As convenient side effect, successful jobs publish the LDC installation directory (as compressed [http://www.7-zip.org/ 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 [https://github.com/ldc-developers/ldc/releases/tag/LDC-Win64-master GitHub release] and download the latest x64/x86 .7z artifact at the bottom. | * Head over to the [https://github.com/ldc-developers/ldc/releases/tag/LDC-Win64-master GitHub release] and download the latest x64/x86 .7z artifact at the bottom. | ||
* Extract it somewhere. | * Extract it somewhere. | ||
| − | * LDC is built with <tt>RelWithDebInfo</tt> CMake configuration, assertions enabled, with a pre-built LLVM 3.9 (from trunk; <tt>Release</tt> CMake configuration, LLVM assertions enabled) and Visual Studio 2015. It's linked dynamically against the MS | + | * Use the executables <tt>bin\ldc2.exe</tt> and/or <tt>bin\ldmd2.exe</tt>. |
| − | + | ||
| + | LDC is built with <tt>RelWithDebInfo</tt> CMake configuration, assertions enabled, with a pre-built LLVM 3.9 (from trunk; <tt>Release</tt> CMake configuration, LLVM assertions enabled) and Visual Studio 2015. It's linked dynamically against the MS Visual C++ runtime, so it requires the [https://www.microsoft.com/en-us/download/details.aspx?id=48145 2015 runtime]. LDC is shipped with debug infos (<tt>bin\ldc2.pdb</tt>). | ||
| + | |||
| + | If you want to use it in combination with Visual Studio 2013, you'll need to [http://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC build LDC yourself]. Apparently there's still a zlib issue in the C parts of the stdlibs preventing successful linking with the VS 2013 libs. | ||
---- | ---- | ||
Revision as of 18:17, 18 August 2016
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 release and download the latest x64/x86 .7z artifact at the bottom.
- Extract it somewhere.
- Use the executables bin\ldc2.exe and/or bin\ldmd2.exe.
LDC is built with RelWithDebInfo CMake configuration, assertions enabled, with a pre-built LLVM 3.9 (from trunk; Release CMake configuration, LLVM assertions enabled) and Visual Studio 2015. It's linked dynamically against the MS Visual C++ runtime, so it requires the 2015 runtime. LDC is shipped with debug infos (bin\ldc2.pdb).
If you want to use it in combination with Visual Studio 2013, you'll need to build LDC yourself. Apparently there's still a zlib issue in the C parts of the stdlibs preventing successful linking with the VS 2013 libs.
