Difference between revisions of "Latest pre-built LDC for Win64"
(no MSVC environment required anymore; clarify VS 2015 requirement) |
m (The CI build is portable now.) |
||
| Line 2: | Line 2: | ||
* Head over to the [https://github.com/ldc-developers/ldc/releases/tag/LDC-Win64-master GitHub release] and download the latest .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 .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.7 (<tt>Release</tt> CMake configuration, LLVM assertions enabled) and Visual Studio 2015. It's linked dynamically against the MS C runtime, so it requires the [https://www.microsoft.com/en-us/download/details.aspx?id=48145 2015 runtime]. | * LDC is built with <tt>RelWithDebInfo</tt> CMake configuration, assertions enabled, with a pre-built LLVM 3.7 (<tt>Release</tt> CMake configuration, LLVM assertions enabled) and Visual Studio 2015. It's linked dynamically against the MS C runtime, so it requires the [https://www.microsoft.com/en-us/download/details.aspx?id=48145 2015 runtime]. | ||
* If you want to use it in combination with Visual Studio 2013, you'll have to remove the default switch <tt>-Llegacy_stdio_definitions.lib</tt> in the configuration file <tt>etc\ldc2.conf</tt>. But apparently there's still a zlib issue in the C parts of the runtimes preventing successful linking with the VS 2013 linker. So currently, you'll need to build LDC yourself if you want to use it with VS 2013. | * If you want to use it in combination with Visual Studio 2013, you'll have to remove the default switch <tt>-Llegacy_stdio_definitions.lib</tt> in the configuration file <tt>etc\ldc2.conf</tt>. But apparently there's still a zlib issue in the C parts of the runtimes preventing successful linking with the VS 2013 linker. So currently, you'll need to build LDC yourself if you want to use it with VS 2013. | ||
Revision as of 11:36, 11 October 2015
As of August 2015, LDC has got support for Windows CI (Continuous Integration) via AppVeyor. As convenient side effect, the debug job publishes the LDC installation directory (a 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 .7z artifact at the bottom.
- Extract it somewhere.
- LDC is built with RelWithDebInfo CMake configuration, assertions enabled, with a pre-built LLVM 3.7 (Release CMake configuration, LLVM assertions enabled) and Visual Studio 2015. It's linked dynamically against the MS C runtime, so it requires the 2015 runtime.
- If you want to use it in combination with Visual Studio 2013, you'll have to remove the default switch -Llegacy_stdio_definitions.lib in the configuration file etc\ldc2.conf. But apparently there's still a zlib issue in the C parts of the runtimes preventing successful linking with the VS 2013 linker. So currently, you'll need to build LDC yourself if you want to use it with VS 2013.
