Difference between revisions of "Latest pre-built LDC for Win64"
m (I've updated the pre-built LLVM.) |
|||
| 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 | + | 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, the debug job publishes the LDC installation directory (a 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:// | + | * Head over to the [https://github.com/ldc-developers/ldc/releases/tag/untagged-364792beca0a751fe44b GitHub release] and download the bottom-most artifact. |
| − | |||
| − | |||
| − | |||
| − | |||
* Extract it somewhere. For it to work out-of-the-box, extract it to <tt>c:\projects\ldc-x64</tt>, otherwise you'll have to adapt the <tt>etc\ldc2.conf</tt> configuration file and replace the absolute paths to the LDC installation directory. | * Extract it somewhere. For it to work out-of-the-box, extract it to <tt>c:\projects\ldc-x64</tt>, otherwise you'll have to adapt the <tt>etc\ldc2.conf</tt> configuration file and replace the absolute paths to the LDC installation directory. | ||
* 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 therefore requires the [https://www.microsoft.com/en-us/download/details.aspx?id=48145 2015 runtime]. If you're using it in combination with an older Visual Studio, you'll have to remove the default switch <tt>-Llegacy_stdio_definitions.lib</tt> in the configuration file <tt>etc\ldc2.conf</tt>. | * 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 therefore requires the [https://www.microsoft.com/en-us/download/details.aspx?id=48145 2015 runtime]. If you're using it in combination with an older Visual Studio, you'll have to remove the default switch <tt>-Llegacy_stdio_definitions.lib</tt> in the configuration file <tt>etc\ldc2.conf</tt>. | ||
* It's safest to use LDC in an environment set up by MSVC, i.e., in a <tt>VS 20xx x64 Native Tools Command Prompt</tt>, for LDC to be able to use the MS linker. | * It's safest to use LDC in an environment set up by MSVC, i.e., in a <tt>VS 20xx x64 Native Tools Command Prompt</tt>, for LDC to be able to use the MS linker. | ||
| − | |||
| − | |||
---- | ---- | ||
Revision as of 23:03, 21 September 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 bottom-most artifact.
- Extract it somewhere. For it to work out-of-the-box, extract it to c:\projects\ldc-x64, otherwise you'll have to adapt the etc\ldc2.conf configuration file and replace the absolute paths to the LDC installation directory.
- 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 therefore requires the 2015 runtime. If you're using it in combination with an older Visual Studio, you'll have to remove the default switch -Llegacy_stdio_definitions.lib in the configuration file etc\ldc2.conf.
- It's safest to use LDC in an environment set up by MSVC, i.e., in a VS 20xx x64 Native Tools Command Prompt, for LDC to be able to use the MS linker.
