Difference between revisions of "Latest pre-built LDC for Win64"

From D Wiki
Jump to: navigation, search
(7 intermediate revisions by the same user not shown)
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, the debug job publishes the LDC installation directory (a compressed [http://www.7-zip.org/ 7-Zip] archive) as build artifact, downloadable for you guys and thus saving you the hassle of building LDC yourselves:
Moved to [[Latest LDC binaries for Windows]].
* Head over to the [https://ci.appveyor.com/project/kinke/ldc Appveyor project], taking you to the <tt>LATEST BUILD</tt>.
* If the latest build is still queued or hasn't completed yet, select an older build after clicking on the <tt>HISTORY</tt> tab.
* Click on the debug job identified by <tt>Environment: APPVEYOR_JOB_CONFIG=Debug</tt>.
* Click on the job's <tt>ARTIFACTS</tt> tab on the right-hand side.
* Download <tt>ldc-x64.7z</tt>
* 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 RC (<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.

Latest revision as of 10:27, 19 March 2016